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
Activate a screen reader, if you don't already have one running
Place the screen reader cursor on the demo button (labelled 'Click me')
Activate the demo spinner button
Wait a bit, long enough to each both the 'The async action is busy' and 'The async action is complete' announcements
Navigate to the two previous DOM elements using your screen reader (e.g. VO + Left Arrow, or Up Arrow on NVDA).
Observed outcome
You will hear 'The async action is complete' as you navigate the DOM element by element.
This can be confusing, as the action has completed long ago. The announcement is now heard out of context and might create confusion.
Observed with:
MacOS 10.14 (Mojave) + VoiceOver + latest Safari
MacOS 10.14 (Mojave) + VoiceOver + latest Chrome
Windows 10 + latest Chrome + latest NVDA
Expected outcome
I expected to not hear a 'the async action is complete' announcement out of context, when traversing the DOM with a screen reader, long after I've clicked a button.
Suggestion
I imagine that it'd be an improvement to empty the content of each live region 500ms or so after they have been populated, so they don't stay populated in the DOM.
The text was updated successfully, but these errors were encountered:
First, thanks a lot for publishing TenonUI. It's been a fantastically helpful learning resource for me.
I've noticed a small issue with the SpinnerButton.
Steps to reproduce
Observed outcome
You will hear 'The async action is complete' as you navigate the DOM element by element.
This can be confusing, as the action has completed long ago. The announcement is now heard out of context and might create confusion.
Observed with:
Expected outcome
I expected to not hear a 'the async action is complete' announcement out of context, when traversing the DOM with a screen reader, long after I've clicked a button.
Suggestion
I imagine that it'd be an improvement to empty the content of each live region 500ms or so after they have been populated, so they don't stay populated in the DOM.
The text was updated successfully, but these errors were encountered: