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.
2. Identified Shortcomings (Honest List)
The items below are real shortcomings identified through manual testing and automated tools (Lighthouse Accessibility, axe DevTools, keyboard-only navigation). A target fix date has been set for each item.
On some hero images and illustrations on the marketing pages the alt attribute is empty or insufficiently defined. For decorative images alt="" (intentionally empty) should be used; for images carrying content, descriptive text should be written.
Some contact and sign-up form fields are labeled only with a placeholder; an explicit <label for="..."> or aria-label should be added for screen readers. The aria-describedby link for error messages will also be reviewed.
In some footer links, small label texts and gray secondary text the contrast ratio may fall below the 4.5:1 threshold required by WCAG AA (a 3.8-4.3 range was detected). All gray tones will be darkened toward #4b5563 instead of #6b7280.
Keyboard users have to tab through the entire menu on every page. A "Skip to content" skip link (visually hidden, becoming visible on focus) will be added to the top of the page.
Target fix date: Q3 2026
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.
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.
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:
- 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 time is extended for a valid reason, we inform you and provide 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:
7. Preparation of the Statement
8. Transparency Note
Every newly identified shortcoming is published here the same day; nothing is hidden. Once a fix is complete it is kept with a "Resolved" mark; that way 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.
Related pages:
Every piece of accessibility feedback is valuable: erisim@cerez.io · This page was last updated on 31 May 2026.
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.