Skip to content

A11y Audit - Screen Reader Testing #4194

Description

@StephDriver

Context

Manual Testing of a sample of pages for screen reader capacity. This is for functionality, not user experience. The aim is to identify 'low hanging fruit' issues which can be addressed before future more exhaustive testing including direct user feedback.

Testing is non-exhaustive.

[edit] It was going to include multiple OS and browsers, and several different journals, with the first tests on iOS Voiceover on Safari because that's the one I know the best so I am more likely to catch such issues and reduces lead time on training on a new system. Early results from this after 2 sample articles show that the many of the errors identified are then clearly visible in the code. They are not 'I wonder how a different screen reader would handle this' but rather 'this heading should be an H5 instead of an H4' which would affect all users/screenreader softwares. So this exercise has been revised: it will be a representative sampling just with iOS Voiceover, then after the identified issues have been addressed, we will have another go at the original plan for testing with multiple different screen readers, browsers etc.

Approach

Metadata

Metadata

Assignees

Labels

a11yIssues that relate to acessibilityauditan inspection or deliberately search for issues.

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Done

Relationships

None yet

Development

No branches or pull requests

Issue actions