Accessibility Statement

1. Our Commitment

We treat accessibility as a functional requirement rather than a late-stage audit. Accessible markup, keyboard operability, and sufficient contrast are part of how we build, not something retrofitted before launch.

We aim to conform to Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the standard referenced by EN 301 549 and, through it, by the European Accessibility Act. We publish our real status below rather than a conformance claim we have not earned.

2. Scope of This Statement

This statement applies to the website published at c9group.dev, including all language versions and all pages served under that domain.

It does not cover:

• Third-party platforms we link to, such as our GitHub organisation, LinkedIn page, or Google Play listing, which are governed by their operators' own accessibility statements
• Software we build for clients, whose accessibility is addressed in the applicable engagement agreement
• Archived documents published before this statement's date

3. Conformance Status

We would rather state a partial conformance we can substantiate than claim full conformance we have not independently tested. We intend to commission an external audit and will update this statement — including the auditor's identity and the date of assessment — once it is complete.

4. Known Limitations

We are aware of the following barriers. Each is listed with the WCAG success criterion it relates to and our remediation intent.

If you encounter a barrier that is not listed here, please tell us — see Reporting a Barrier below. Reports from users are the fastest way for us to find what our own testing missed.

5. Measures We Take

To support accessibility, we:

• Build with semantic HTML and native controls in preference to custom widgets
• Set the page language programmatically so assistive technology reads each translation correctly
• Maintain text and interface contrast ratios at or above the WCAG AA thresholds
• Keep every interactive control reachable and operable by keyboard, with a visible focus indicator
• Render the site server-side, so content is present without relying on client-side scripting
• Provide text alternatives for informative images and mark decorative images so they are ignored by screen readers
• Respect the operating system's reduced-motion preference
• Include accessibility in code review, and treat reported barriers as defects rather than enhancement requests

6. Technical Specifications

Accessibility of this website relies on the following technologies working with your browser and any assistive technology you use:

• HTML
• WAI-ARIA
• CSS
• JavaScript
• SVG

These technologies are relied upon for conformance with WCAG 2.2 Level AA.

7. Compatibility With Browsers and Assistive Technology

This website is designed to work with current versions of Chrome, Firefox, Safari, and Edge, on desktop and mobile, in combination with the screen readers commonly paired with them, including NVDA, JAWS, VoiceOver, and TalkBack.

It is not tested against browsers more than two major versions behind current, and it may not work reliably with Internet Explorer.

8. How We Assessed This Website

The conformance status above is based on a self-evaluation carried out by C9 Group, combining:

• Automated testing of rendered pages against WCAG 2.2 rules
• Manual keyboard-only traversal of the primary user journeys
• Manual review of heading structure, landmarks, form labelling, and link text
• Contrast measurement of text and interface components

Automated tooling reliably detects only a minority of accessibility barriers, which is why the manual review matters and why an independent audit remains on our plan. Anyone claiming a tool alone proves conformance is overstating what tooling can do.

9. Reporting a Barrier

If you cannot access part of this website, or you need information from it in a different format, please contact us. Tell us the page address, what you were trying to do, and — if you can — the browser and assistive technology you were using. Any detail helps, but none of it is required; a one-line report is welcome.

10. If You Are Not Satisfied

If you are unhappy with how we handled your report, please escalate it to office@c9group.dev, marking it for the attention of management, and we will review it independently of whoever handled it first.

If you remain dissatisfied, you may contact the market surveillance authority responsible for accessibility of digital services in your country. Within the European Union, each Member State designates such an authority under the European Accessibility Act (Directive (EU) 2019/882) and its national implementing legislation.

11. Preparation and Review of This Statement

This statement was prepared with reference to the model statement structure used under EN 301 549 and the European Accessibility Act.

12. Language