- From: <bugzilla@jessica.w3.org>
- Date: Wed, 19 Jan 2011 08:20:07 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11798
Summary: It has been brought to my attention by some browser
vendors that browsers don't actually implement
accessibility API annotations exactly the way the ARIA
spec says to; instead, they have default mappings from
HTML directly to the accessibility APIs that t
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#ann
otations-for-assistive-technology-products-(aria)
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org,
public-html-wg-issue-tracking@w3.org,
public-html@w3.org
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Section:
http://www.whatwg.org/specs/web-apps/current-work/#annotations-for-assistive-technology-products-(aria)
Comment:
It has been brought to my attention by some browser vendors that browsers
don't actually implement accessibility API annotations exactly the way the
ARIA spec says to; instead, they have default mappings from HTML directly to
the accessibility APIs that they use unless an explicit role="" has been
given. So it might make sense to change this section so that it is nothing but
conformance criteria for authors, removing the UA conformance criteria
relating to ARIA and platform AAPIs from the HTML spec altogether.
Posted from: 76.102.14.57 by ian@hixie.ch
--
Configure bugmail: http://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, 19 January 2011 08:20:09 UTC