1723424 - [XFA] Intended document order not exposed to accessibility

Status: NEW

(Firefox :: PDF Viewer, defect, P2)

Description

[James Teh [:Jamie]]

STR (with the NVDA screen reader):

1. Open this PDF in Firefox: https://bug1671648.bmoattachments.org/attachment.cgi?id=9182033
2. Wait a few seconds for the first page to load.
3. Press control+home to ensure you are at the top of the document.
4. Press d to move to the top of the actual content.
5. Press down arrow several times, reading the first few lines of the document.
   • Expected: NVDA should read "PROTECTED WHEN COMPLETED - B", the "Canadian Flag image. Citizenship and Immigration Canada." image (though this is impacted by bug 1723418), "Page of", then the "APPLICATION FOR VISITOR VISA (TEMPORARY RESIDENT VISA)" heading.
   • Actual: After "PROTECTED WHEN COMPLETED - B", NVDA reads "IMM 5257 (06-2019) E", then "This form is made available by Immigration, Refugees and Citizenship Canada and is not to be sold ", etc.

What gets read here might be the order of the text in the document, but it isn't the visual order, nor is it the document order specified by the author for accessibility purposes. This is very confusing for screen reader users. In this example, it requires them to read content that isn't of interest (which is why it is placed at the bottom of the page visually). In other cases, it could be a lot more problematic.

I'm not sure how XFA exposes this information, but it is picked up by Acrobat Reader. It could be exposed by pdf.js either by reordering the DOM or by using aria-owns to reorder the accessibility tree.

Comment 1

[GorgeBush3]

Attachment: link which are not working on moz.txt