Open Bug 1708041 Opened 4 years ago Updated 9 months ago

Internal links in PDF do not work with screen reader

Categories

(Firefox :: PDF Viewer, defect, P3)

defect

Tracking

()

Accessibility Severity s3

People

(Reporter: bdahl, Unassigned)

References

Details

(Keywords: access, Whiteboard: [pdfjs-accessibility])

When a document has links to sections (e.g. a table of contents), activating the links doesn't move the screen reader cursor to the page or section. This can be seen in the PDF specification.

The way this is handled on the web normally is that the page URL gets "#target" appended, the a11y engine gets notified that the page is scrolling to the element with id target and the a11y engine notifies a11y clients. I notice that activating an internal link doesn't append a "#target" to the page location. However, I see the links do have suffixes like "#G4.776894", though the id "G4.776894" doesn't exist in the document. In order for this to work, there would need to be an element with that id to which the screen reader should scroll.

From https://bugzilla.mozilla.org/show_bug.cgi?id=1705139#c1

Whiteboard: [pdfjs-accessibility]
Keywords: access
Type: enhancement → defect
Severity: -- → S3
Priority: -- → P3
Accessibility Severity: --- → s3
You need to log in before you can comment on or make changes to this bug.