New issue
Advanced search Search tips

Issue 628862 link

Starred by 4 users

Issue metadata

Status: Verified
Owner:
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Changing a radio button control causes the name and state of the control to be uttered twice

Reported by nimerjaber1@gmail.com, Jul 16 2016

Issue description

Mode: force_next
Version: 54.0.2796.4
Reproduction Steps: 
1. Launch Cvox Next
2. Navigate to any page with radio buttons
3. Up/down arrow to cycle between options and to select one.
Expected: Name and type of control to be uttered once.
Actual: Name and state are uttered at least twice.

 
Labels: Phase3
Owner: dtseng@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 2 by chaok@google.com, Oct 16 2016

Demo URL of radiobutton: http://webaim.org/techniques/forms/controls
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 25 2016

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

commit 6007cdb65f04ec552d34c04b744cd50f16defc01
Author: dtseng <dtseng@chromium.org>
Date: Tue Oct 25 21:45:23 2016

Complete checked state announcements and clarify state usage

Firstly, the checked state has some unexpected bheaviors as follows:
- aria checked is not reflected by the state bitmap; for example, if aria-checked is set to true, the state bitmap doesn't actually contain the checked state. ChromeVox should not have to make this workaround, but for the purposes of output, we should do the right thing regardless of this behavior
- some states really should only be relevant  when they are true (e.g. collapsed, expanded, visited); encode this in the state data
- other states are only relevant for specific roles (e.g. pressed).

BUG= 646100 , 628862 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

[modify] https://crrev.com/6007cdb65f04ec552d34c04b744cd50f16defc01/chrome/browser/resources/chromeos/chromevox/common/chrome_extension_externs.js
[modify] https://crrev.com/6007cdb65f04ec552d34c04b744cd50f16defc01/chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs
[modify] https://crrev.com/6007cdb65f04ec552d34c04b744cd50f16defc01/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
[modify] https://crrev.com/6007cdb65f04ec552d34c04b744cd50f16defc01/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js
[modify] https://crrev.com/6007cdb65f04ec552d34c04b744cd50f16defc01/chrome/browser/resources/chromeos/chromevox/cvox2/background/output_test.extjs
[modify] https://crrev.com/6007cdb65f04ec552d34c04b744cd50f16defc01/chrome/browser/resources/chromeos/chromevox/strings/chromevox_strings.grd

Comment 4 by dtseng@chromium.org, Oct 25 2016

Status: fixed (was: Assigned)
Status: Verified (was: Fixed)
verified on 56.0.2903.0

Sign in to add a comment