Houston Dragna · Accessibility

Accessibility

Last tested August 2026 · 744 automated checks passing

This site aims to meet WCAG 2.2 Level AA. It is not perfect, and the parts that fall short are listed below rather than left for you to discover.

What is in place

• A skip link, so the keyboard does not have to walk the whole photo grid to reach the content
• Every interactive element reachable and operable by keyboard, with a visible focus ring
• Page changes announced to screen readers, with focus moved to the new content
• Alt text on every image, written by looking at the picture rather than reading the filename
• Photo grids that report their size and your position in them
• Text and controls that meet contrast minimums in both the dark and light themes, verified by measurement
• Full function at 400% zoom with no sideways scrolling, and with your own text spacing applied
• Motion that respects the reduced-motion setting, and colour that is never the only signal
• Support for Windows High Contrast and forced-colours modes
• Touch targets that clear the 24px minimum

Where it still falls short

Stated plainly, because a list of known gaps is worth more than a badge:

• Small monospaced labels around the edges of the layout run to 10px. They pass contrast, but they are smaller than I would set for body copy.
• The hero name sits over photography, so its contrast depends on the image behind it.
• The films are hosted on YouTube. Captions there are the platform's, not mine, and quality varies by video.
• Testing is largely automated. It is checked by hand with a screen reader periodically, not on every change.

No accessibility overlay

This site does not use an accessibility overlay or widget. Those tools are widely opposed by the disabled people they claim to help, and they frequently make screen reader use worse rather than better. Accessibility here is built into the markup instead.

How it is tested

Every build runs an automated suite covering keyboard operation, focus handling, heading structure, contrast measured against the actual background, tap target sizes, horizontal overflow at ten screen widths, and reduced motion. Automated testing catches perhaps a third of real problems, which is why the list above admits what it misses.

Found a barrier?

Tell me and I will fix it. Email houston.dragna+site@gmail.com with the page and what got in your way. You will get a person, not a ticket queue, and I would rather hear about it than not.

In client work

The same standards go into what I build for clients: contrast-tested palettes, alt text written by a human, keyboard-tested builds. If accessibility matters on your project, say so early and it costs almost nothing. Retrofitted later, it costs a great deal.