Code posts
Introducing the Accessible Components Library
We've open-sourced our Accessible Components Library, and, as you might expect, this includes the HTML, CSS, and JavaScript code. But, we thought, "Why stop there?" So, we've also published our documentation, including the accessibility requirements, test scenarios, and even the working automated tests which validate each one.
Foundations: the accessibility tree
There's a common misconception that when browsing the web using a screen reader, it's reading the actual screen. This is not really surprising, as the name suggests that's exactly what it's doing. And, this is what early screen readers did, so, we can't really blame anybody for thinking that!
Should native app screen titles be headings?
Many screens in native apps include a screen title that summarises the contents of the screen, but these titles are often not identified as headings to screen readers. In this post, we look into some of the reasons why this might be the case, and why this is an example of the challenges involved in applying WCAG to native apps.
Accessible building blocks for the web videos
By applying accessibility considerations to the building blocks of your web content you can create digital products that everyone can use.
Our Accessible building blocks for web video series introduces key accessibility considerations for some of the most widely used elements on websites - from headings to images, links, buttons, and form fields.
Screen reader HTML support tables
With the addition of Gez Lemon to the editing team, work continues on expanding and improving the HTML and screen reader support information.
Foundations: Keyboard accessibility
By prioritising semantic HTML and offering keyboard-friendly alternatives for complex interactions, you help create a more inclusive experience for people who use a keyboard.
Foundations: grouping forms with <fieldset> and <legend>
In this post, we explore how to use the <fieldset> and <legend> elements to group and label form elements effectively, creating a more accessible and well-structured experience.
Foundations: form validation and error messages
As well as labelling text fields with input and labels, and grouping forms with the <fieldset> and <legend> elements, form validation and error messages are also essential to making forms accessible to everyone.
Foundations: labelling text fields with input and label
In this post about forms, we explore how to effectively label text fields using <input> and <label> elements to create form inputs that are both accessible and user-friendly.
Why are my live regions not working?
Live regions have a reputation for being "flaky" and inconsistent. While this can be attributed in part to shortcomings in current implementations, the problem can also be caused by developers misunderstanding how live regions are intended to work.
