New issue
Advanced search Search tips

Issue 685723 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

ChromeVox does not read MathML in labels for radio buttons

Reported by dchappel...@gmail.com, Jan 26 2017

Issue description

Chrome Version       : 55.0.2883.87
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: PASS/FAIL (Version)
    Firefox: PASS/FAIL (Version)
         IE: PASS/FAIL (Version)

What steps will reproduce the problem?
(1)Open the attached HTML file in Chrome.
(2)Activate ChromeVox.
(3)Using ChromeVox move to the radio button selections in the first list item.
(4)Using ChromeVox focus on each of the three selections.
(5)Note that ChromeVox announces the label text.
(6)Using ChromeVox move to the radio button selections in the second list item.
(7)Using ChromeVox focus on each of the three selections.
(8)Note that ChromeVox only announces the selection state of the radio button.
(9)Using ChromeVox move to teh radio button selections in the third list item.
(10)Using ChromeVox focus on each of the three selections.
(11)Note that ChromeVox only announces the selection state of the radio button.

What is the expected result?
The highest expectation is that label content would behave the same even if it is in MathML. The next highest is that the alttext value would be used as the text for the label.


What happens instead?
Only the selection status of the radio buttons is announced.


Please provide any additional information below. Attach a screenshot if
possible.
I have done testing with JAWS and NVDA in Firefox and IE for this issue. Neither will announce MathML properly when it exists in a label without an alttext attribute. When the alttext attribute is present this value is used as the label. If the alttext value cannot be used then there seems little hope of making multiple choice questions involving math equations accessible. This is likely an issue on MacOSX and Linux as well but I have not done testing yet.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
ChromeVox label issue.html
3.0 KB View Download

Comment 1 by tkent@chromium.org, Jan 30 2017

Components: UI>Accessibility

Comment 2 by ajha@chromium.org, Jan 31 2017

Labels: Needs-Milestone

Comment 3 by ajha@chromium.org, Feb 9 2017

Cc: ajha@chromium.org
Components: Platform>Extensions
Labels: -Pri-3 -Needs-Milestone M-58 OS-Linux OS-Mac Pri-2
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on the latest canary(58.0.3007.0) on Windows-10, Mac OS 10.12.2 and Linux Ubuntu 14.04 with Chromevox extension.

Similar behavior is seen on older chrome version(43.0.2312.0) as well. Versions prior to that I was unable to add the extension and getting error 'There was a problem with the download. Please contact the developer or try again later. Invalid manifest'

Marking this as Untriaged for more inputs on this.
Owner: dmazz...@chromium.org
Status: Assigned (was: Untriaged)
dmazzoni for ChromeVox triage.
ChromeVox -> dmazzoni@ for triage.
Labels: OS-Chrome
All ChromeVox bugs should be OS:Chrome by default. We can remove in the rare case where it's not.

Labels: NewComponent-Accessibility-ChromeVox
Labels: NewComponent-Accessibility
Components: UI>Accessibility>ChromeVox
Labels: -newcomponent-accessibility -newcomponent-accessibility-chromevox
Components: -UI>Accessibility
Labels: -M-58 ChromeVox-specific
ChromeOS Version 63.0.3238.0 (Official Build) canary (64-bit)
Firmware Version Google_Samus.6300.174.0

This still reproduces on Chrome OS. I am testing this with ChromeVox on Chrome OS because we recommend that you use native screen readers on other platforms such as JAWS, NVDA, TalkBack, or VoiceOver. 

Here are the steps I followed:
(1)Open the attached HTML file in Chrome. - opened in Chrome OS 
(2)Activate ChromeVox.
(3)Using ChromeVox move to the radio button selections in the first list item.
(4)Using ChromeVox focus on each of the three selections.
(5)Note that ChromeVox announces the label text. - pass, it reads the radio buttons for me. 

(6)Using ChromeVox move to the radio button selections in the second list item.
(7)Using ChromeVox focus on each of the three selections.
(8)Note that ChromeVox only announces the selection state of the radio button.
- I also see the same, it reads ", radio button unselected" 

(9)Using ChromeVox move to the radio button selections in the third list item.
(10)Using ChromeVox focus on each of the three selections.
(11)Note that ChromeVox only announces the selection state of the radio button.
- I also see the same, it reads ", radio button unselected" 

Google Chrome	64.0.3282.24 (Official Build) dev (64-bit) (cohort: Dev)
Windows 10 Enterprise Version 1607 Build 14393.1770
JAWS 2018.1712.10 Private Beta 

This also reproduces with JAWS on Windows using the steps listed in the description. It is a cross-platform bug in that way. The MATHML in the second two groups is not read. This is an interaction bug.

group start These radio buttons have plain text within the label.
radio button not checked   Radio button number 1. 
radio button not checked   This is the second radio button. 
radio button not checked   No one understands the power of being the third radio button.
group end
group start The MathML for these radio buttons have an alttext attribute.
radio button not checked   
radio button not checked   
radio button not checked   
group end
group start The MathML for these radio buttons do not have an alttext attribute.
radio button not checked   
radio button not checked   
radio button not checked   
group end

Labels: -ChromeVox-specific win-a11y
Owner: ----
Status: Available (was: Assigned)
I think this is secondary
Project Member

Comment 15 by sheriffbot@chromium.org, Dec 17

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: dmazz...@chromium.org
Components: -Platform>Extensions
Status: Available (was: Untriaged)

Sign in to add a comment