Table A11y updates

[StephDriver]

• [x] review use of tables across platform

From #4194 the following issues have been identified:

• Tables do not consistently have <th> tags for both rows and columns. This occurs in both tables that are part of the main template for the page, e.g. article dates shown on the material theme, and for tables within articles themselves.
• footnotes within the tables that are to be written under the table, rather than as endnotes are not working well.

Part of the problem here is that JATS allows for inaccessible tables to be specified, thus user content will not always produce accessible tables. The row/column headings should be specified in the JATS and then picked up so if it is not correct there, it won't be correct on the page either.

Therefore we should -

• [x] ensure non-article (i.e. non user content) tables are accessible. Each data cell is expected to be understood in the context of one column header and one row header - so a single row of headers and a single column of headers for each table, using the <th> tag.
• [x] add user content/jats issue to Phase 2 of A11y project.

[StephDriver]

from Screen reader testing (#4194):

• Sample 2, item 66. dates are given in a table. This has no column header. I suggest "Date" as the header, or not to use tables here.
• Sample 4, item 33. table does not have unique headers for rows and columns, and what row headers exist, are only shown visually with <strong> tags rather than <th>
• Sample 4, item 35. following footnotes inside the table (e.g. in table 7) link to footnotes by moving the page on the screen, but reading or tabbing onwards takes you back to the original location, so footnote cannot be read.
• Sample 4, item 36. table footnotes do not have the letter of the footnote to which they relate.
• Sample 4, item 37. table footnotes are in paragraphs, rather than as a list.

[StephDriver]

https://jats4r.niso.org/accessibility/ JATS table a11y

[StephDriver]

I have started going through the codebase to work out what tables we have and what kind of updates might be needed. I think for the majority, I have the information needed to make updates, so I'd like to move this to Dev Ready and continue working on it there - might as well make changes as I review rather than report my findings only to have to go through them all again to make updates. It is possible some tables will be missed, but this should address the majority, and any outliers could be picked up later as individual fixes.

For info:

I have found 211 tables that need reviews.

Having taking an initial look at the first 24 tables:

• 8 tables with empty cells
• 8 tables with merged cells
• 1 table with a header marked as td
• 7 tables that have passed the first review that was just looking for obvious issues.

From this I believe that even if I only fix the obvious stuff, it would make a big difference.

[StephDriver]

Working on tables within themes directory only, and using W3C Tables Tutorial for guidance.

[StephDriver]

templates outside the clean theme that include tables (to investigate): (see https://github.com/openlibhums/janeway/issues/4215#issuecomment-2483302101 for how this list was generated)

• [x] common/accounts/register_privacy_policy.html
• [x] common/elements/altmetric_badges.html
• [x] common/elements/analytics.html
• [x] common/elements/edit_profilecss block.html
• [x] common/elements/edit_profile_js_block.html
• [x] common/elements/journal/editorial_team_country.html
• [x] common/elements/journal/editorial_team_image.html
• [x] common/elements/orcid_registration.html
• [x] common/elements/password_rules.html
• [x] common/elements/profile_image.html
• [x] common/elements/skip_to_main_content.html
• [x] common/elements/static-error-messages.html
• [x] elements/article_meta_tags.html
• [x] elements/forms/errors.html
• [x] elements/funder_info_for_readers.html
• [x] elements/social_meta.html

[StephDriver]

templates outside the clean theme that include tables (to investigate)

👉 no tables found in templates included from outside the theme directory..