- From: Jan Hellbusch <jan@hellbusch.de>
- Date: Mon, 7 May 2018 07:53:58 +0200
- To: "'WAI Interest Group'" <w3c-wai-ig@w3.org>
> In the example you give there is a simple solution by using nested tables. The wrapper table is not actually necessary, but with role="none" semantics can be removed. The results are two tables, which can be "joined" in the accessibility tree with aria-owns (will work mostly, but aria-owns does not work properly in NVDA/IE): <table role="none"> <tr><td> <table id="left" aria-owns="right1 right2 right3"> <tr><td>key 1</td><td>value 1</td></tr> <tr><td>key 2</td><td>value 2</td></tr> <tr><td>key 3</td><td>value 3</td></tr> </table> </td><td> <table id="right"> <tr id="right1"><td>key 4</td><td>value 4</td></tr> <tr id="right2"><td>key 5</td><td>value 5</td></tr> <tr id="right3"><td>key 6</td><td>value 6</td></tr> </table> </td></tr> </table> Jan -- Hellbusch Accessibility Consulting Chemnitzer Str. 50, 44139 Dortmund Tel.: +49 (231) 58054815 Mobil: +49 (163) 3369925 -- Accessibility-Consulting seit 15 Jahren Leistungen, Bücher, Artikel: https://www.barrierefreies-webdesign.de Blog: https://www.hellbusch.de
Received on Monday, 7 May 2018 05:55:08 UTC