Dominic Mazzoni

Use case: explore accessibility API for existing document

1

Existing web accessibility APIs are complicated and it isn't always obvious to web authors how declarative accessibility markup affects the actual accessibility properties exposed to clients via native accessibility APIs....

One of the major gaps in ARIA is that a custom control can't be manipulated via accessibility actions. For example, on almost all platforms, a native HTML slider can be...

Enabling "native" browser accessibility support has performance and memory implications. Simply setting or accessing the AOM should not do this. This needs to be clear in the spec.

Discourage authors from using role=none/presentation on table cells (and maybe list items)

3

# Describe your concern Someone tried to use role=none on a table cell, e.g. Name Subject Ranjit (no subject) Some browsers are removing the native table cell role. Others are...

Need an attribute for direct interaction elements on a touch screen

53

Screen readers with touch screen support typically include a "touch exploration" mode where you can tap or slowly drag around the screen and listen to feedback on what you're touching,...

[AriaNotify] Should notifications be HTML rather than plaintext or SSML?

4

It feels like a missed opportunity to invent a new API that's built around plaintext, or a speech-only markup language like SSML. I'm fine with not prioritizing braille in v1...

[AriaNotify] Should we first standardize live regions, and let ariaNotify can build on them?

2

It feels like ariaNotify is trying to solve two problems simultaneously: poor ergonomics of live regions for web developers, and inconsistent implementations in browsers and screen readers. Wouldn't it make...

## Bug Report 1. On macOS, enable VoiceOver and visit this page: https://bvaughn.github.io/react-virtualized/#/components/Grid 2. Navigate to the grid and interact in 3. Try to use VoiceOver+Up/Down to move up/down in...