Research insight: accessibility of images

Posted on by Henny Swan

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 the team: Léonie Watson

Posted on

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.

Android accessibility: roles and TalkBack

Posted on by Graeme Coleman

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).

Accessible design systems

Posted on by Henny Swan

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 the team: Patrick H. Lauke

Posted on

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.

Inclusive user research: analysing findings

Posted on by Ela Gorla

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.

How to write user stories for accessibility

Posted on by Leon Hampson

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.

Triaging WCAG 2.1 Level AAA

Posted on by Ian Pouncey

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?

Foundations: lists

Posted on by Léonie Watson

A list is generally agreed to be a series of words or phrases that are grouped together for a reason. That reason might be to remember the items we want from the store, to share our top five favourite movies, or to write down the steps needed to complete a task.

The business case for accessibility

Posted on by Felicity Miners-Jones

In an ideal world, products and services would be designed so that every person experienced them in an equitable and comparable way. However, sometimes it is necessary to justify to stakeholders why the proper time, money, and resources need to be dedicated to embed accessible practises.

Contact us

We like to listen. If you have a project, product, problem, or idea that you want to discuss, get in touch!