James Scholes
James Scholes
> “Insure NVDA is in browse mode by pressing Escape. Note: This command has no effect if NVDA is already in browse mode.” See https://github.com/w3c/aria-at/issues/382.
> The note is incorrect if focus is in a widget that processes escape, such as a dialog or menu. In those circumstances, the web page will receive the escape...
We currently believe NVDA+Space to be the only suitable method for testers to verify that browse mode is active, and nobody on the Feburary 4th community group call had any...
Assigning this to myself, to propose some language for the test pages to be reviewed by the community.
A few thoughts about proposed language for this issue. At present, NVDA users are instructed to activate focus mode for "interaction mode" tests as follows: > If NVDA did not...
Raised during the September 23 CG meeting, in terms of: 1. the instructions referring to "focus mode" rather than "interaction mode" which may feel a bit inconsistent; and 2. users...
@s3ththompson It is easier to manually convert a Windows path to a POSIX path by hand, than trying to manually create a file URI. I.e. if a member of the...
Decisions from August 4 CG meeting: * Provide instructions to testers about how to configure their Windows screen reader to announce mode changes, instead of playing a sound. * Update...
@RFischer-FS Thank you for reporting this issue. We're investigating and will provide an update soon.
@RFischer-FS All test pages should now be operable. Please let us know if you find any "open test" links that continue to result in a 404 error.