Accessibility

Made to be usable for everyone.

Accessibility is part of doing the job properly — not a tick-box added at the end. Here’s what that looks like on this website, and what to do if I’ve missed.

What I’ve aimed for

This site is built to broadly meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That’s the standard most accessibility regulations in the UK and EU point to. In practice it means:

  • Keyboard-friendly. Everything you can do with a mouse should be doable with just the keyboard. Visible focus styles tell you where you are on the page.
  • Readable by screen readers.Headings are properly nested, images carry sensible alt text (or are marked decorative), and interactive elements use real semantics — buttons are buttons, links are links.
  • Readable by humans. Body copy meets the WCAG colour-contrast minimum in both light and dark modes. Line lengths and spacing are set to make long reading comfortable.
  • Responsive and resizable. The layout reflows down to small phones and up to large screens. Text can be zoomed up to 200% without breaking the page.
  • Motion-respectful. Animations are modest and respect your prefers-reduced-motion setting if you have one.
  • Theme. Light and dark modes are both supported and follow your system preference unless you override it.

What I can’t guarantee

Accessibility is a moving target. I test with keyboard, screen-reader spot-checks, and automated tooling on every meaningful change — but the web is full of edge cases, and I don’t catch all of them. If something doesn’t work for you, please tell me. That’s the most useful thing you can do.

Specifically I’d note:

  • Embedded third-party content (videos, maps) follows the accessibility of whoever’s hosting it. I’ll always pick the best option I’m aware of.
  • Some decorative SVGs and background visuals don’t have alternative text because they don’t add information — they’re marked aria-hidden so assistive tech can skip them.

If something isn’t working

Email me at hello@madebyjack.co.uk with what you were trying to do, where on the site you were, and (if you can) what device or assistive technology you were using. I’ll get back to you, and where the fix is on me I’ll do it.

For the sites I build for clients

The same standard applies. Every site I deliver is built to broadly meet WCAG 2.2 AA out of the box. If your project has specific accessibility obligations (public- sector, regulated industry, large-organisation procurement requirements), say so up front and I’ll factor in a formal audit and remediation.

Changes

I’ll update this page as the site evolves.

Last updated: 18 May 2026.

Back home