anon81750324:
ARIA labels are great for describing what is coming next to a screen reader. Often the common mistake is to fill out the ARIA label the same text as the title. It will just read this out twice because it’s the same text. I rarely recommend filling out Aria labels for things like the text component.
Where ARIA labels are useful is for things like Flip Cards. Filling out the ARIA label with something like ‘There are 4 objects to interact with, which will reveal more text when interacted with’. This tells the end user that they have to actually do something to read out the text on the other side. This is also good to have in an ARIA label as this might be different to instructional text, which would normally be something like ‘Flip over each card’ - This wouldn’t make a lot of sense someone visually impaired, as they don’t know how many things to flip over, or where the interactivity ends.
Indeed, Evolve will instruct the screen reader to skip this content if it doesn’t have an Aria label filled out - Make sure you check the help text on the ARIA labels for certain interactions.
Hi Evolve,
We’ve recently run into some issues with JAWS screen reader and ARIA labels, specifically on Mozilla. Just seeing if this is on the roadmap to be supported? Or, if there are any workarounds in the mean time?