Testing posts

A big question for many organisations is if WCAG 2.2 applies to native apps. In this post we explore what does and doesn't apply.

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.

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?

These 10 quick accessibility tests can help you understand how easy or difficult it is for people with disabilities to perceive, operate and understand content on your website or mobile app. The tests are helpful for anyone wishing to get an idea of a product's support for accessibility, including project managers, content editors, procurement managers, and many others.

All user research projects should include people with disabilities. Representing at least 15% of the world population, according to The World Bank, and potentially your target market, it doesn't make sense to exclude them. This post provides user researchers with tips on how to best moderate usability testing sessions where participants have a disability.

In our second post on WCAG 2.1 Level AAA, we discuss how to test against various Level AAA success criteria. You can read about the benefits of Level AAA and when to consider including Level AAA Success Criteria in our first post, Understanding WCAG 2.1 Level AAA, and what to do with your test results in our third post, Triaging WCAG 2.1 Level AAA.

An Accessibility Conformance Report (ACR) is a document that formally summarises the extent to which an information and communications technology (ICT) product or service conforms to an agreed set of international accessibility guidelines and standards.

This article gives an overview of what an accessibility assessment is, when it is beneficial, and when another service such as an Insight Report may be better suited.

When a website is assessed using the Web Content Accessibility Guidelines (WCAG), it is rarely feasible to test every single page. Instead, the assessment can be based on a sample of pages that are representative of the website as a whole, to keep things as efficient and cost-effective as possible.