- From: James Craig <jcraig@apple.com>
- Date: Tue, 15 Apr 2014 17:57:43 -0700
- To: Matthew King <mattking@us.ibm.com>
- Cc: W3C WAI Protocols & Formats <public-pfwg@w3.org>
Received on Wednesday, 16 April 2014 00:58:18 UTC
Seems like an easy fix for ARIA 1.1. I don't mind moving it. https://www.w3.org/WAI/PF/Group/track/actions/1294 We decided to leave the related colindex/rowindex issue for 2.0, which I think that's a bigger can of worms. On Apr 15, 2014, at 5:49 PM, Matthew King <mattking@us.ibm.com> wrote: > We just ran into the situation in an app where we need posinset on a tab element in a tablist. It is nice that browsers and screen readers are already supporting posinset and setsize on the tab element, but our checking tool is "correctly" flagging it as a violation, which I am ignoring. > > I see that this action 1294 was partially completed, but not done for tab. The issue 398 is marked for 2.0. Do we really need to wait for 2.0 to update this? Was there something that made it more complicated than we initially thought? > > Matt King > IBM Senior Technical Staff Member > I/T Chief Accessibility Strategist > IBM BT/CIO - Global Workforce and Web Process Enablement > Phone: (503) 578-2329, Tie line: 731-7398 > mattking@us.ibm.com
Received on Wednesday, 16 April 2014 00:58:18 UTC