Timeline for When providing programming documentation to users of an office suite software, does intelligent cell merging in tables, make the info more accessible?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:51 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jul 22, 2019 at 4:21 | comment | added | slugolicious |
"If you are able to edit your post to include links to academic research agreeing with your opinion". I don't feel that's necessary. The links to the various screen reader documentation that shows all the shortcut keys that are available for navigating a table is sufficient enough to show that screen readers have fantastic support for tables.
|
|
| Jul 22, 2019 at 4:17 | comment | added | slugolicious |
"BTW, you said that Word had no facility for marking header rows". No, I said there's now way to make a row header which is absolutely true. There is no way. You can make column headers which is the URL you posted but that has nothing to do with what I said was not possible.
|
|
| Jul 20, 2019 at 8:04 | comment | added | user127749 | When I looked at the university advice, I mistook the advice as being the direct fruits of academic research. Looking at it again, I can see that the advice wasn't specifically part of any academic research and I agree that the true nature of the advice lessens how official it is. If you are able to edit your post to include links to academic research agreeing with your opinion, that would improve your answer probably a great deal. | |
| Jul 20, 2019 at 7:57 | comment | added | user127749 | Hello @slugolicious, thanks for improving your answer. Whilst your personal experiences and the survey results did add weight to your argument, the thing that convinced me in the end was your pointing out that the Microsoft Word advice didn't necessarily apply to HTML tables and your pointing out that the W3C accessibility tutorials covering complex tables, didn't mention that merged cells were a problem. | |
| Jul 20, 2019 at 7:50 | vote | accept | CommunityBot | ||
| Jul 10, 2019 at 17:00 | comment | added | slugolicious | There is no "official" advice re. complex tables. As noted in my update, all the "official" advice was purely subjective and one person's opinion and was based on incorrect information. Note also that the most recent WebAIM screen reader survey (2017) says that complex tables are one of the least problematic areas - webaim.org/projects/screenreadersurvey7/#problematic | |
| Jun 30, 2019 at 22:32 | history | edited | slugolicious | CC BY-SA 4.0 |
add more details to address comments
|
| Jun 22, 2019 at 17:35 | comment | added | user127749 | Whilst what you say makes perfect sense, unfortunately, it seems to clash with the generally held official advice re. complex tables. It appears to clash with Microsoft's advice; such advice bears weight for my particular circumstances. See support.office.com/en-us/article/…. Is it possible for you to cite some kind of official advice re. your opinions? I think that would improve this StackExchange question a great deal. Thanks. | |
| Jun 22, 2019 at 17:35 | comment | added | user127749 | Thanks for your input on this. Great to have a screen-reader user adding their thoughts. | |
| Jun 21, 2019 at 14:41 | history | answered | slugolicious | CC BY-SA 4.0 |