11798 2011-01-19 08:20:07 +0000 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 2012-01-13 09:38:15 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED DUPLICATE 10066 http://www.whatwg.org/specs/web-apps/current-work/#annotations-for-assistive-technology-products-(aria) P3 normal --- 1 contributor ian annevk cooper dbolter faulkner.steve ian laura.lee.carlson mike mjs public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 44461 0 contributor 2011-01-19 08:20:07 +0000 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 44473 1 annevk 2011-01-19 14:11:30 +0000 If we want interoperability here this should still be defined somewhere, no? 44485 2 ian 2011-01-19 17:15:39 +0000 This probably affects ISSUE-129. 44486 3 faulkner.steve 2011-01-19 17:19:31 +0000 (In reply to comment #2) > This probably affects ISSUE-129. i am sure it does, when can we expect some elaboration of your thinking? 44487 4 mjs 2011-01-19 17:22:31 +0000 The comment in the subject is not accurate as to WebKit. We map elements and attributes to generic roles and properties (matching ARIA whenever possible) and then map those to a native API. 44492 5 dbolter 2011-01-19 18:09:45 +0000 (In reply to comment #4) > The comment in the subject is not accurate as to WebKit. We map elements and > attributes to generic roles and properties (matching ARIA whenever possible) > and then map those to a native API. Firefox also has had an internal representation that predates ARIA and in some cases informed the spec. I don't tend to mention this in case it conflates things. 44580 6 ian 2011-01-21 23:30:34 +0000 (In reply to comment #3) > i am sure it does, when can we expect some elaboration of your thinking? I'm not sure there's anything to elaborate on beyond what comment 0 says. 44601 7 faulkner.steve 2011-01-22 08:08:30 +0000 (In reply to comment #6) > (In reply to comment #3) > > i am sure it does, when can we expect some elaboration of your thinking? > > I'm not sure there's anything to elaborate on beyond what comment 0 says. "some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to" how do they differ? "This probably affects ISSUE-129" how? "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." how will this materially affect the current spec text? 44602 8 faulkner.steve 2011-01-22 08:41:08 +0000 "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." does this bug indicate that we are closer to an amicable resolution in regards in regards to the "basis for addition of "Guidance for User Agents" [1] part of the change proposal? [1] http://www.w3.org/html/wg/wiki/ChangeProposals/ARIAinHTML5#basis_for_addition_of_.22Guidance_for_User_Agents.22 44716 9 cooper 2011-01-25 16:36:24 +0000 Bug triage sub-team is marking this as a duplicate of 10066. That is the master bug for ARIA integration and ISSUE-129. Under remit of those issues, the ARIA integration sub-team is developing HTML to Platform Accessibility APIs Implementation Guide currently drafted at http://dev.w3.org/html5/html-api-map/overview.html. That is the document that addresses the concern raised by this bug. *** This bug has been marked as a duplicate of bug 10066 *** 52685 10 mike 2011-08-04 05:03:37 +0000 mass-moved component to LC1 62654 11 faulkner.steve 2012-01-13 09:38:15 +0000 removing accessibility keywords as bug is a dupe.