New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 649138 link

Starred by 6 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

JAWS screen reader announces page title instead of modal document title

Reported by emily.se...@pearson.com, Sep 21 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
0. Open JAWS screen reader
1. Go to Bootstrap modal sample page: http://v4-alpha.getbootstrap.com/components/modal/#live-demo
2. Open sample modal via "Launch demo modal" button
3. JAWS announces "Modal title dialog" (this is expected)
4. Press arrow down to go to next element
5. JAWS announces "Modal dot Bootstrap document"

What is the expected behavior?
Either simply announce "document" or provide a more accurate title.  In Firefox, JAWS simply announces "document."  Or support aria-labelledby on role=document in order to set a more descriptive label for the document.

What went wrong?
It is confusing to announce the modal document this way because the title of the entire document is "Modal . Bootstrap."  But now I need to know that I am within a document that is within the modal.

Did this work before? N/A 

Chrome version: 53.0.2785.116  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0
 

Comment 1 by nek...@chromium.org, Sep 22 2016

Cc: lpalmaro@chromium.org dmazz...@chromium.org
Components: -UI UI>Accessibility
Owner: nek...@chromium.org
Status: Available (was: Unconfirmed)
Labels: NewComponent-Accessibility-Compatibility
Labels: NewComponent-Accessibility
Able to reproduce the issue with following snippet:
<head><title>My Page</title></head>
<body><p>Page start</p><div role="document">document start</div></body>

In Chrome Jaws announces "My page document" for the document object. In Firefox it simply announces document.

Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Status: WontFix (was: Available)
Tested and document role can take aria-label and aria-labelledby. Jaws announces "Label document" ... "Document end".
So, you may use aria-label as a workaround.
Closing bug since Jaws behavior unlikely to change, there is nothing that Chrome can do and workaround present.
I've tried adding an aria-label to the div with role="document" but the screen reader won't read the label until I remove the role. This is the same with aria-labelledby. Is there any other workaround for this?
Status: Available (was: WontFix)
Reopening as per discussion today 
Status: Assigned (was: Available)
Cc: dsexton@chromium.org
Labels: a11y-testers
Status: Fixed (was: Assigned)
I was not able to repro using Chrome 67 with JAWS 2018.

Testers, please verify.
Hi, we still see this issue. Which chromium version this is fixed in?

Sign in to add a comment