Accessibility statement.
This site should be usable by everyone, including people who navigate by keyboard, use a screen reader, or need larger text and higher contrast. Here is exactly what that means in practice, and what to do if it isn't true for you.
Our conformance target
itsjustin.me aims to conform to Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That's the standard referenced by the Americans with Disabilities Act in US practice, and it's the bar I hold client sites to, so it's the bar this site is held to as well.
What that means on every page here
- A skip link is the first thing you reach by keyboard, so you can jump straight past the navigation to the content.
- Every page has one main heading and headings run in logical order, so screen-reader navigation by heading works.
- Every image and diagram has a text alternative. The illustrations in the build guide are inline graphics with a title and a full description, so nothing shown as a picture is unavailable to a screen reader.
- Every interactive control has a visible focus outline, is reachable by keyboard, and is announced with a meaningful name.
- Text meets a contrast ratio of at least 4.5:1 against its background.
- Links that open a new tab say so to assistive technology.
- Pages are readable and usable at 200% zoom and on small screens.
Known limitations
Being honest is more useful than claiming perfection:
- Some wide content — tables and diagrams — scrolls sideways inside its own box on narrow screens. That's a deliberate choice so the page itself never scrolls sideways, but it does mean some content requires horizontal scrolling within a region.
- This site links out to third-party sites. I can't control their accessibility, only my own.
If you hit something not listed here, I'd genuinely rather know.
Feedback — and what happens when you send it
If any part of this site is a barrier to you, email heywillhite@gmail.com and tell me the page and what happened. You do not need to know the technical name for the problem — "the menu won't take my keyboard" is a perfect bug report.
I aim to reply within 5 business days and to fix confirmed barriers as a priority over new features. If a fix will take time, I'll tell you that and offer the content another way in the meantime.
How this is tested
Pages are checked with automated tooling (axe and Lighthouse) and by keyboard-only navigation. Automated tools catch perhaps a third of real accessibility problems, which is why the feedback address above is not decorative — human reports are how the rest get found.