01 · CommitmentThe standard.
jonrezin.com is committed to providing a website that is accessible to the widest possible audience, regardless of ability, technology, or circumstance. We aim to conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the international standard published by the World Wide Web Consortium (W3C).
This statement applies to jonrezin.com in its entirety, including all subpages, blog posts, release pages, and admin interfaces.
02 · What we've doneBuilt-in features.
- Semantic HTML structure with proper heading hierarchy and landmark regions.
- Skip-to-content link at the top of every page.
- Keyboard-navigable controls with visible focus indicators.
- Color contrast that meets or exceeds WCAG AA (4.5:1 for body text, 3:1 for large text).
- Text alternatives for all meaningful imagery (alt text, ARIA labels).
- Form fields with associated labels and clear error messaging.
- Modal dialogs with focus traps, escape-to-close, and click-outside dismissal.
- Carousel/slider components with keyboard controls and pause-on-hover.
- Reduced-motion support — animations are minimized for users who prefer it.
- 16px minimum font size on form inputs (prevents iOS zoom-on-focus).
- 44px minimum tap-target size for interactive elements on mobile.
- Embedded media (YouTube, Spotify, Apple Music) inherits the host platform's accessibility features, including captions where provided by the rights holder.
03 · Known limitationsWhere we're still working.
Honest disclosures of areas under active improvement:
- Some embedded YouTube videos may not have captions if the rights holder hasn't provided them — we don't control caption availability on third-party content.
- The interactive Leaflet world map on the credits-stats page is visual; the same data is presented in a screen-reader-friendly ranked list adjacent to the map.
- The artist-graph force-directed visualization is visual; a searchable artist directory is available at /artists as a text-based alternative.
- Some legacy blog posts may have minor heading-order or alt-text gaps; we audit and fix these as we encounter them.
- Dolby Atmos audio examples assume the listener has stereo or compatible playback — alternative formats are noted where relevant.
04 · Tools we useHow we test.
We use a combination of automated and manual testing:
- axe DevTools and Lighthouse accessibility audits in Chrome and Safari.
- Manual keyboard-only navigation passes on every new template.
- VoiceOver (macOS / iOS) screen-reader checks on critical user flows: contact form, work-with-me form, newsletter signup, admin login.
- Color-contrast verification with the WebAIM contrast checker.
- Mobile audit on iOS and Android with real devices, not just emulators.
05 · Report a barrierIf something doesn't work.
If you encounter a page, control, or piece of content that isn't accessible to you — even if it's not in the "known limitations" list above — we want to know. We aim to respond to all accessibility reports within 5 business days, and to remediate confirmed barriers as quickly as practical.
06 · Formal complaintIf we don't resolve it.
If you've reported an accessibility barrier and aren't satisfied with our response, you may file a complaint with:
- United States: the U.S. Department of Justice Civil Rights Division (Title III ADA) — ada.gov/file-a-complaint.
- European Union: the equalization body in your member state under the European Accessibility Act / Directive (EU) 2019/882.
- United Kingdom: the Equality and Human Rights Commission — equalityhumanrights.com.
07 · Conformance levelWhere we stand.
This site is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most parts of the content fully conform but some parts (notably embedded third-party media and certain legacy blog posts) do not. We continue to make improvements with each release.
This statement was last reviewed on the date listed above and is reviewed on each significant site update.