A11y

Designing for the colorblind doesn’t have to be difficult. And best of all, designing with the colorblind in mind will also improve your design for everyone

This is the 18F Accessibility Guide.

How usable are the new success criteria in WCAG 2.2: How understandable, teachable, testable are they and how much positive impact do they have?

Now that it is a market differentiator to talk about accessibility in projects, that’s all many do — talk about it. In a sea of pop-dev noise, “accessibility” can be claimed with little risk someone will challenge it. If someone does, the response is often a fine balance between silence…

A long time ago (2008) I wrote an article: Screen Readers lack emphasis. At the time, 15 years ago, the screen readers tested did not signify the semantics of text […]

Default description English

When our CSS contains Dark Mode rules and the file fails to load, we’re left with plain old HTML. Luckily we can request Dark Mode in our markup!

A bug with link text colours in Safari’s HTML-only Dark Mode theme means we need a bit of extra code. Here’s how to patch things until it’s fixed.

There’s a commonly held idea that HTML is accessible out of the box, before any CSS has been applied. Unfortunately, that isn’t quite the case.

In this webinar you’ll learn how and why semantic HTML helps screen reader users browse your website, whilst being mostly transparent to people who do not us...

Understanding how people with disabilities browse the web using assistive technologies (AT) is core to making an accessible and inclusive user experience. In...

Type-Ahead, Autocomplete, Autosuggest — die Combobox hat viele Namen. Wir erläutern die barrierefreie Umsetzung fürs Web nach ARIA 1.2.

Es gibt einige Websites, die ein Siegel zur Barrierefreiheit aufweisen. Und seit einigen Jahren gibt es für alle Webangebote aus dem Öffentlichen Dienst (und zwar für allen Webangebote aller staatlichen und kommunalen Stellen aus ganz Europa!) sogar die Pflicht, eine Barrierefreiheitserklärung vorzuweisen. Mit einem Siegel und einer Barrierefreiheitserklärung soll aufgezeigt…

A beginner's guide to digital accessibility.

ARIA roles and attributes can make your website more accessible, if you know what you're doing.

In this first Deep Dive into Accessibility APIs installment, we'll start from absolute scratch and recount the widely available basic story. It's written for beginners, but the fact that I describe web accessibility in the broader context of software accessibility might offer a different twist for current practitioners as well. Parts 2 and 3, on the other hand, are more technical. Although those discussions may largely be of interest only to "inquiring minds that want to know", understanding the history and variety of the specialized protocols at the heart of this process sheds light on why screen readers sometimes perform differently in the same application or on the same web site while also providing a glimpse of a likely future.

It's a lot. It's tempting to pretend we didn't read that very confronting article telling us we need to Do Better.

A collection of bad practices in HTML, copied from real websites.

Accessibility can be a daunting field to dive into. Following best practices and using automated tools will get you a long way, but stepping into the shoes of your users will give you perspective and knowledge that can only be gained firsthand.

Each person on your team have their own responsibilities to deliver accessible websites.

There is a non-zero chance that WCAG Success Criterion 4.1.1 Parsing will go away in WCAG 2.2. This isn’t a problem for users, regardless of the problems it may pose for the WCAG process, ACT rules, automated testing tools, or ossified testing processes. The joke here is using an antique…