Issue metadata
Sign in to add a comment
|
JAWS does not read the contents of tab-modal dialogs when they appear |
||||||||||||||||||||
Issue descriptionVersion 69.0.3447.3 (Official Build) canary (64-bit) Version 68.0.3440.7 (Official Build) dev (64-bit) JAWS Version 2018.1805.33 ILM NVDA version 2018.1.1 Windows version 1709 (OS Build 16299.431) Steps: 1. Launch JAWS. 2. Launch any of above versions of Chrome 3. Navigate to any page with an edit area, such as http://www.google.com 4. Navigate to the edit box, and press applications key or shift+F10 to open context menu. 5. Use arrow keys to find spellcheck menu, then press right and select ‘Ask Google for suggestions’. Expected: JAWS should read the contents of the dialog describing the feature. Actual: JAWS reads the title of the dialog, then announces the first button in focus. Notes: Reproduces in Canary and Dev Reproduces with JAWS, does not reproduce with NVDA. The current workaround is to invoke the read dialog and controls command (JAWS key +B).
,
Aug 7
,
Aug 7
,
Sep 18
,
Sep 18
,
Sep 18
,
Sep 18
,
Sep 18
Issue 849910 has been merged into this issue.
,
Sep 18
This needs to be fixed for (at least) all tab-modal dialogs. These include (not comprehensive): - Resubmit form - HTTP Auth - JS Alert - Sign in - Credit card CVC confirmation - Cookies (security chip > cookies) - share your screen - create shortcut - Add extension (via a page, not webstore) - Print - Cast - Review payment - WebAuthN JAWS+B reads the contents of the dialog; it should be read when it first appears. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Jun 1 2018