cerez.io Accessibility Statement
We run our own site with our own product. This statement was prepared per EAA Article 13 + EN 301 549 + WCAG 2.2 AA standards, including our shortcomings.
1. Compliance Status
cerez.io is currently PARTIALLY COMPLIANT with the WCAG 2.2 AA standard. Our goal is to reach WCAG 2.2 AA FULL COMPLIANCE by the end of 2026.
"Partially compliant" means: the bulk of the site (navigation, main content, forms, documentation) meets the accessibility criteria; however the shortcomings listed in Section 2 below have not yet been resolved. WCAG 2.2 AAA level is not our goal; WCAG's own documentation states that this level is not applicable for most content types.
| Standard | Target Level | Current Status |
|---|---|---|
| WCAG 2.2 | Level AA | Partially Compliant |
| EN 301 549 v3.2.1 | Article 9 (Web) | Partially Compliant |
| EAA (Direktif 2019/882) | Article 13 | Statement Published |
| Law No. 5378 + KAİK | Full Compliance | Partially Compliant |
2. Identified Shortcomings (Honest List)
The items below are real gaps identified through manual testing and automated tools (Lighthouse Accessibility, axe DevTools, keyboard-only navigation). A target fix date is set for each item. Items resolved in the September 2026 scan have been removed from this list; what was done is listed separately below.
The "Products" and "Solutions" dropdown menus in the header work fine with a mouse; however they were not fully tested keyboard-only (Tab, Enter, arrow keys, Escape). ARIA aria-expanded, aria-haspopup and focus management will be reviewed.
Some modal windows may be missing the aria-modal="true" and role="dialog" attributes. When a modal is closed, focus should return to the trigger element that opened it; this behavior will be standardized across all modals.
There is currently no video content on the site. For tutorial videos to be added soon, closed captions, audio description for visually impaired users, and a transcript will be mandatory. WCAG criteria 1.2.2, 1.2.3 and 1.2.5 will be applied.
Policy: CC and transcript will be ready before publishing
The <nav>, <main>, <aside>, <footer> semantic elements are not used consistently across all pages. On some pages a div was preferred. All page templates will be reviewed and migrated to semantic HTML5 elements.
Gaps resolved in the September 2026 scan
The items listed below from the 31 May 2026 statement have been resolved and verified by measurement.
At the top of every page there is a Skip to content link that becomes visible on keyboard focus and moves to the main content region (main).
The areas previously reported in the 3.8-4.3 range were re-measured: footer links 6.96:1, footer headings 14.48:1, secondary grey text 4.83:1, body text 7.65:1. All are above the 4.5:1 threshold required for WCAG AA.
Verified: 10 September 2026
All fields in the contact, registration and sign-in forms are associated with an explicit <label for="...">. The hidden spam-trap field in the newsletter form also received an aria-label so that screen readers announce a name for it.
The alt attribute has been completed for content images, and decorative images are marked with an intentionally empty alt="". In addition, skipped heading levels (such as h5 following h1) were corrected, caption elements were added to data tables, and external links that open in a new tab now carry a screen reader notice.
3. Tested Environments
This statement is based on tests carried out in the following environments. The coverage is not complete; we continue to expand it.
| Assistive Technology | Platform | Status |
|---|---|---|
| NVDA (Turkish) | Firefox / Windows | Tested |
| VoiceOver | Safari / macOS | Partially tested |
| JAWS | Chrome / Edge / Windows | Planned: Q4 2026 |
| TalkBack | Chrome / Android | Planned: Q4 2026 |
| Keyboard-only navigation | Tab, Enter, Esc, arrow keys | Tested |
| Chrome DevTools Lighthouse | Accessibility audit | Run continuously |
| axe DevTools (Deque) | Chrome extension | Run continuously |
4. Feedback and Contact
If you experience an accessibility issue, a feature isn't working, or there is an incompatibility with your assistive technology, please reach out:
| Channel | Contact |
|---|---|
| Accessibility dedicated line | erisim@cerez.io |
| General support | destek@cerez.io |
| Phone | +90 540 059 40 40, Monday-Friday 09:00-18:00 |
| +90 540 059 40 40 | |
| Contact form | cerez.io/iletisim |
- We respond to your request within 7 days.
- We commit to fixing the issue within 30 days (7 days for critical access-blocking issues).
- If the fix takes longer for a substantiated reason, we inform you and give a new target date.
5. Legal Basis
This statement was prepared within the framework of the following national and international legislation:
- EAA (European Accessibility Act, Directive 2019/882). In force in EU member states as of 28 June 2025. cerez.io is within scope as it provides customer services aimed at the EU market.
- EN 301 549 v3.2.1. The European harmonized standard and the technical counterpart of the EAA. Article 9 (Web content), Article 10 (Non-web documents) and Article 11 (Software) are the relevant sections.
- WCAG 2.2 (W3C). Web Content Accessibility Guidelines: Level A, AA and AAA. Our goal is Level AA.
- Law No. 6701 on the Human Rights and Equality Institution of Turkey. Prohibition of disability-based discrimination.
- Law No. 5378 on Persons with Disabilities. The right of persons with disabilities to access information and communication services.
- Presidential Circular No. 2019/12: Accessibility of Public Web Pages and Mobile Applications (KAİK). Mandatory for public institutions; a best-practice reference for the private sector.
- Section 508 (USA). Mandatory for suppliers doing business with federal agencies. cerez.io This compliance is used as a reference for US customers.
6. Enforcement Procedure (Right to Complain)
If you are not satisfied with our response to the accessibility request you submitted to us, or if your request goes unanswered, you have the right to file a complaint with the following institutions:
| Institution | Area of Authority |
|---|---|
| Disability Federation of Turkey | NGO support and follow-up: engelliler.gen.tr |
| KAİK (Public Accessibility Monitoring and Auditing Unit) | Accessibility auditing of public sites (an advisory mechanism for the private sector) |
| Human Rights and Equality Institution of Turkey (TİHEK) | Discrimination complaints under Law No. 6701: tihek.gov.tr |
| Ombudsman Institution | Complaints against administrative actions: ombudsman.gov.tr |
| Ministry of Family and Social Services, General Directorate of Services for Persons with Disabilities and the Elderly | Review under Law No. 5378 |
7. Preparation of the Statement
| Method | Manual testing (keyboard, NVDA, VoiceOver) + automated tools (Lighthouse, axe DevTools) + internal team code review |
| Initial publication date | 31 May 2026 |
| Last update | 31 May 2026 |
| Next scheduled review | 30 November 2026 (6-month cycle) |
| Independent third-party audit | Planned for Q4 2026 |
| Statement language | Turkish (official); English and German translations coming soon |
8. Transparency Note
Every newly identified gap is published here the same day; nothing is hidden. Once a fix is complete it is kept with a "resolved" marker, so the history of the process stays traceable.
Accessibility is not a destination but a process of continuous improvement. It is the example the team behind the product we sell to our customers should set on its own site.
Your own site needs an EAA statement too
EAA Article 13 requires an accessibility statement for every digital service. Create an honest, complete statement like ours in 5 minutes.