Accessibility Statement

Last updated: 2026-04-17

What's in place today

• Skip-to-content link that appears as the first focusable element on every page.
• Semantic landmarks (<header>, <nav>, <main>, <footer>) and heading hierarchy.
• Keyboard navigation for the primary nav and mobile menu, with ESC + outside-click to close.
• Consent dialog uses role="dialog" with a focus trap and ESC-to-decline.
• Charts expose an SR-only data table and an aria-label derived from the chart description or title.
• Wiring schematics expose <title>/<desc> via aria-labelledby and can carry a textual connection list.
• Visible focus indicators on interactive controls; the one focus:outline-none offender has been replaced with a focus-visible ring.

What's in place today (continued)

• Dark mode with a toggle in the primary nav, persisted in localStorage. Respects prefers-color-scheme on first visit and sets data-theme before paint to avoid flash.

Known gaps

• Automated a11y scans (pa11y-ci + Lighthouse) are not yet blocking in CI — they're being stood up as advisory-first so we fix the backlog before enforcing.
• Alt-text coverage on inline images in articles is inconsistent; it's being audited.
• Dark mode contrast has been implemented but not yet re-audited with axe/Pa11y against every component state — the advisory a11y workflow will catch regressions as the dark palette settles.
• Chart components accept a description prop but don't currently enforce it — some older charts rely on title-only labelling.

How to report a barrier

If something on this site gets in your way, please tell me. The fastest path is a GitHub issue using the a11y report template — it captures the page, the assistive technology, and what you expected.

File an accessibility report on GitHub · or email contact@jellwrites.com.

Keyboard navigation reference

The site is fully operable without a pointing device. These are the shortcuts you'll use most often.