Blog

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.

Foundations: landmarks

Posted on by Léonie Watson

Most websites have common areas of content like a header and footer, a main content area, and one or more navigation blocks. Sighted people can identify these areas based on the way they're styled and the content they contain, but people who are blind cannot do that quite as efficiently. Landmarks, like headings and lists, offer screen reader users a more comparable experience for identifying and navigating between these areas of content.

Foundations: session timeouts

Posted on by Patrick H. Lauke

Session timeouts are designed to protect privacy and security, but if they’re implemented incorrectly, they can prevent people from completing tasks on a website.

Foundations: headings

Posted on by Henny Swan

Well structured content helps everybody understand and navigate documents. When coded properly in the HTML, headings, lists, and landmarks help people who use screen readers (software that reads what’s on screen) both scan and navigate pages.

Contact us

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

hello@tetralogical.com