WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Jonathan Avila
Date: Mar 3, 2021 1:24PM

Last time I checked that use first row as header cell caused THs to be created in PDF without requiring the previous approach of repeat header rows across pages to be checked when using the Save as PDF option in Word. So it seems like MS is moving toward using that approach - from what I recall. Repeating headers across pages is still a good idea though.

Jonathan

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Farough, David (CFP/PSC)
Sent: Wednesday, March 3, 2021 3:00 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] Can someone explain the following Accessibility checker results in Office 365?

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


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.