Theme

Accessibility Statement

Last updated:

Daveden Digital Ltd is committed to making this site usable for as many people as possible. Accessibility is part of what I teach, so it's a baseline expectation here — not an afterthought. This statement explains the standard I aim for, what I know works, what I know doesn't, and how to tell me when I've missed something.

The standard I aim for

This site is designed to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Where I can reach AAA on a specific success criterion without compromising legibility or content, I do.

How the site is built

  • Semantic HTML landmarks (header, nav, main, footer) on every page.
  • A skip link as the first focusable element.
  • Logical, predictable heading order on every page.
  • Visible two-tone focus indicators on all interactive elements, designed to stay visible against light and dark backgrounds.
  • Light and dark colour themes, both meeting the WCAG AA contrast minimum (4.5:1 for text, 3:1 for large text and non-text UI).
  • Keyboard support across all interactions — including the menu dialog, theme toggle, and contact form.
  • No motion that runs automatically; animations respect prefers-reduced-motion.
  • Form fields have programmatic labels, error messages are announced via aria-live, and validation hints are linked with aria-describedby.

Conformance status

At the date above, I am not aware of any WCAG 2.2 AA failures on the pages I author and template directly. Older blog posts may contain edge cases — see the limitations below.

Known limitations

Some content is more accessible than others. The areas I'm actively improving:

  • Older blog images. A small number of pre-2023 posts have images with weak or missing alternative text. I'm working through them in date order.
  • Embedded video. Videos hosted on YouTube use YouTube's player, which has its own accessibility behaviour. Captions are available on the channel; if a specific video is missing captions, please tell me and I'll prioritise it.
  • Code snippets. Long code blocks scroll horizontally on narrow screens. They are focusable and announced as scrollable regions, but I'm exploring softer wrap behaviour for prose-heavy posts.

Tested with

I check the site regularly with:

  • Keyboard only, on macOS Safari and Firefox.
  • VoiceOver on macOS Safari; NVDA on Windows Firefox.
  • Browser zoom up to 400%.
  • Automated and structural checks: axe DevTools, Lighthouse, Accessibility Insights for Web, and the HeadingsMap browser extension for heading-order audits.

Testing is carried out on an ongoing basis. Results and known limitations are reflected in this statement as they are identified.

Feedback and reporting issues

If something on this site is hard to use — even if it doesn't fail a specific WCAG criterion — I want to hear about it. Two ways to get in touch:

I aim to respond within five working days.

Enforcement

If you contact me about an accessibility problem and you're not satisfied with the response, you can raise a complaint with the Equality Advisory and Support Service (EASS).

About this statement

This statement was prepared on 19 July 2026 and is reviewed at least once a year, or whenever the site undergoes a substantial redesign.