Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Map to Existing Roles #25
ARIA 1.2 contains roles that do not have native HTML counterparts, as outlined in 2.14 Aria roles and properties not available as features in HTML. A collection of roles that may apply to this proposal:
Each of these roles identifies how it is exposed to the accessibility APIs and what states and properties they should expose.
For any of these roles that you feel applies to the proposed toast element, then you may want to mint attributes to indicate which (eg:
At the very least, a native toast implementation should look to adopt one or more of these roles and follow the interactions already defined in the ARIA specification.
This was referenced
Jun 14, 2019
Thank you for creating an issue to discuss these, this has been really helpful for the accessibility research which is currently our highest-priority task.
After exploring these roles, the specs for
Can you share the screen reader testing results and materials?
How did they provide the best results? Discoverability? Verbosity? Were the users skilled screen reader users? How did you recruit these users? What screen readers? What browsers? How were the tests structured? How did you measure success? How was the pattern implemented? …?
Having done research with users for years, forgive me if I am wary of trusting results without an opportunity to review the methodology, materials being tested, and final results.
i'm quite curious as to how
neither of which (a timing countdown, nor a live region that is not announced by default) being common expectations for a visible pop up message that is meant to communicate a small bit of information without interrupting a user's current action.