Our Blog

Extended Reality (XR) experiences tend to focus on providing immersive sounds and directional audio to convey information. But we need to consider how we convey the information in these experiences to people who can’t hear them.

Extended Reality (XR) experiences tend to focus on providing rich, visual content to convey information. But we need to consider how we convey the information in these experiences in a way that isn’t overwhelming, scary, or difficult to understand.

Extended Reality (XR) experiences tend to focus on providing rich, visual content to convey information. But we need to consider how we convey the information in these experiences to people who can’t see them.

Extended Reality (XR) provides immersive experiences through detailed visual, audio, and multi-media content. When using these different types of content, we need to consider how we can communicate the same information to people with disabilities in order to make XR accessible to everyone.

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.

The ARIA Authoring Practices Guide (APG) contains an extensive range of design patterns aimed at helping developers to create accessible web experiences using WAI-ARIA. However, while we encourage web authors to follow these design patterns, a common misconception is that their usage is a prerequisite for conformance.

This is not the case.

A big question for many organisations is if WCAG 2.2 applies to native apps. In this post we explore what does and doesn't apply.

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.

Accessibility isn't solely important in the final product; it's crucial at every step of the process. Adopting accessible practices from the outset unlocks your team's full potential. This approach not only improves the products you create but also nurtures a culture of inclusivity within your organisation and means your team will more accurately reflect the diversity of your customer base.

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.