New issue
Advanced search Search tips

Issue 713600 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

update placeholder/aria-placeholder mapping

Project Member Reported by faulkner...@gmail.com, Apr 20 2017

Issue description

Chrome Version: Version 58.0.3029.81
OS: win10

What steps will reproduce the problem?
(1) open http://s.codepen.io/stevef/debug/jmWrxV/dXMqBbOKgnPr
(2) check the accessible name value for the 2 text inputs


What is the expected result?
the value of the placeholder and aria-placeholder is exposed via the placeholder property (for example in IA2 a placeholder-text object attribute)

What happens instead?

the value of the placeholder and aria-placeholder is exposed via the acc name property 


Please use labels and text to provide additional information.

mapping for placeholder - https://w3c.github.io/html-aam/#att-placeholder

placeholder maps to aria-placeholder defined here: http://w3c.github.io/aria/core-aam/core-aam.html#ariaPlaceholder

Note: the current implemented mapping was correct at time, but since then placeholder properties have been added to acc APIs to handle the attribute

.

 
Steve, have JAWS, NVDA and VoiceOver caught up and use the text attribute? I'd also be concerned about older JAWS users who don't get an update. So if we implement this won't we be messing some people up?
I'm worried about this too. Many platforms don't have a separate placeholder attribute, and older AT won't support it.

Status: Available (was: Untriaged)
Related to  issue 677147 . Keeping this as P3 Available and will contact AT vendors about supporting placeholder mapping.

Sign in to add a comment