Blog

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.

Foundations: colour and meaning

Posted on by Henny Swan

Colour is a valuable tool for communicating meaning. But if you can't see colour, then meaning is lost. Always plan to use colour to convey meaning in combination with another means of identification.

Foundations: colour contrast

Posted on by Henny Swan

Good contrast is about using colours that provide enough variation between the content and background. This is particularly important for people who have conditions that affect vision or colour perception, as well as people browsing on mobile in different light conditions.

Foundations: text descriptions

Posted on by Henny Swan

Text descriptions are primary content, and when images do not have a text description, anyone who cannot see the image will not know its purpose. This means people may be unable to access content or perform related tasks.

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