Invalid use of a "THead" structure element - NO Table or THead tag present

Report · Jun 14, 2023

Hello,

I created an accessible form however I have one issue, I keep getting "Invalid use of a "THead" structure element".

In the form I have NO tables, and I do not have any THead tags.

How do I fix this??

HELP!!

Thanks!

Report · Jun 15, 2023

Hi @CyndyB836, I downloaded and examined your PDF and did not get the error about invalid use of the <THead> structure element.

I checked not just the tag tree, but also the architectural order (Order panel) and the Contents: could not find any remnants of the original layout table that was used to create the form.

What checker did you use that gave this error?

I wondering if there's some hidden <Table> code still in the file that's triggering the error.

FYI, this type of form is best built using Adobe InDesign, not Word. Several reasons:

InDesign's form tools let you insert the form fields directly in the layout so that they are there in the exported PDF and don't have to be added afterwards in Acrobat.
InDesign's table and general formatting tools are faster and easier to use.
There are 3rd party plug-ins you can install that allow for advanced control of the form fields and designating the table as a "layout table" to be artifacted in the PDF.
Using these tools and workflow, you can quickly edit and update the base form, and export a nearly-accessible PDF from InDesign. We have an upcoming class in this at www.PubCom.com (not that I'm here to promote our services).

Also noticed a few odd items in your PDF:

A few other errors.

The above errors indicate that the PDF was heavily altered after it was created and that some key elements (lists) weren't correctly tagged, edited, or artifacted during the process. It appears that this editing corrupted the PDF file itself, so I'm not surprised to see a negative checker report.

Suggestion:

Re-export a new PDF to get rid of the file corruption. To remove the <Table> tags:

First, drag each tag and its content out of the <Table> and drop it in the tag tree.
After that's completed, then you can select the <Table> tag (now empty) and artifact it correctly. I'd do this in the Content pane: select <Table>, right-click, select Artifact.
Make sure that the remaining content tags in the tag tree are correctly nested. Example, your lists must conform:
     <L>
         <LI>
            <Lbl> if you're using it
          <LBody>
You can copy/paste the <Form> fields from the original PDF into the new one, which should save some time and labor. Just make sure they end up being correctly nested within their <P> or <LBody> tags.

Another option is to send this file to a professional remediator. Contact me off-list if you'd a recommendation from us. We have one firm that does a superb job with forms, is honest and reliable, and has very reasonable prices.

Report · Jun 15, 2023

Hi Bevi,

Thank you so much for taking a look at this!!

In order to check the document I am using Pac 2021.

I would LOVE to use InDesign to create the forms, however I work for the Federal Governement and the forms I am transforming "belong" to other teams within my department. The form owners do not have InDesign on their comps and therefore would not be able to look over their documents to see if they agree with the changes I suggest. Additionallly, we collaborate with each division in order to create the form and the owners would have no idea on how to use InDesign to utilize the template I created for them.

For some reason when I tag the lists that way in Adobe PAC gives me an error. If I tag it that way in like Foxit PAC reads it fine...

Yes the document is very edited as you see, I do exactly as you suggest once I start working on a PDF.

If I don't correct the issue, what can happen? Like you said neither of us can find the tag it says I get an error with.

I honestly love when when I see your name popup when I ask a question! I know I will be getting the most indepth answer possible!

Thank you so much I GREATLY apprciate you!

Cyndy

Report · Jun 15, 2023

And I love your questions, Cyndy @CyndyB836 ! They're always thoughtful, looking for the best way to meet our end users' needs. Keep at it!

If I don't correct the issue, what can happen? Like you said neither of us can find the tag it says I get an error with.

First, a little background. All of the checkers — Adobe Acrobat, CommonLook, PAC, and others — are just software programs that look for black/white technicalities. Is it tagged? Yes/No. Do lists have one or more <LI> tags? Yes/No. None are perfect. None are as good a human testing.

We all must learn how to analyze the reports they give and decide whether the issue is valid or not.

RE: the <THead> tag error, let it go for now. I tested your file on 2 Windows computers with NVDA and it didn't choke on that. But correct the bigger issue with how your office is creating the forms so that this doesn't continue to happen. It might trip up some assistive technology, other than a screen reader. Remember, accessibility is for all people with any kind of disability and using any technology.

But some serious problems lie with these issues and they should be fixed before distributing this form. They are:

1. The lists, especially the one with 5 bullets on page 2. It's voicing is: "List. 1 item. bullet certificate...territorial one. bullet certificat de naturalisation two. etc."

So there's confusion/misinformation about how long the list is and when each bulleted item is being voiced. This list must conform to:

<LI>
<LBody>

The tag structure in the PDF when it was exported from Word should have automatically tagged it correctly, so I don't know how it got mangled into the hot mess it is now! But add new tags and drag/drop the appropriate content into them.

2. The second issue are the footnotes. Right now the superscript numbers are just inserting "two" into the middle of a stream of text without any hyperlink to the footnote itself, or identification that they are a reference.

So grab each individual superscript number, wrap it in a <Reference> tag, and then hyperlink it to its footnote text at the bottom.

You'll also have to correct the footnote tags themselves. They should look like this:

<H3> Notes

<Note> 1. Une personne...

<Note> 2. Emis...

<Note> 3. Emis entre...

<Note> 4. Les personnes...

I've simplified the tag structures above: technically, footnotes and bullets should have <Lbl> tags as well, but they're not yet recognized by assistive technologies and the file will work without <Lbl>s.

All the other stuff worked fine. Text and headings were announced, and there was no mention of a table anywhere.

Report · Jun 16, 2023

for the notes and the hyperlinks, do I need to create a hyperlink back up to the text that has the notes as well? Or just on the small number down to the associated note?

Report · Jun 16, 2023

for the notes and the hyperlinks, do I need to create a hyperlink back up to the text that has the notes as well? Or just on the small number down to the associated note?
By @CyndyB836

It's not required, but is surely very helpful to our users. And this hasn't yet been addressed by the accessibility standards.

Report · Jun 15, 2023

And about your workflow...

I understand completely where you are. Here in the states we say "between the dog and fire hydrant." <grin>

Have worked for decades with US government agencies on documents, publishing, forms, and accessibility.

It is possible to create accessible templates that staff can use to produce reasonably accessible PDFs.

But not for accessible forms.

Everyone who creates a government form must have advanced training in how to do this. There isn't a magic easy button to click, nor can you provide this to them in a template. Only a trained form designer can create the final form that will go public. Otherwise you'll have this type of code crud to deal with, and as you've discovered, it's not easy or fun to correct a bad PDF form. (You should get "combat pay" for doing this!)

Here's one workflow that works for our clients (and us at our shop). Maybe a variation can work for you.

Client "designs" the form skeleton in Word. The skeleton is just the text and graphics, but no form fields because Word's form controls are totally useless when the PDF is exported.
The form designer polishes the form skeleton in either Word or Adobe InDesign.
The skeleton form is exported to PDF to test the accessibility. It should have the correct headings, paragraphs, and lists, as well as a good logical reading order. If not, go back and correct the source file before proceeding.
Once the skeleton passes, then export a PROOF PDF to send to the client for review. Don't add the form fields until the client has first signed off on the skeleton and basic layout/design.
Once the client's edits are completed, now add the form fields in either Acrobat or InDesign.
Add the tool tips, set the form field options, etc. and do all the other stuff you need to complete the form.
Then export the final, accessible PDF form.

It should end up in very good shape and need little manual remediation, well, except if you use a layout table. That you'll have to drag/drop manually.

Wish you the best on this!

Report · Jun 16, 2023

This is such a good idea!

I have never felt so seen when you said we should get combat pay for this. I am COMPLETELY self taught in this! My boss one day was like "hey can you do make all our forms accessible? It can't be that hard right?"

Me knowing nothing on the subject was like "yeah, accessibility is the reason we use computers, this should be easy!!"

Two years later I have finished 6 of 140, technically 280 because they all have to be unilingual but we need them in French and English....ANd they keep taking resources away LOL