How accessible this site is, and where it isn’t.

This site targets WCAG 2.2 Level AA and conforms to it.

Every page was audited against Level AA in full, not sampled. That covered twelve routes at seven widths, from 320 pixels to 2560, when the full audit ran.

Evaluation date: August 9, 2026.

The site now has seventeen routes. Pages added or changed since the full audit are checked against the same standard as they ship, real computed color contrast, keyboard focus, and semantic structure, not just an automated scan. Most recently verified: August 23, 2026.

Light mode has its own set of color tokens, checked against the same AA contrast requirements as dark. Switching between them respects reduced motion. Under that setting the transition is skipped entirely.

The audit ran in seven phases over multiple days, each one committed separately: baseline, structure, contrast, keyboard and focus, screen reader semantics and alt text, motion and media, and forms.

Automated testing used axe-core 4.12 across every route at every width, 84 runs in total, in headless Chrome so that entrance-animated content was actually visible to the scanner. Automation catches roughly a third of accessibility problems, so the rest was done by hand: every one of the 581 focusable elements on the site was focused and checked for a visible ring, color contrast was measured by compositing the real rendered layers rather than reading values off the stylesheet, and reduced-motion behavior was verified with the operating system preference emulated rather than assumed.

Automated tools cannot hear anything, so the contact form was also tested with VoiceOver on macOS. That pass found a real defect no scanner reported: the success message was announced twice, once by the live region and once by the focus move. It now announces once.

Result: zero automated violations mapped to WCAG, down from 47 at the start.

The site relies on HTML, CSS, JavaScript and SVG. Page content is rendered on the server and readable without JavaScript; interactive pieces, the image viewer, the work filters and the carousels, need it.

The audit was carried out in Chrome on macOS, then verified again in Safari and Firefox.

If any part of this site is hard to use, I want to know, and I will fix it rather than log it.

Send it through the contact form. Tell me the page and what happened, and I’ll get back to you shortly.

This statement covers mrchrisallen.me and was last reviewed on August 23, 2026.