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

Issue 781631 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

ChromeVox ignores reversed and start=n on ol element

Reported by soapboxc...@gmail.com, Nov 5 2017

Issue description

Chrome Version       : 62.0.3202.75

What steps will reproduce the problem?

Create an ol with reversed and/or start="n" attributes.

What is the expected result?

ChromeVox says the appropriate list marker for each child li, counting down if reversed is specified and starting at the number specified.

What happens instead of that?

ChromeVox always reports the children as 1, 2, ..., m even if reversed and/or a start="n" attribute is provided.

Please provide any additional information below. Attach a screenshot if
possible.

The correct ListMarker value is shown in the dev tools Accessibility panel. The information is in the accessibility tree but is ignored by ChromeVox.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36



 
Components: UI>Accessibility>ChromeVox
Cc: krajshree@chromium.org
Labels: Needs-Triage-M62 Needs-Feedback
soapboxcicero@ - Thanks for filing the issue...!!

Could you please provide a sample test file to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!
attached
issue-781631.html
402 bytes View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Pri-3 M-64 OS-Mac OS-Windows Pri-2
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #62.0.3202.75 and latest canary #64.0.3261.0.
This is a non-regression issue as it is observed from M52 old builds. 
Note: From M51 and older builds the chrome vox doesn't read the content in the page. Hence, marking it untriaged from M-52 to get more inputs from dev team.

Thanks...!!
Hello, 

We recommend using a native screen reader with Chrome. For example, please let us know if this reproduces with JAWS or NVDA on Windows or ChromeVox on Chrome OS. 

Thanks,

Laura 
I don't have access to those, but I don't need a screenreader. Just stumbled along this messing around. If anyone with access to those screenreaders can see what those do, I'm sure that would be helpful data.
Chrome 65.0.3294.0 (Official Build) canary (64-bit) 
NVDA 2017.4

This does not repro in Chrome with NVDA.
Status: WontFix (was: Untriaged)

Sign in to add a comment