Accessibility statement

I check websites for accessibility, so this one has to be accessible too. If any part of it does not work for you, I want to know, and I will fix it.

My goal for this website is WCAG 2.2 Level AA. That is one version newer than the WCAG 2.1 Level AA I check client sites against. I also follow the extra best-practice rules in the axe-core scanner.

These are the tests I ran on every page, on October 29, 2026:

• Two automated scanners. axe-core 4.13.0 and AccessLint 0.13.0, at a desktop size (1280 by 900) and a phone size (390 by 844). A second axe-core pass added the WCAG 2.2 and best-practice rules. That pass ran in both color schemes, light and dark. Result: no problems found.
• Lighthouse. Google’s Lighthouse 13.6.0 accessibility score, with phone and desktop settings. Result: 100 on every page.
• Keyboard. A scripted walk with the Tab key through every page, at both sizes and in both color schemes. Every stop has a visible focus outline and a name, nothing covers it, and the skip link moves focus to the main content.
• A screen reader. NVDA 2026.2 on a Windows laptop, in Microsoft Edge. It read every page two times: the headings, landmarks, links and pictures, every Tab stop, and the whole page from top to bottom. It reached the end of every page. Result: no problems found.
• The example on the Check page. The “Show the fixes” switch works with the Space key and the Enter key. It tells a screen reader whether it is on, and it announces what changed. With JavaScript off, the example is a still picture with its three notes.
• Zoom and narrow screens. Every page at 320 and 640 pixels wide (like 400% and 200% zoom on a laptop). No sideways scrolling. Also a Tab walk on a very short screen, 382 by 174 pixels (400% zoom on a small laptop screen). No focused item was hidden.
• Text spacing. Every page with wider line, letter, word and paragraph spacing. No text was cut off or overlapped.
• High contrast and reduced motion. Every page with Windows high-contrast colors and “reduce motion” turned on, emulated in Chrome. Focus outlines and buttons stay visible, and nothing moves.
• Color contrast. The scanners measured the text on every page in both color schemes. A second check measured every color pair in the style sheet, in both color schemes.

• VoiceOver on a Mac and an iPhone: some pages were checked by hand on October 29, 2026. A full VoiceOver pass on every page is still to do.
• The screen reader test ran on a real Windows laptop. The other tests ran in Google Chrome on a Mac. High-contrast mode and zoom were emulated in Chrome, not tested on a Windows computer or a real phone.

If something on this site does not work for you, please email kyle@awfullyhelpful.com. Tell me the page and what went wrong. I will be embarrassed, and then I will fix it.

This statement was written on September 30, 2026, and updated on October 29, 2026. It is not a technical assessment or a claim of conformance.