New issue
Advanced search Search tips

Issue 619950 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jun 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Semantics and not presented when traversing DOcs in Next

Project Member Reported by chaok@google.com, Jun 14 2016 
Mode: force_next
Version: 52.0.2743.32
Reproduction Steps: 
1. Open DOcs with headings, bullets, and other formatting
2. Try arrowing through the DOcs with Next
3. Try with CLassic

Observed:
Classic reports if an element is a heading, bullet, link, and when page changes; however, next treats everything as plain text with 0 formatting

Expected:
Next to be equivalent to classic, where it's possible to know the structure and formatting details of DOcs

Comment 1 by dtseng@chromium.org, Jun 14 2016

Status: wontfix (was: Unconfirmed)
Please try braille mode. The non-braille mode will be as good as any other screen reader (using Docs' live region based editor).

Classic will be *better* with braille mode off.
Next better with braille mode on.

Please re-open if you see something different.

Comment 2 by chaok@google.com, Jun 14 2016 

I'm using Braille mode
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 16 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ba8ead8fec469e986b2bf246398775d39bfca962

commit ba8ead8fec469e986b2bf246398775d39bfca962
Author: dtseng <dtseng@chromium.org>
Date: Thu Jun 16 18:43:02 2016

Adjust output rules related menus

Fixes for Google Docs' menu:
1. menuItem, menuItemCheckBox, and menuItemRadio don't play a button earcon
2. menuItem, menuItemCheckBox, and menuItemRadio all ignore output of their ancestry. Their ancestry gets created/destroyed on each key press, so the ancestry diffs are always up to the application node
3. play checked/unchecked earcons for menuItemCheckBox and menuItemRadio. Also, add specific output rules for these; they cannot inherit checkBox and radioButton rules because they must include index/total announcements.

BUG= 619950 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2069543004
Cr-Commit-Position: refs/heads/master@{#400218}

[modify] https://crrev.com/ba8ead8fec469e986b2bf246398775d39bfca962/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js
[modify] https://crrev.com/ba8ead8fec469e986b2bf246398775d39bfca962/chrome/browser/resources/chromeos/chromevox/cvox2/background/output_test.extjs

Comment 4 by chaok@google.com, Jul 8 2016 

TItle are reported, subtitles are not, headings are when using jump command (but not arrow), and bullets are not uttered.
Partially fixed in: 54.0.2787.0
►

Sign in to add a comment