Adrian Roselli

> In Firefox, JAWS also recognizes the cells as empty. But a JAWS bug causes empty cells in tables to be skipped, which is analogous to https://github.com/FreedomScientific/standards-support/issues/403 Testing empty cells...

> The cells are also empty for JAWS in Firefox, which is easy to check when navigating through the table using only the arrow keys. I think I understand the...

See #29 for why limiting to these roles can limit further implementation risks and challenges.

@jackbsteinberg > They have also been providing the best results in screen reader tests, including tests of existing toast patterns on the web. Can you share the screen reader testing...

@jackbsteinberg To quote myself from above: > Can you share the screen reader testing results and materials?

@domenic > Did you see the research? https://github.com/jackbsteinberg/std-toast/blob/master/study-group/. It turns out it's quite common for toasts to have at least a close button, and often an action button. I did....

@jimkeller I think the interaction itself is not the limiting factor. Check how the [dialog role](https://www.w3.org/TR/wai-aria-1.2/#dialog) is defined: > A dialog is a descendant window of the primary window of...

@jackbsteinberg > * The action and close buttons within the toast (if they exist) are the next two elements in the tab order Big red flag here. Are you suggesting...

I think #25 also addresses a) above. ARIA has defined the standard set of types. For new patterns that emerge / have emerged since, then they will need to have...

@jackbsteinberg > Assertive types such as `error` and `warning` could use `role=”alert”`, and polite types such as `info` and `success` could use `role=”status”`. Other solutions could involve creating new ARIA...