When making Word templates, I use the table design tools and make tables with header rows etc. passing the accessibility check in Word.
When exported to PDF, I get this check result:
The TD and TH check passed, but failed on "Headers". What headers are these? On the upper table, I added a visible header but find no way to connect it to the table...
According to the Microsoft support, everything is correct in Word. So what can be done to get this check passed??
I tried to change the proporties for the second table in Adobe Acrobat, thus some of this information would be the Table Header, but still it doesn't pass the Table Header check...
What's the consequence on accessibility if I skip the Header check? Just as the Summary is skipped per default...??
Hope for helpful competence out here!
Best regards,
Ulrika
1 Correct answer
One more note,
Check to ensure you've updated both your Acrobat and MS Office software. Both companies have released updates and bug fixes since mid-September, and the new versions correct some of the massive accessibility problems from both companies.
Acrobat's releases are listed here: https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/index.html
Microsoft's are listed here: https://docs.microsoft.com/en-us/officeupdates/current-channel
14
Replies
@Ulrika_G, Hi.
When making Word templates, I use the table design tools and make tables with header rows etc. passing the accessibility check in Word...
On the upper table, I added a visible header but find no way to connect it to the table...
By @Ulrika_G
In a Word table, the Table Headers are usually the first row of the table. They are a part of the table, not something that is added or connected to the table. So when you say "I added a visible header" and can't "find a way to connect it," I'm wondering if the tables are correctly constructed, regardless of what Word's accessibility checker says (it often misses accessibility items).
Generally, if a table is correctly made in Word, it automatically outputs correctly with the headers to the PDF and you do not get errors in Acrobat's accessibility checker.
Here's how to check in Word:
- Select the table.
- In the top Table Design tab, make sure that Header Row is checked. You can also check the First Column is you want Row Headers on the table.
In Word: Designating the first row of a tables as its column headers.
There's nothing to connect to the table because the first row of the table is now designated as the header row.
Can you verify if this is how you made your table in Word?
Thanks,
—Bevi
..The other one lacks content header in the first column's top cell, which is natural as this table has a first column with headers. By @Ulrika_G
Leaving the 1st (left-most) column header blank is a violation of accessibility standards and, therefore, will always be flagged by all accessibility checkers.
Every column must have a valid header.
Traditionally, that 1st column was left blank but no longer. Put something for the column header, even something generic like "description" or "item."
Recap of what has been covered:
- Format your Word document and table correctly. (See above.)
2. Don't use Adobe's PDF Maker to export the PDF. It is severely broken and makes an inaccessible PDF table. The error was mis-programmed into PDF Maker about 2-3 years ago and has gotten worse with the latest release from Adobe in Fall 2021.
Instead, use Microsoft's PDF export utility built into Word (see directions below). It tags tables correctly and you'll pass the accessibility checkers. (And it's FREE!)
Here are the errors you're getting from your PDFs made with Adobe's PDF Maker plug-in:
These errors make the PDF inaccessible and non-compliant with the PDF/UA-1 specification, which Adobe's engineers write and chair.
Use this method to export a more compliant PDF from MS Office:
- Ditch Adobe PDF Maker entirely.
- File / Save As (NOT Save As Adobe PDF...that invokes PDF Maker again, GAH, no no no !!!).
- Select PDF from the Type drop-down menu. And Select More options just below it.
Choose Microsoft's built-in export utility.
- In Options, set these parameters:
— Optimize for Standard
— Select Options button
— Create bookmarks using Headings
— Check: Document Properties
— Check: Document structure tags for acessbility
— Check: Optimize for image quality
— UNcheck: Bitmap text when fonts may not be embedded (bitmapped fonts are a violation of accessibility standards)
Click OK/Save.
I've attached 2 PDFs and their matching Word.docx files: One set uses Adobe's PDF Maker as of today's versions of software, the other uses Microsoft's built-in PDF export utility.
Hope this helps save your deadlines!
—Bevi Chagnon
IAAP ADS, and member of the ISO committees for PDF and PDF/UA standards (along with Adobe's engineers)
I can't tell for sure from your screen shots, but if you expand your <TR> and see a <P> tag full of PathPathPath, then the workaround below should help.
Here is a super dumb way past this bug:
In Word, do NOT use File >Save As PDF. Instead,
Go to File > Save As > [choose PDF from the file type droplist] > press Save.
No more PathPathPath!
It's objectively silly that File > Save As PDF should give you different results than choosing the file type manually. It doesn't create an accessibility nightmare like printing to PDF does, but those PathPathPath errors can really add up!
AdChoices