Accessibility Statement
This platform is built to conform to WCAG 2.1 Level AA as its target
standard. This page describes what's actually been done toward that goal, what's still in
progress, and how to report an accessibility problem.
What this site does today
- Color contrast. Text and interactive-component colors are checked
against the WCAG AA contrast formula (4.5:1 for normal text, 3:1 for UI components), in
both light and dark mode. A recent design-system review found and corrected three real
contrast gaps — a keyboard focus ring, several component borders, and a hover-text color in
dark mode — all now verified passing.
- Keyboard navigation. Every interactive element — links, buttons, the
mega menu, the mobile drawer, form fields, tabs, and accordions — can be reached and
operated using only a keyboard, with a visible focus indicator at every stop.
- No keyboard traps. The mobile navigation drawer and dropdown menus can
always be closed with the Escape key or by moving focus away.
- Semantic HTML. Headings, lists, tables, and landmarks (header, nav,
main, footer) use real HTML elements rather than styled generic <div>s, and a "Skip to
main content" link is available at the very top of every page for keyboard and
screen-reader users.
- Works without JavaScript. Every navigation path, form, accordion, and
tab set on this site is built with plain HTML/CSS first — JavaScript (used only for the
sticky header and mobile drawer) is a progressive enhancement, not a requirement.
- No motion traps. Animations are short and subtle by design; if your
system has "reduce motion" turned on, transition effects are minimized accordingly.
Known limitations
This statement is honest about gaps rather than silent about them:
- This site has not yet been audited by a third-party accessibility specialist or tested
with real assistive-technology users — the checks described above were done programmatically
and through manual keyboard/contrast review, not a full external audit.
- A small number of older content pages may not yet reflect every design-system update
described here, since this platform is updated incrementally rather than all at once.
Reporting an accessibility problem
If you use assistive technology and hit a barrier anywhere on this site, please tell us
specifically what page you were on and what happened. We treat accessibility reports the same
way we treat factual corrections: acknowledged and acted on, not ignored.
Found an accessibility barrier?
Tell us the page and what happened — a real person reads every message.
