Blog

Quick Response (QR) codes are graphics that can be scanned to direct people online to complete an action or find content. This blog post explores considerations and provides guidance for creating accessible experiences with QR codes.

One of the most important and challenging aspects of running inclusive user research is finding participants with a wide range of access needs, who can provide feedback on different features of your products. Our third post from the Inclusive user research series answers key questions around recruitment.

When conducting usability testing with disabled users, we observed how well images performed from both a visual and non-visual perspective when it came to finding and understanding content.

Meet Léonie Watson. Our purple-haired maverick was TetraLogical's founder back in 2019 and has guided this accessible ship through an incredible amount in such a short time.

TalkBack only announces role information for a relatively small number of user interface (UI) elements within native apps. When comparing this behaviour against web content, this can often give the (false) impression that these elements must have been coded incorrectly and therefore need to be "fixed".

This blog post looks at when it is acceptable for a role not to be announced, the roles that TalkBack does announce, and what this means for conformance to the Web Content Accessibility Guidelines (WCAG).

A design system is a library of styles, components, and patterns used by product teams to consistently and efficiently launch new pages and features. A good system has accessibility embedded throughout and includes documentation, guidelines and implementation notes for accessibility.

Meet Patrick H. Lauke, he's a technical wiz, passionate advocate and all-round expert in the world of digital accessibility. Here he shares his favourite resources and tips for those starting out.

In moderating usability testing with people with disabilities we covered the skills and techniques that help researchers run sessions smoothly and collect valuable insights. The second post in our Inclusive user research series discusses some of the unique challenges posed by findings from sessions run with people with disabilities, and advice on how to analyse them.

A user story usually focuses on the value a software feature will deliver to an end-user, and an accessibility user story is no different. Whether you need to write an accessibility user story to fix issues found in an accessibility review, as part of a business case, or as part of your service delivery plan, there’s not much that you need to do differently.

If you've taken the time to understand WCAG 2.1 Level AAA and have spent time testing WCAG 2.1 Level AAA, what do you do with the results?