A11y

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…

Outlines the current principles and work needed to improve the accessibility of the GOV.UK Design System

Discover beautiful color combinations your whole audience can appreciate with the click of a button. Try our free accessible color palette generator today.

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

TL;DR: Description list support is generally good (with Safari being the outlier), even if you may not like how it is supported. This post builds on my 2020 tests when iOS 14 finally added (partial) support for description lists (VoiceOver on iOS 14 Supports Description Lists). The dl has existed…

There seems to be a confusion about the relationship and how to test for the WCAG 2.1 Success Criteria 1.4.4 Resize Text and 1.4.10 Reflow. While these two success criteria seem related, they cover different use cases.

On the downsides of constraining content through CSS.

As a follow up to my previous post about common accessibility issues, I have written out five more issues that you could fix today.

Gets information for WCAG 2.1 criteria based on a reference number. - abbott567/wcagify: Gets information for WCAG 2.1 criteria based on a reference number.

This article is the second of two parts about a guide to making websites accessible to keyboard users. Here Cristian Diaz covers a toolset on JavaScript that you can mix into different components to create a great experience for keyboard users.

Automated web testing, especially at an integration level, saves time, money and effort. It ensures...

My notes for making the web more inclusive.

In this article, Cristian Diaz covers how to use HTML and CSS to create an accessible experience for keyboard users while mentioning what WCAG criteria we should keep into consideration.

A complete guide to WCAG 2.0 contrast accessibility requirements and contrast tools with examples to help you apply it to your own website.

An open letter about accessibility overlays.

Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.

Some common patterns that stood out to me during usability interviews with frequent screen reader users.