Forum Discussion
Screen reader issue with tab blocks
Hi Sasha! Thanks for reaching out!
I cannot reproduce the behaviour you described with the phrase "DOCUSIGN USE CASE MAP TOOL". Voice Over does announce "Docusign" as a word and not spelled out. I made screen recordings for you just in case I'm missing anything that you can point out.
VO + Safari Test
JAWS + Chrome Test
NVDA + Edge Test
In the meantime, thank you for sharing your research regarding the CSS property "text-transform". I don't have much experience with CSS interfering with screen readers in particular, but your sample proves it may influence it. It does, however, seem to be an edge case for Voice Over having problems with some words, like "Add", in the context of using the CSS property text-transform in the example. This property intends to separate the visual presentation (displaying as uppercase) while maintaining its semantic meaning in the HTML, which works quite well across various screen readers. I made recordings if you are curious.
VO reading html buttons (in this recording I'm showing the source)
JAWS reading html buttons
NVDA reading html buttons
There could just be some off words with Voice Over, but I did not encounter a problem with the word "Docusign". Will be waiting for your reply!
Cheers!
Marvie