Content and screen readers research

[sarawilcox]

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.

• Different screen readers announce punctuation in different ways, and users have control over how punctuation is announced. This means you don’t know how someone will experience your punctuation.​
• Some screen reader users listen incredibly quickly so punctuation will sound very different.​
• Screen reader users will be used to hearing how hyphens, for example, are announced on there particular screen reader(s).
• Screen reader users are able to go back to and interrogate a word or punctuation that they haven’t understood.

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

• components and headings
• the inset text issue
• the pronunciation issue
• hint text
• hyphens or spaces

[sarawilcox]

Service manual team is meeting with Alistair for an initial discussion on 3 Feb.

[mcheung-nhs]

Some testing pages here for screen readers:
https://github.com/mcheung-nhs/accessibility/tree/master/docs/tests

[sarawilcox]

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.