- From: Léonie Watson <tink@tink.uk>
- Date: Fri, 9 Mar 2018 11:26:03 +0000
- To: Matt King <a11ythinker@gmail.com>, 'Joanmarie Diggs' <jdiggs@igalia.com>, 'ARIA Working Group' <public-aria@w3.org>
Thanks for discussing further review of the ARIA in HTML and HTML AAM specs, in the meeting yesterday. When we asked ARIA WG to review ARIA in HTML last year, it was decided that APA WG's review would be done on behalf of both WGs. This was only documented on the APA WG wiki [1], and informally on the ARIA WG email list [2], which is why the current request has been made. We responded to the subsequent issues filed by Michiel on behalf of APA, and also to issues filed individually by Bryan, James, and Rich. Changes to the spec since that point have been mostly editorial. The bulk of the ARIA 1.1 changes had already been made by the time we went for wide review, because we were hoping ARIA 1.1 would be in CR in time to let us take ARIA in HTML to Rec at the same time as HTML5.2. It didn't turn out that way of course. Based on comments from the meeting, there seems to be some confusion as to what ARIA in HTML is. ARIA in HTML does not define roles (that is done in the ARIA spec). Nor does it document accessibility API mappings (that is done in the HTML AAM). ARIA in HTML describes a set of authoring rules for using ARIA when HTML is the host language. The host language is where the rules for using ARIA in that context are defined. The content of this specification was originally part of the HTML5.0 specification, but was pulled out into its own module before HTML5.1 was released. This was done because the WebPlat WG was considering modularising much of the HTML spec at that time. Steve Faulkner, as editor of ARIA in HTML, works closely with Mike Smith, as the person responsible for the W3C validator. The validator is the definitive implementation of this spec, flagging up errors and warnings when authors mis-use ARIA within an HTML document. With regard to the HTML AAM, we're hoping to put it out for wide review within the next few weeks. As with ARIA in HTML, we'll send a specific request through to both APA WG and ARIA WG when we get to that point. In the meantime, if it would help for either me, as WebPlat co-chair, or Steve, as ARIA in HTML/HTML AAM editor, to attend an ARIA WG meeting, please just ask. HTH Léonie [1] https://www.w3.org/WAI/APA/wiki/ARIA_in_HTML [2] https://lists.w3.org/Archives/Public/public-aria/2017Jul/0084.html On 08/03/2018 19:09, Matt King wrote: > Draft minutes for the below meeting are published at: > https://www.w3.org/2018/03/08-aria-minutes.html > > -----Original Message----- > From: Joanmarie Diggs [mailto:jdiggs@igalia.com] > Sent: Wednesday, March 7, 2018 10:26 AM > To: ARIA Working Group <public-aria@w3.org> > Subject: EDITED Agenda for Thursday, 8 March 2018 WAI-ARIA Working Group > > New topic requests have come in, so updated agenda. > > Meeting: WAI-ARIA Working Group - 8 March 2018 > Time: 10:00 AM US Pacific, 1:00 PM US Eastern > Duration: 1 hour > Webex: https://www.w3.org/2017/08/telecon-info_aria > IRC: irc.w3.org, port: 6665, channel: #aria > > Agenda: > 1. Reminder: Daylight Saving Time and next week's meeting 2. Face-to-face 1 May - 3 May, Toronto 3. ARIA in HTML and HTML AAM reviews 4. Personalization Semantics 5. Publishing the "wide review" Working Draft of AccName 6. AccName: 1.1 issues update 7. AccName: Testable statements and testing > > ========= > Resources > ========= > > Time: > https://www.timeanddate.com/worldclock/fixedtime.html?msg=WAI-ARIA+Working+Group+Meeting&iso=20180308T13&p1=43&ah=1 > > Issues: > * ARIA: https://github.com/w3c/aria/issues/ > * Core AAM: https://github.com/w3c/core-aam/issues > * AccName: https://github.com/w3c/accname/issues > > Decision Policy: https://www.w3.org/WAI/ARIA/decision-policy > > Minutes Last Meeting: https://www.w3.org/2018/03/01-aria-minutes.html > > > > > > > > > > > > > -- @LeonieWatson @tink@toot.cafe Carpe diem
Received on Friday, 9 March 2018 11:26:40 UTC