Simon Pieters

I think accname should either have a general language-agnostic algorithm with clear hooks for each language to define the relevant steps, or accname should just contain everything (HTML, SVG, what...

I think an important aspect is that the special modifier key is configurable for some screen readers.

From today's AT Automation Working Session, @jscholes and @mcking65 think we should first specify: For each AT: - Enumerate all available settings - Get one setting's value - Set one...

Thanks @straker > the information is already available via browser developer tools; and But you can't use that to infer anything about the spoken output from this API. For example,...

It's indeed async and output would be events in the protocol. I don't know if screen readers are able to keep track of cause and effect between pressing a key...

> > enunciate punctuation > > This is quite a complex setting, so we'll need to scope out exactly what we want/need here. E.g. different screen readers have different predefined...

I've edited the milestones in OP to reflect our current thinking. In particular: - Milestone 1, settings, are now vendor-specific and can include all settings (except any to exclude for...

Based on our conversation in the CG meeting yesterday ([minutes](https://www.w3.org/2022/08/15-aria-at-minutes.html)), I think we should make the following adjustments to the roadmap: - Milestone 4: Activate commands - Milestone 5: Headless...

The text content of an element with `role="time"` (when not the `time` element with a `datetime` attribute) is a *machine-readable* time, which is often not what you want to present...

OK, filed #2320