New issue
Advanced search Search tips

Issue 641848 link

Starred by 3 users

Issue metadata

Status: Verified
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

Cannot select device/provider with Next, but can with Classic

Project Member Reported by chaok@google.com, Aug 29 2016

Issue description

Mode: force_next
Version: 55.0.2842.0
Reproduction Steps: 
1. hbogo.com/activate
2. Try to select *any* device/provider
3. Both set of list are empty with Next, but work with Classic


 
Project Member

Comment 1 by sheriffbot@chromium.org, Aug 29 2016

Labels: Hotlist-Google
Status: Untriaged (was: Unconfirmed)
Unable to use both classic and next to select the device 
Cc: lpalmaro@chromium.org dtseng@chromium.org
Labels: -Pri-2 Phase3 Pri-3
Thanks - out of curiosity, have you noticed this issue with other lists as well or is this specific to hbogo so far? 

Comment 5 by dtseng@chromium.org, Oct 27 2016

Status: fixed (was: Untriaged)
Maybe out of date or fixed by another change. Works for me.
Status: Assigned (was: Fixed)
As i check on 56.0.2903.0 , this isn't working for me
Status: started (was: Assigned)
Please write more specific reproductions; *any* and doesn't work usually won't help us track the issue down and causes round trips like above.

The actual reproduction below:
STR
- hbogo.com/activate
- search+right until you get to the my device link
- search+sace
- search+right and see various devices
- search+space
- a device is selected

This is all working properly


- search+right until continue link
- search+space
- new screen
-search right until list

result:
no items

expected:
images inside of list


Fix is in review...
Project Member

Comment 8 by bugdroid1@chromium.org, Nov 6 2016

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

commit 32e424c9defb30fdf056cc48f1c90451f8c6c2a9
Author: dtseng <dtseng@chromium.org>
Date: Sun Nov 06 23:32:34 2016

Expose images to accessibility

Blink has some loose heuristics to ignore images, even ones that are important for interaction.

Specifically, web authors do use horizontal images (i.e. 1d images) to convey information to screen readers that is not purely presentational.

At the very least, it should be up to each client to make an intelligent determination.

This cl also adds missing graphics predicates and key bindings to ChromeVox.

BUG= 641848 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/chrome/browser/resources/chromeos/chromevox/chromevox/background/keymaps/next_keymap.json
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/chrome/browser/resources/chromeos/chromevox/cvox2/background/automation_predicate.js
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/chrome/browser/resources/chromeos/chromevox/cvox2/background/command_handler.js
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/content/test/data/accessibility/html/img-empty-alt-expected-blink.txt
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/content/test/data/accessibility/html/img-empty-alt-expected-mac.txt
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/content/test/data/accessibility/html/img-expected-android.txt
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/content/test/data/accessibility/html/img-expected-mac.txt
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/content/test/data/accessibility/html/img-expected-win.txt
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/third_party/WebKit/LayoutTests/accessibility/img-alt-tag-only-whitespace-expected.txt
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/third_party/WebKit/LayoutTests/accessibility/img-alt-tag-only-whitespace.html
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/third_party/WebKit/LayoutTests/accessibility/img-fallsback-to-title-expected.txt
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/third_party/WebKit/LayoutTests/accessibility/img-fallsback-to-title.html
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/third_party/WebKit/LayoutTests/inspector-protocol/accessibility/accessibility-ignoredNodes-expected.txt
[modify] https://crrev.com/32e424c9defb30fdf056cc48f1c90451f8c6c2a9/third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp

Status: fixed (was: Started)
Status: Verified (was: Fixed)

Sign in to add a comment