Re:When to use tables for layout
by simonw on Tuesday June 17, 2008 @05:55PM
(#220188)
According to accessibility gurus that I know (proper ones who run real controlled tests with screen readers, not just random people who read blogs) using tables for form layout (as shown in that article) is bad, because screen readers have "forms mode" and "tables mode" and a form inside a table forces them to constantly toggle between the two, making it extremely hard to follow.
[ Parent
| on HN ]
Re:When to use tables for layout
by shawndrost on Tuesday June 17, 2008 @06:10PM
(#220211)
The world will not write code for screen readers. How about writing screen readers that can read the code that the world wants to write?
That would be fantastic. The problem is that we're pretty much stuck with the screen readers we've got - even when the screen reader companies do release new versions (which they do painfully infrequently) most of their users stick with their current versions because the upgrades are so expensive. If you care about blind users (which you should; you're missing one of the great benefits of the Web if you don't) you need to cater to screen reader versions that are five or so years old!
Fine, I'll ignore the blind market. I'm not trying to be mean but just realistic. I don't operate a government website which needs to be ADA compliant, and if screen reader software isn't where it needs to be, then maybe there is just no solution.
It is pretty pointless to care about blind users, since they can't use most AJAX based sites anyway.
Re:When to use tables for layout
by jonny_noog on Wednesday June 18, 2008 @02:40AM
(#220587)
I thought this was the whole point behind "graceful degradation". If an AJAX based site does not degrade to still be useable/accessible when JS is off or unavailable, then it's not that well desgined to begin with.