- From: <bugzilla@jessica.w3.org>
- Date: Wed, 18 Apr 2012 13:05:51 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16774
Summary: placeholder name calculation
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia
Shelly)
AssignedTo: faulkner.steve@gmail.com
ReportedBy: faulkner.steve@gmail.com
QAContact: sideshowbarker+html-a11y-api@gmail.com
CC: mike@w3.org, public-html-bugzilla@w3.org,
public-html-wg-issue-tracking@w3.org,
public-html@w3.org
Ref: HTML to Platform Accessibility APIs Implementation Guide
http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html
For accessible name / description calculation under 5.1 Input type="text" or
textarea element the suggested order is aria-labelledby, aria-label,
placeholder, then the host language's placeholder, label element and title
attributes
Comment-1:
The INPUT type=text / textarea are host language constructs. So I find it odd
that aria-attributes should take precedence unless there is a role attribute
that is present that changes the role declared by the host language.
Comment-2:
Having stated the above order of precedence, it goes on to say that when only
placeholder and label are present, the label takes precedence and should be
considered to calculate accessible name.
Then why does placeholder precede label element in the above order beginning
with aria attributes?
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 18 April 2012 13:05:53 UTC