-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A11y Audit - Screen Reader Testing #4194
Comments
Sample 1 - Article OLH Theme but with article for download only.using iOS Safari and Voiceovertraversing from top to bottom of page.
Safari on MacThese are only notes problems not already described.
|
Sample 2 - Article in Material Themeusing iOS with Safari and Voiceovertraversing from top of page to bottom
|
Sample 3 - Article in Clean Themeusing ios with safari and voiceover
|
Sample 4 - Article in OLH theme (full article displayed on page)This has been written with reference to sample 1, only adding in differences (not identified before, or different behaviour).
|
Sample 5 - Non-article pagesignoring navigation, header/footer etc if already appears on article sample. Looking for other content not yet tested. 5.1 OLH - homepage
5.2 - Material homepage
5.3 - Clean homepage
|
Other Observations
|
The results here are now integrated into the rest of the audit. |
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
The text was updated successfully, but these errors were encountered: