Accessibility of this website

What has been tested on this site, what passed, and the problems I know about and have not fixed yet. Last tested 6 October 2026.

This is a statement about this website, not about the audits I sell. I publish it because I tell clients that a missing accessibility statement is itself the first finding, and it would be a poor look to leave my own off.

Last tested 6 October 2026, by me.

What I tested

All 48 public pages on this site, which is every page, post, tag page and author page in the sitemap. Automated testing with axe-core against WCAG 2.0, 2.1 and 2.2 at levels A and AA, plus Section 508.

That returned no violations. 216 colour contrast checks came back undecided, which usually means text sitting over something the tool cannot resolve, so I measured those by hand with the alpha composited against the painted background. All of them pass. The tightest real margin on the site is 5.04 to 1, on the magenta buttons, against a requirement of 4.5.

I also checked keyboard focus order on the home page, the reading order and heading structure, and the accessible names of the dialogs and form fields.

What that does not mean

It does not mean this site conforms to WCAG 2.2 AA, and I am not claiming that it does. Automated testing reaches perhaps a third of the success criteria. The rest need a person, and some of them need a person who uses the thing being tested.

Specifically, I have not run screen reader speech output testing, I have not tested on a real mobile device rather than an emulated one, and I have not tested the reduced-motion behaviour at runtime even though the stylesheet carries it.

Problems I know about and have not fixed

This is the part that makes a statement worth reading, so here is the honest list.

  • Between about 500 and 1100 pixels wide, the site switches to the phone navigation. A tablet held sideways, or a browser window taking half a laptop screen, loses the header and the logo and opens straight on the page heading.
  • With JavaScript turned off, the navigation tells you which section of the site you are in but not which page you are on. With JavaScript running it tells you both.
  • Site search is forgiving about spelling, so a word that is nearly right still returns results. Where a word appears nowhere on this site at all, the result count now says which word that was, except when the query uses quotation marks or a minus sign.
  • The pricing tables crowd badly on a narrow phone. Rows grow very tall and some cells wrap to many lines.
  • The contents control on long articles sits close to the right edge of the text on a phone, and its touch target is smaller than it should be.

None of these stops anybody using the site, as far as I know. They are on the list to fix and this page gets updated when they are.

If something does not work for you

Email dean@deanfrankreynolds.co.uk and tell me what happened and what you were using. You do not need to know the technical name for it, and you do not need to be polite about it.

I will tell you whether it is something I can fix, and when. If it is something I cannot fix, I will say that instead of going quiet.

I am a wheelchair user and profoundly deaf, so email is the route that works. I do not take phone calls.