Accessibility Statement
Last updated: 4 November 2026 · Goal: WCAG 2.2 AA
DRAFT — legal counsel approval required
Current status
1. Status and goal
TRADO aims to make its public website and the buyer/seller panels accessible at WCAG 2.2 AA (Web Content Accessibility Guidelines). This is a goal; we do not claim conformance today.
Current status: partially conformant — assessment in progress. Below we state plainly what is checked automatically and by tests, and what has not been done yet.
2. Scope
This statement applies to the public TRADO website and the signed-in buyer and seller panels (Turkish and English interface). The administration application used by the platform team is a separate application and is outside the scope of this statement.
Content uploaded by users (product images, documents, certificates, message attachments) and text entered by companies belongs to the user; TRADO cannot verify the accessibility of this content. The alternative text of images depends on what the product owner enters.
3. What we do (checked by automation and tests)
The items below are checked by automated tools and software tests. This does not mean a person has verified them by hand with assistive technology (see section 4).
- Automated scanning: in browser-based end-to-end tests, axe-core 4.x scans many pages and states with the rules tagged WCAG 2.0, 2.1 and 2.2 A/AA (wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa); new screens are added to this scan and a violation fails the test.
- Of WCAG 2.2, axe automatically catches only 2.5.8 (Target size, at least 24 × 24 pixels). For 2.4.11 (focus is not hidden under the sticky cookie banner), 2.5.7 (no functionality requires dragging), 3.2.6 (consistent help), 3.3.7 and 3.3.8 (pasting into password fields is not blocked, password managers are supported, no cognitive tests) there are unit and end-to-end tests.
- Design principles: every form field has a visible label, error messages are associated with the field and announced to screen readers (role="alert"), dialogs manage focus, tables have header cells, state is shown with text and not only colour, all functions are reachable by keyboard, heading order is kept.
- The interface is offered in Turkish and English; the page language is marked.
4. Known limitations
- Manual screen reader testing has not been done yet: no NVDA or VoiceOver pass has been carried out. Live-region announcements (status messages) and focus management have not been tried by a person with assistive technology.
- We have no manual audit record and no independent third-party accessibility audit. Our assessment is a self-assessment based on automated checks and tests.
- The WCAG 2.2 criteria that cannot be caught automatically are protected by pattern-based tests; a violation could be missed if a new component is added in a way those tests do not detect.
- Some pages (for example consent management, the unit conversion tool, city and category supplier pages, seller payment terms) were verified only by automated scanning and tests, not by hand.
- axe "best practice" rules are off in the default scan. WCAG 2.2 AAA criteria (2.4.12, 2.4.13, 3.3.9) are out of scope.
- Documents and images uploaded by users (section 2) may not be accessible.
5. Assessment method
The assessment was carried out by the TRADO team: automated scanning (axe-core), unit tests and browser-based end-to-end tests. Manual testing with a screen reader is planned before launch; this statement will be updated when it is done.
6. Feedback and support
If you cannot use a page or a function, or you notice an accessibility problem, please tell us: field to be completed: [accessibility contact channel: e-mail address / form — to be completed]. Please include the page address, the problem you experienced and the browser or assistive technology you use.
We aim to reply to reports within field to be completed: [response time — to be set with legal counsel]. Where needed we will try to provide the same information in another format (for example as plain text).
7. If you are not satisfied with our reply
If our reply is not sufficient, the competent authority and route you can turn to: field to be completed: [competent authority / complaint route — to be determined by legal counsel].
8. Updating this statement
This statement is updated as accessibility work progresses (in particular when manual testing is done); the date of the last update is shown at the top of the page.