Skip to content
fixyour.page

Accessibility

We aim for WCAG 2.2 Level AA. We haven't had a formal audit, so we won't claim we're there. Here's what we've built in, and what we know is still rough.

What We've Built In

  • Semantic HTML landmarks: <header>, <main>, <nav>, <footer>.
  • Skip-to-content link as the first focusable element on every page.
  • Visible orange focus ring on every interactive element.
  • Keyboard-navigable nav, including Escape to close the mobile menu.
  • lang="en" declared on every page.
  • Form fields have associated <label> elements.
  • ARIA attributes (aria-label, aria-expanded, aria-controls) on toggles and custom controls.
  • Meaningful images have alt text; decorative SVGs are hidden from screen readers.

Gaps We Know About

  • No formal third-party accessibility audit.
  • No systematic screen reader testing (NVDA, JAWS, VoiceOver) — just spot checks.
  • Some of the more interactive tools (toggle groups, live-update previews, color pickers in the CTA button generator) likely have rougher edges in assistive tech than the static pages do.

We Drink Our Own Coffee

We ship an Alt Text Checker and a Heading Analyzer so you can audit your own pages. Felt fair to apply the same standards here.

Report Something Broken

Email [email protected]. Tell us what assistive tech you use and what didn't work. We read every one.