Design and development posts
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.
When to use tabindex='0'
When tabindex="0" is applied to an HTML element, the content marked up using that element will become keyboard focusable, and is therefore a good starting point for supporting keyboard accessibility. However, applying this attribute haphazardly or unnecessarily can reduce the experience for people who use a keyboard or an equivalent input device to navigate web content.
Accessibility foundations
Our foundations series provides an overview of core accessibility considerations.
They are a good starting point for visual designers, content designers, interaction designers, and developers when designing and building accessible products and services.
Can generative AI help write accessible code?
Like many inventions before it, Generative AI is changing the way we do things. Like those inventions that went before it, Generative AI is capable of great good and great harm, and like the humans that used those inventions before us, we need to be smart about the way we use Generative AI.
Keyboard accessibility myths and WCAG
Supporting keyboard-only interaction is one of the most important principles of web accessibility. However, the scope of the Web Content Accessibility Guidelines (WCAG) in relation to keyboard accessibility is often misunderstood.
Considerations for TV user interface accessibility
TVs, set-top boxes and streaming devices are a huge part of all our lives and should be accessible so everyone can watch what they want, when they want, how they want.
We've started exploring challenges people with disabilities may face when interacting with TV apps and considerations for people designing and developing TV app interfaces.
Sticky content: focus in view
Sticky content helps prioritise important content so it's always visible, but it can create issues for sighted people who use a keyboard, or a keyboard-like device, as focused controls become hidden behind the sticky content.
This post discusses how you can keep controls behind sticky content visible and usable when they receive focus.
Meeting WCAG Level AAA
In this post, we cover updates we've made to our own site in order to better satisfy the requirements of the Web Content accessibility Guidelines (WCAG) 2.1 Level AAA.
Foundations: accessible names and descriptions
An element's name, or accessible name, is how it's identified. An accessible description provides additional information, about the element, that complements the accessible name.
In this post we explore assigning accessible names and descriptions using HTML and WAI-ARIA.
Inclusive XR: accessible augmented reality experiences
In our second post about creating accessible experiences within Extended Reality (XR), we highlight some key considerations for designing accessible augmented reality (AR) experiences with our AR TetraLogical principles cube.
You can also explore Inclusive XR: accessible 3D experiences.