-
Notifications
You must be signed in to change notification settings - Fork 5
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
Content and screen readers research #305
Labels
content
Goes into the 'Content' section of the service manual
Comments
sarawilcox
added
the
content
Goes into the 'Content' section of the service manual
label
Jan 22, 2021
Service manual team is meeting with Alistair for an initial discussion on 3 Feb. |
Some testing pages here for screen readers: |
Details of discussions and next steps are recorded in the issues for the components noted above. I'm going to close this ticket t avoid duplication. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What
We'd like to test various content scenarios on screen readers, share findings and make decisions based on that. For example, identifying if screen reader users experience any issues with hyphens and dashes or pronunciation.
Why
We don't know to what extent different content scenarios cause screen reader users problems. Broadly speaking, the advice we've had is not to change what's grammatically correct in order to cater for screen reader users. There are several reasons for this.
However, we don't know for certain whether there are any content style areas where we could provide a better experience for screen reader users.
Related issues
The text was updated successfully, but these errors were encountered: