You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason we use the <span role="text"></span> was to deal with a VoiceOver 'feature' where it reads out 'chunks' of content if wrapped in separate elements. See https://axesslab.com/text-splitting/ for an explanation.
Unfortunately the role of 'text' is not a valid role value, hence why axe flags it as an issue.
However, we took the view in this case that we would prefer VoiceOver to read content out in a way that may not cause confusion so chose this method to do that, even though it is not valid.
There's also further discussion here from Deque about adding an exception for it: dequelabs/axe-core#1597
Bug Report
What is the issue?
We are using the Warning Callout component but Axe and Lighthouse both report an issue with the use of
span[role="text"]
Axe
Lighthouse
What steps are required to reproduce the issue?
What was the environment where this issue occurred?
The text was updated successfully, but these errors were encountered: