Pain001 logo Pain001
Get started ›

Accessibility

Accessibility Statement

WCAG 2.2 AAA as a build gate, not a review item — the target, the evidence, and the honest limits.

2 min read Last reviewed

This website targets WCAG 2.2 Level AAA — beyond the AA level most financial institutions publish against — and treats accessibility as a build gate, not a review item. This page states the target, the evidence, and the honest limits.

01. Conformance status#

All pages of pain001.com are built to conform to WCAG 2.2 AAA. Concretely:

  • Contrast: every colour token is documented in the stylesheet with its measured contrast ratio; body text meets or exceeds 7:1 in both light and dark themes, verified computationally and by automated scan.
  • Keyboard: every interactive element is reachable and operable by keyboard, with a visible focus indicator (3px ring) on all controls, a skip-to-content link as the first focusable element, and a CSS-only navigation menu that requires no JavaScript.
  • Motion and preferences: prefers-reduced-motion disables animation and smooth scrolling; prefers-contrast: more promotes all muted text to full-contrast ink; the theme honours prefers-color-scheme before first paint.
  • Structure: one h1 per page, landmark regions, visible breadcrumbs mirrored in structured data, tables with proper header scope that collapse to labelled cards on small screens, and touch targets of at least 44px.
  • Zero-JS interactivity: FAQs are native details/summary elements; the mobile menu is a checkbox toggle. JavaScript is an enhancement, never a requirement, everywhere except the interactive demo — which is progressively disclosed and fully keyboard-operable.

02. How this is tested#

Three layers, run on every build via continuous integration:

  1. Build gates — the site generator's WCAG audit runs across all pages on every build and fails the build on any finding.
  2. Independent automated scan — pa11y 4.1.1 at the WCAG2AAA standard across twelve representative pages (home, documentation, installation, demo, MCP, briefing, FAQs, glossary, comparison, contact, French, 404), in both light and dark themes. Current result: zero errors.
  3. Manual keyboard pass — tab-order walk, skip-link operation, focus-visibility check, and keyboard operation of the demo and FAQ widgets, performed on the current release (last performed: 26 July 2026).

Fixes found by this process are applied at the source or in the build pipeline — including repairs to third-party components (the search widget's injected styles and the markdown renderer's presentational attributes were both corrected at build time to meet AAA).

03. Known limitations#

  • Assistive-technology coverage: testing to date uses automated tooling, computed contrast, and manual keyboard passes. Structured testing with screen readers (VoiceOver, NVDA, JAWS) has not yet been performed by users of those technologies; if you rely on one and hit friction anywhere, that is a bug — please report it.
  • Code samples scroll horizontally on narrow screens rather than wrapping, preserving meaning at the cost of a scroll gesture.
  • Third-party destinations (GitHub, PyPI) linked from this site have their own accessibility policies.

04. Feedback and enforcement#

Accessibility issues are treated with the same severity as functional bugs. Report anything — however small — via GitHub issues or contact@pain001.com. Reports are typically acknowledged within a few days.

This statement was prepared on 26 July 2026 and is reviewed with each site release.