Table Header Not Identified Programmatically

I am trying to figure out how to set/mark a header row with the TH for accessibility purposes. I do have "Include Header" checkmarked. The header is read fine by NVDA. But my reviewer is indicating that the table header row is not identified programmatically and needs to be marked up as TH.

How do I do this? I am not a coding person, so you will need to be detailed in any instructions.

Thank you in advance!

Discussion (4)

Fair enough.

I am using Lectora 19.0.4. The course is hosted on Moodle. I believe it was tested in Chrome. I use Firefox, but don't know what I am looking for when using NVDA.

When I publish and go to the table, it reads the column headings fine. I am thinking it may be yet another Chrome issue.

I wanted to attach one of the tables, but even after stripping away everything but the table and zipping it, I can't get the file size down enough to attach to this message. And I don't have anywhere I can put it for download.


I don't know the answer to your question, but I do know that the experts can help you better if you give more details. For instance, what version of Lectora are you using? What LMS? Have you tested it in different browsers/different screen readers?

The very best thing you could do would be to upload a zip export of the course, or a cut-down version of the course with only the problem page in it.

If you select the table and choose the property "Include Header" in the Table section of the Ribbon under TEXT -> PROPERTIES, the header row will be identified using the HTML TH tags. I just tested a short course and the TH tags are present. If you'd like to share your course so we can look at it in eLearning Brothers Customer Support Team, please export the whole course to a ZIP and upload to the following link:

Thank you!

@jholland I do have the "Include Header" marked. Using Firefox and Chrome with NVDA, it is read just fine. Does the TH tag affect something different?

I tried to upload a page (published as offline) as a zip file, but it was too big even with everything stripped out (navigation, background, page number, etc.).