WCAG posts
WCAG 3: a different future for accessibility
Did you know that when given a minimum payment threshold, people pay off about 70% less from their credit card than they would have done without it?
The minimum payment doesn't change the number of people who pay off their full outstanding balance, but it dramatically changes how much everyone else chooses to pay.
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.
Designing for people who are colour blind
Colour blindness can get overlooked in accessible design, but it can have a significant impact on how people access the web, making it harder to notice important information, distinguish interactive elements, or understand data that relies on colour alone.
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.
Introduction to creating accessible documents
Digital documents and book files are a core part of our everyday communication. When documents aren’t accessible, they can exclude people with disabilities from integral learning, information, and content. Publishing accessible documents and book files ensures we can communicate the same information to people with disabilities, making this content accessible to everyone.
Designing for people who are blind
When designing products and services, we often think in terms of their visual appearance. However, some people use digital content without being able to see it. This means we need to design interfaces that remain understandable, navigable, and controllable even when people are unable to perceive layout, colour, and spatial clues.
By doing so, we ensure designs provide a comparable experience so that people who are blind can complete tasks in a way that suits their needs without undermining the quality of the content.
Designing for people with low vision
Low vision affects millions of people worldwide, yet it's often overlooked in the design process. The design choices we make, from how we emphasise content to where we position controls, can either empower people to customise their experience or create unnecessary barriers. By understanding these impacts and designing with flexibility in mind, we can create interfaces that truly work for everyone.
Designing for people with anxiety
Most of us will experience anxiety at some point, sometimes triggered by a stressful moment, other times as a chronic condition. By taking thoughtful, intentional steps, we can ensure our designs at the most reduce stress, and the very least, do not contribute to or amplify it further.
Designing for people with disabilities
At the heart of inclusive design are people. Not technology, and not standards. Technology is what people use, and standards provide a foundation for access, but inclusive design is shaped by real use, not rule sets.