jonas.splinter
Search
Topic

Accessibility

Making websites usable for everyone, guided by WCAG: readable contrast, clear keyboard focus and layouts that work on any screen, in my own projects.

Web accessibility means that people can perceive, understand, navigate and use a website whatever their abilities or the way they browse: with a keyboard instead of a mouse, with a screen reader, with enlarged text or on a small phone. The Web Content Accessibility Guidelines (WCAG), developed by the W3C's Web Accessibility Initiative, are the international standard for it. The guidelines are organised under four principles: perceivable, operable, understandable and robust. Each one comes with testable success criteria at three levels, A, AA and AAA.

In my own work it mostly comes down to details. In November 2026 Blockspot got a design and accessibility sweep: buttons got readable contrast, dark mode was polished, keyboard focus became clearer and phone layouts stopped zooming or overflowing. The rebuilt Automate & Tweak site scores at or near the top in Lighthouse for accessibility and has a skip-to-content link, so keyboard users can jump straight past the navigation.

Accessibility overlaps a lot with good design and with SEO: clear headings, descriptive link text and a sensible page structure help screen readers and search engines alike. Automated checks such as Lighthouse catch only some issues, though. Moving through a page with the Tab key and watching where the focus goes shows problems that no score reveals.

2 blog posts

Longer articles about Accessibility

1 update

About Accessibility, from jsplinter.nl only

jsplinter.nl

New post: measuring accessibility after a redesign

New

I measured the redesigned site against WCAG 2.2 AA instead of trusting my eyes. The post covers what failed, how I fixed it while keeping the design, and what to check first.