Re:CSS Grid – Table layout is back. Be there and be square
by return0 on Tuesday January 31, 2017 @05:01AM
(#13529214)
The problem with screen readers is summarized "Screen readers assume the content inside a table is tabular". Are divs better just because they are undefined? It seems to me that the problem would more easily be solved by adding some attributes to skip tabular treatment or to add captions, rather than ditching tables altogether. Table elements like <caption> could even be used to identify and access parts of the UI pages.
[ Parent
| on HN ]
Re:CSS Grid – Table layout is back. Be there and be square
by andybak on Tuesday January 31, 2017 @06:22AM
(#13529642)
> Screen readers assume the content inside a table is tabular
I'm curious to hear from screen reader users. I recall that the gap between "what web developers think screen readers do" and "what screen readers do" has always been sizable.
Re:CSS Grid – Table layout is back. Be there and be square
by recklessplayer on Tuesday January 31, 2017 @11:07AM
(#13531716)
Windows based screen readers (more sophisticated than Mac's VoiceOver), let the users treat only data tables as tables and ignore layout tables.
Also users can adjust announcement of only column headers, only row headers, both or none while navigating through the data table.
Re:CSS Grid – Table layout is back. Be there and be square
by extra88 on Tuesday January 31, 2017 @08:10AM
(#13530190)
Using tables for layout is so commonplace, I think most screenreader makers basically gave up and don't treat a table as a table unless it includes headers (<th>). Of course people who choose to use tables for layout also skip using more semantic elements, have a lot less flexibility to make layout changes (because their choices are expressed in HTML instead of CSS), and have a lot more trouble making their designs responsive.