Wiki page to define a common language for screen reader specific modes and features

[spectranaut]

Including things such as reading mode/interactive mode and their names in different screen readers.

[mfairchild365]

For whatever it's worth, I have a start to this.

• mappings of common commands across screen readers:
  • HTML representation
  • JSON representation
• all of that is sourced from ATBrowsers.json

Its a little messy and incomplete, but perhaps a start.

[spectranaut]

Matt started this here: https://github.com/w3c/aria-at/wiki/Screen-Reader-Terminology-Translation

[carmacleod]

I found @ljwatson's post about screen reader interaction modes helpful (it is very old, but still helps explain the concepts). :)

[zcorpan]

I'm not sure whether to have common terms for different ATs, or if it's better to use the terms that are specific for the AT in question. For example, we have tests for VoiceOver that say they're testing "interaction mode", but @cookiecrook pointed out (#111) that VO doesn't have modes, so it's a bit inaccurate to have common terms when the ATs have different idioms or ways of operation.