WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Can someone explain the following Accessibility checker results in Office 365?

for

From: glen walker
Date: Mar 3, 2021 1:20PM

I'm still using Office 2013 so was able to try this out. I don't have
office 365 so can't check that part.

If I have a table and check the "repeat as header row at the top of
each page" checkbox in the table properties dialog for the first row,
then if I save as PDF, the first row is correctly tagged as <TH>
elements. However, if I save as HTML, the table headers are not tagged
correctly. The elements are contained in a <thead> but they're
incorrectly tagged as <td> instead of <th>. Now, this is probably a
bug in "save as" and not a problem with the table itself (since the
PDF version worked). So I would expect office 365 to correctly read
the table headers. Did you confirm in the table properties dialog
that the row header checkbox is still selected (assuming O365 still
has that dialog).

On Wed, Mar 3, 2021 at 12:59 PM Farough, David (CFP/PSC)
< <EMAIL REMOVED> > wrote:
>
> I looked at a document that I had previously checked for accessibility in office 2013.
>
> I had insured at the time that all table header rows were set to repeat at the top of page so that they would be considered to be header rows for the tables.
>
> Now when inspecting the document in office 365 the accessibility checker reports all of these tables as having no header rows despite the fact that they are still marked appropriately in the rows page of the table properties dialogue.
>
> Can anyone tell me what selecting the 'use first row as header" option in the recommendations menu does and whether it actually makes a difference to the accessibility of the table.
>
> More importantly, will it be necessary to make similar changes to our other office 2013 documents?
>
> Thanks for any information you can provide.
> > > >