- From: Cynthia Shelly <cyns@microsoft.com>
- Date: Mon, 31 Mar 2014 14:37:00 +0000
- To: Richard Schwerdtfeger <schwer@us.ibm.com>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
- Message-ID: <f19f89fe6d45418a9d4874715a473b6f@BLUPR03MB166.namprd03.prod.outlook.com>
Regrets. I'm out sick today ________________________________ From: Richard Schwerdtfeger<mailto:schwer@us.ibm.com> Sent: ý3/ý28/ý2014 3:58 PM To: W3C WAI Protocols & Formats<mailto:public-pfwg@w3.org>; Dominic Mazzoni<mailto:dmazzoni@google.com> Subject: Agenda: March 31, 2014 WAI-PF ARIA Caucus Agenda: March 31, 2014 WAI-PF ARIA Caucus Time of meeting is 1:00PM EST, 10:00AM PST, 17:00 UTC, duration is 1.5 hours Zakim Bridge +1.617.761.6200, conference 92473 ("WAIPF") IRC: server: irc.w3.org, port: 6665, channel: #aria. - Identify Scribe - User Agent Implementation Guide - Quick status update - Michael chair while Rich on vacation? - ARIA 1.1 Meaty Issue - WebComponents requires selector functionality in ARIA attributes that are currently limited to IDREF(S) which cannot access elements within a web component - http://lists.w3.org/Archives/Public/public-pfwg/2014Mar/0091.html - http://www.w3.org/TR/components-intro/ - Need a workaround for DOM-based accessibility assessment tools http://lists.w3.org/Archives/Public/public-pfwg/2014Mar/0112.html We need to validate that all selectors resolve to a Node. Can we use eval() to do this? Need to see if eval will return null if no node available. - Issue 523 (searchbox/searchfield role): - https://www.w3.org/WAI/PF/Group/track/issues/523 - ARIA 1.1 Less Meaty Issues - Issue 590 Caption Role: Per our last discussion this should be closed in favor of aria-labelledby - https://www.w3.org/WAI/PF/Group/track/issues/590 - Issue 561 (introduce a placeholder attribute for custom text fields) - https://www.w3.org/WAI/PF/Group/track/issues/561 - Issue 606 grid role does not allow aria-setsize and aria-posinset - https://www.w3.org/WAI/PF/Group/track/issues/606 - Issue 637 ARIA math role should encourage the use of MathML - https://www.w3.org/WAI/PF/Group/track/issues/637 - Issue 427 Do we want to got for a Element.computedName and/or Element.computedRole? https://www.w3.org/WAI/PF/Group/track/issues/427 - January Face to Face Discussion Computed Role, Computed Name http://www.w3.org/2014/01/24-aria-minutes.html - No decision was made in the minutes but it sounded like there was consensus that we should do this and we could mark these as at risk items. - This would require coordination. References: ARIA Test Plan Action Items: http://www.w3.org/WAI/PF/Group/track/products/5 UAIG Open Actions and Issues: https://www.w3.org/WAI/PF/Group/track/products/10 ARIA Test Report: https://www.w3.org/WAI/PF/testharness/testreport?testsuite_id=1 Use Cases for Extended Descriptions: http://www.w3.org/WAI/PF/wiki/Use_Cases_for_Extended_Descriptions ARIA 1.1 Open Actions and Issues: https://www.w3.org/WAI/PF/Group/track/products/17 Minutes Last Meeting: http://www.w3.org/2014/03/24-aria-minutes.html <http://www.w3.org/2014/03/17-aria-minutes.html> Rich Schwerdtfeger
Received on Monday, 31 March 2014 14:37:31 UTC