New issue
Advanced search Search tips

Issue 682989 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

ABBR element accessibility

Reported by luis.mar...@gmail.com, Jan 20 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.59 Safari/537.36

Example URL:
https://thepaciellogroup.github.io/AT-browser-tests/test-files/abbr.html

Steps to reproduce the problem:
1. Read any abbr element with ChromeVox.
2. Notice no expansion offered or indicated.

What is the expected behavior?
ChromeVox to offer an expansion, indicate it exists, or catalog it in a list of expansions.

What went wrong?
No expansion is indicated.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 56.0.2924.59  Channel: beta
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

Web Content Accessibility Guidelines 2.0 recommend "H28: Providing definitions for abbreviations by using the abbr element" https://www.w3.org/TR/WCAG20-TECHS/H28.html
Assistive Technology should use this accessibility feature.
 

Comment 1 by ajha@chromium.org, Jan 23 2017

Components: UI>Accessibility
Labels: Needs-Triage-M56
Cc: rbasuvula@chromium.org
Labels: -Needs-Triage-M56 M-57 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Tested the issue on chrome Beta #56.0.2924.69, Canary 57.0.2989.0 in Windows 7 and was able to reproduce the issue.

Observations:
M30-M45 - Unable to add the Chrome vox extention.
M45-M57 - No expansion is indicated

This is a Non-Regression issue since seeing this from M45 #45.0.2454.0, Making the status to Untriaged so that the issue would get addressed.

Note : Able to reproduce the issue in MAC 10.12 and Linux Ubuntu 14.04.

Thank you.
Components: -Blink
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
Components: -UI>Accessibility>ChromeVox UI>Accessibility
Labels: -M-57
Status: Available (was: Untriaged)
Chrome 63.0.3214.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 10.0.14393 Build 14393.1593
NVDA 2017.3
JAWS 2018 Beta 
Firefox 55.0.3 (64-bit)
ChromeOS Version 63.0.3207.0 (Official Build) canary (64-bit)

I am able to reproduce this issue across platforms as well as in FireFox. 

I used the following steps:
# Load https://thepaciellogroup.github.io/AT-browser-tests/test-files/abbr.html
# Navigate to the BBC text. Listen for any mention of expansion.

# Put JAWS into "expand abbreviations" mode in Settings Center > Web/HTML/PDFs > Reading > Verbosity Level, check "Expand Abbreviations" 
Chrome + JAWS w/ expand abbr: BBC is properly expanded into British Broadcasting Corporation
# Uncheck the box for Expand Abbreviations in JAWS Settings
Chrome + JAWS w/o expand abbr: BBC is not expanded, no prompt to expand 

#Close JAWS, launch NVDA
# Navigate to the BBC abbr, press NVDA + 5 to report dynamic content
Chrome + NVDA: No expansion offered, speaks "BBC report dynamic content changes on"

Firefox + JAWS: same behavior as Chrome
Firefox + NVDA: same behavior as Chrome 

#Load page in ChromeBook, launch ChromeVox
ChromeVox + ChromeOS: BBC is spoken, no expansion offered. 
 

Labels: win-a11y
Summary: ABBR element accessibility (was: ChromeVox won't expand abbr elements)
Project Member

Comment 12 by sheriffbot@chromium.org, Dec 21

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

Sign in to add a comment