Wikipedia talk:Manual of Style/Accessibility/Data tables tutorial: Difference between revisions
Content deleted Content added
Timeshifter (talk | contribs) |
|||
Line 388:
:::Getting to your questions. I don't see the need for designating row headers in the 2 column table examples you gave. Screen readers will read the column header for each data cell. It will be obvious to the user what the relationship is between the the 2 cells in each row, even without row headers. And scopes are total overkill in that example.
:::--[[User:Timeshifter|'''Timeshifter''']] ([[User talk:Timeshifter|talk]]) 10:41, 10 December 2021 (UTC)
::::Thanks, {{u|Timeshifter}}. You've given me a fair bit of homework, and I can't promise I'll jump on it immediately ... As I've said, I'm hopeless with table terminology ("scope"?).
::::I'm all for ensuring good accessibility for screen readers, but I'm confused as to why a simple, two-column table has to be rendered in the current way. And/or: why it is that the screen-reader-friendly input needs to even register visually when one reads the page "normally". (Why do we need to ''see'' what that software handles differently?) As I've said, my concern is with the two-column tables for record charts. Not only is it so simple in presentation that one questions whether info in the left-hand column really is a row header, but the table ends up such an eyesore, because the darkened-out LH column is usually far wider than the RH column, which contains just a single or double digit.
::::Anyway, don't feel the need to reply to that. I obviously need to do some reading. [[User:JG66|JG66]] ([[User talk:JG66|talk]]) 15:57, 10 December 2021 (UTC)
| |||