- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Sep 2012 19:47:23 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18245 --- Comment #7 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2012-09-13 19:47:23 UTC --- (In reply to comment #6) > (In reply to comment #5) > > For a CSS approach see: > > > > http://lists.w3.org/Archives/Public/www-style/2009Apr/0298.html > > doesn't ppaear to provide any info about how the semantics/states and > properties of the tabs are to be conveyed or am I missing something? Don't think you are. It's just an example of what a tabbing mechanism might look like in CSS. If this was added, mappings to accessibility API roles, states, and properties would have to be derived. If we also added markup for tab views that could use the CSS mechanism. Not sure of the merits of tab views being expressed as part of the structure of the document/application rather than presentation. -- Configure bugmail: https://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 Thursday, 13 September 2012 19:47:29 UTC