Accessibility

Accessible
by design.

Accessibility is part of how I work, not a check at the end. At PrePass it is a hard requirement: our services run in government facilities and scalehouses, and state partners require WCAG 2.1 AA for every new product. I hold this site to the same standard.

On this site

  • Keyboard: every link, button and form control works from the keyboard, with a visible focus ring and a skip link straight to the main content.
  • Contrast: text meets WCAG AA contrast, 4.5:1 or better, including the small labels and the form’s helper text.
  • Motion: if your device asks for reduced motion, the star field becomes a still image, the headline doesn’t animate in, the moon rests beside its letter and the sun stops pulsing.
  • Custom controls: the contact form’s “Type of work” menu follows the W3C ARIA Authoring Practices for a select-only combobox, with full keyboard support and screen-reader announcements. Without JavaScript it falls back to a standard menu.
  • Forms: every field has a visible label, required fields are flagged to assistive technology, and errors are written out in text and announced.
  • Touch: tap targets are at least 44 pixels on phones, and navigation is a bottom tab bar rather than a hidden menu.
  • Structure: page landmarks, one main heading per page, meaningful heading order, and alternative text on every content image. Decorative 3D and animation are hidden from screen readers.
  • Zoom and reflow: pages reflow down to small phone widths, and zoom is never disabled.

In my work

On product teams I treat accessibility as a design constraint from the first sketch: contrast and focus states live in the design system’s tokens and components, interaction patterns follow established ARIA practices, and automated checks catch regressions before customers do. Field research matters here too: an officer reading a screen at a glance, under glare, mid-task, is an accessibility case as real as any screen reader.

Feedback

This statement reflects my own review against WCAG 2.1 AA, last updated October 2026. If anything on the site gets in your way, email info@chsanderson.com and I’ll fix it.