w3c / at-driver

AT Driver defines a protocol for introspection and remote control of assistive technology software, using a bidirectional communication channel.
https://w3c.github.io/at-driver
Other
31 stars 4 forks source link

Feedback on additional requirements, mode semantics, and formatting #1

Closed s3ththompson closed 2 years ago

s3ththompson commented 2 years ago

Feedback from @jscholes, copied from email:


After an initial read-through, I would add the following to the "Requirements" section:

  1. Start screen reader
  2. Quit screen reader

Under the "Configure screen reader" section, the example is listed as 'the "mode" in which it should start'. I would consider this more under the umbrella of "Configure screen reader testing conditions"; configuring a screen reader is more about setting certain explicit options like: instructing NVDA and JAWS to convey mode changes in speech instead of via sound files.

In the same section, 'the "mode" in which it should start' is a misnomer, because modal screen readers don't start in a particular mode. Indeed, outside of web content, reading/interaction mode doesn't really apply at all, and the default focus position on Windows is usually the taskbar or similar. It would be more unambiguously worded as, 'the "mode" which should be active before a particular test command is executed'.

In the "Fake key presses and intercept spoken output" section, "Pros:" and "Cons:" should probably be headings.