New issue
Advanced search Search tips

Issue 758089 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

HTML5 section element role exposed incorrectly

Project Member Reported by faulkner...@gmail.com, Aug 23 2017

Issue description

Chrome Version: (copy from chrome://version)
OS: (all)

The HTML Accessibility API Mappings 1.0 defines different roles for the section element depending on the presence of an accessible name:

with accessible name role=region
https://w3c.github.io/html-aam/#el-section
http://w3c.github.io/aria/core-aam/core-aam.html#role-map-region
without, does not = region
http://w3c.github.io/aria/core-aam/core-aam.html#role-map-region-nameless

suggest chrome align implementation with spec.

test case which includes named and un-named section element: https://s.codepen.io/stevef/debug/JyvZLN

 
Components: UI>Accessibility
Labels: win-a11y OS-Android OS-Chrome OS-Fuchsia OS-iOS OS-Linux OS-Mac OS-Windows
Owner: dsexton@chromium.org
Status: Available (was: Untriaged)
This appears to be fixed on Windows in 65.0.3291.1 (Official Build) canary SyzyASan (32-bit) (cohort: ASAN)

Needs testing in other OS'
Components: -UI>Accessibility UI>Accessibility>ChromeVox
Labels: -OS-Windows -win-a11y
Owner: dtseng@chromium.org
The named section is not read with ChromeVox
Chrome: 65.0.3357.3
Status: Assigned (was: Available)
Labels: -OS-Android -OS-iOS -OS-All -OS-Fuchsia

Sign in to add a comment