Government-technology systems are used by every citizen — including citizens with visual, auditory, motor, or cognitive impairments. Accessibility is not a feature we add on; it is a structural quality of the platforms we build. We commit to WCAG 2.2 Level AA conformance as the baseline standard for this website and all citizen-facing surfaces we produce, and we hold ourselves to that standard in active development as well as in published deliverables.
Our design system enforces minimum contrast ratios, accessible focus states, scalable typography, and keyboard-navigable patterns. Components that fail accessibility review do not enter the library.
We use semantic HTML, ARIA only where appropriate, and consistent heading hierarchies. We do not rely on colour alone to convey meaning.
Every interactive surface is fully operable from the keyboard alone. Focus order is logical and visible.
Citizen-facing platform surfaces are tested with at least one current screen reader (NVDA or VoiceOver) before release.
The platform is built RTL-first. Accessibility is verified in both LTR (English) and RTL (Arabic) modes.
Citizen-facing copy is reviewed against plain-language guidelines. Government services are unintelligible to many citizens not because of the topic but because of the language used; we treat that as a defect.
| emeron.io (this website) | Partially conformant with WCAG 2.2 Level AA. Active remediation of known gaps in progress; published audit scheduled Q3 2026. |
| CitizenOS platform | Built to WCAG 2.2 AA as a design-system requirement; per-deployment conformance verified at acceptance test with the customer. |
| Administrative consoles | Built to WCAG 2.2 AA where reasonably achievable for the target user (trained administrative staff). Documented exceptions where role-specific UI requires it. |
| Procurement documents (PDF) | Tagged, navigable, and screen-reader compatible. Older archived documents may not meet current standards — accessible versions available on request. |
In the interest of honesty: we are not perfect today. Known accessibility gaps on this website, currently being remediated, include (a) inconsistent focus styling on a small number of legacy components, (b) decorative SVG that should be hidden from assistive technology, and (c) form-error patterns that need a clearer non-visual signal. These items are tracked, owned, and targeted for resolution in our Q3 2026 release cycle.
If you encounter any other accessibility issue on this site or a platform we operate, please tell us — see below.
Write to accessibility@emeron.io. Please include (a) the URL or screen where you encountered the issue, (b) the assistive technology you were using if applicable, and (c) what you were trying to do. We acknowledge accessibility reports within five business days and commit to a remediation plan within twenty.
If the issue concerns a citizen-facing service operated by one of our customers, we will route the report to the customer alongside our own acknowledgement, and remediation will be coordinated with them.
One inbox, one named owner, one acknowledged response window. Accessibility is not delegated to a generic support queue.