Accessibility

Last updated: September 9, 2026.

Our commitment

Eunomia, both this website and the @eunomia/elements library it documents, is designed and maintained independently, by a single developer. Accessibility standards (WCAG, ARIA authoring practices) are followed to the best of our ability throughout design and development, but this is a best-effort, independent commitment, not a certified one: no certified accessibility audit has been performed on this website or the library. See "Current limitations" below for exactly what that does and does not cover.

This is not a legally mandated accessibility statement either: under French law, that obligation applies to public-sector organizations and large private companies, not to a site like this one. We publish it anyway because accessibility is one of the things the library is meant to make easier to get right for the people who build on it. If anything here is unclear, or you run into a concrete issue, contact us: see "Reporting an issue" below.

What's built in

• ARIA roles, states, and keyboard navigation are part of every interactive component's own implementation, not an optional add-on consumers have to build themselves.
• Severity matters to how information is announced: eun-alert interrupts the current screen reader speech for warning and critical severities, and waits for it to finish for every other one.
• Every color in every prebuilt theme, light and dark, is generated from a WCAG 2.1 relative-luminance and contrast-ratio calculation at build time, not picked by eye.
• Focus is managed explicitly in components that open or close content, such as the modal, drawer, dropdown, and tooltip.

Current limitations

• This project is designed and maintained independently, by a single developer, without a dedicated accessibility team or a certified auditor.
• No formal accessibility audit, RGAA or WCAG, has been carried out on this website or the library yet.
• Accessibility is verified by design and manual testing during development, not by an automated test suite: there is no automated accessibility testing (such as axe-core) in the project's test pipeline yet.
• Conformance to a specific WCAG level is a design target guiding how components are built, not a certified or audited outcome.

Reporting an issue

If you run into an accessibility barrier on this website, or in a component from the library, please let us know at melvin.marra@gmail.com. We'll do our best to address it.