Made a table spanning multiple pages accessible. In JAWS 2023, after announcing the table end, JAWS returns to the beginning of the table instead of proceeding to the next page.
Example:
Tag multi page table
It doesn't matter whether you use the tags or not.
Test with JAWS 2023.
When JAWS announces the table end, it returns to the first cell of the table. The user is trapped in an endless loop.
Test with JAWS 2022.
No problems. JAWS reads the table fine and proceeds to the next page at the end of the table as it should.
Expected result
What did you expect to happen? JAWS should read the table and after it ends, JAWS should read the following page.
Actual result
What actually did happen? JAWS returned to the first cell of the table, trapping the user in an endless loop.
Example
I cannot provide an example due to my NDA. You'll have to create a test multi-page table yourselves.
I created a test document to prove what is happening.
Here's my updated report, documents and screenshots.
Summary
Made a table spanning multiple pages accessible. In JAWS 2023, after announcing the table end, JAWS returns to the beginning of the table instead of proceeding to the next page.
Example:
Tag and remediate multi page table
It doesn't matter whether you allow PDFMaker to tag, use Acrobat's autotag or manually tag - same outcome for all 3.
It doesn't matter whether you include or not - same outcome.
Test with JAWS 2023.
After JAWS announces the table end, it returns to the second cell of the header row of the table. The user is trapped in an endless loop and is unable to advance to subsequent pages in the document.
Test with JAWS 2022.
No problems. JAWS reads the table fine and proceeds to the next page at the end of the table as it should.
Expected result
What did you expect to happen? JAWS should read the table and after it ends, JAWS should read the following page.
Actual result
What actually did happen? JAWS returned to the second cell of the table, trapping the user in an endless loop.
Example
I created a sample table in MS Word, converted to a PDF using PDFMaker, then remediated the PDF. I originally encountered this issue in a PDF that was created in InDesign (which I cannot share due to my NDA).
Summary