Closed Bug 1723421 Opened 4 years ago Closed 4 years ago

[XFA] Headings not exposed for accessibility

Categories

(Firefox :: PDF Viewer, defect, P1)

defect

Tracking

()

VERIFIED FIXED
93 Branch
Accessibility Severity s3
Tracking Status
firefox-esr91 --- fixed
firefox91 --- disabled
firefox92 --- verified
firefox93 --- verified

People

(Reporter: Jamie, Assigned: bdahl)

References

Details

(Keywords: access)

Attachments

(2 files)

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 h to move to the next heading.
    • Expected: NVDA should say "APPLICATION FOR VISITOR VISA (TEMPORARY RESIDENT VISA) heading level 1"
    • Actual: NVDA says "no next heading"

Semantic headings make it much easier for screen reader users to know that a piece of text is a heading (rather than having to guess based on context), as well as making it much more efficient to navigate between sections.

I'm not sure how XFA encodes this information, but it is exposed correctly in Acrobat Reader. Pdf.js could expose this by using the attributes role="heading" aria-level="n", where n is the heading level.

Assignee: nobody → bdahl
Severity: -- → S3
Status: NEW → ASSIGNED
Priority: -- → P1
Commit merged into master by GitHub Authored by Brendan Dahl (brendandahl)
Depends on: 1724461

:bdahl, now that bug 1724461 is closed, can this be closed as well? That is, is there any reason this fix wouldn't have been included in that update?

Flags: needinfo?(bdahl)

(In reply to James Teh [:Jamie] from comment #3)

That is, is there any reason this fix wouldn't have been included in that update?

The patch landed in bug 1724461, let's just close this one as fixed :-)

Flags: needinfo?(bdahl)
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED

I have verified the fix using the steps above in Windows 10 with NVDA.
Furthermore, I have also verified the fix in MacOS 11 with VoiceOver by using hotkey VO + CMD + H for next heading command.
Also verified in Ubuntu 20 with ORCA by using the H key to jump to the next heading.

All PDF headings (Levels 1, 2 and 3) are exposed and correctly read by all three Screen Readers.

Status: RESOLVED → VERIFIED
QA Whiteboard: [pdf_xfa_generic]
Depends on: 1741445
Target Milestone: --- → 93 Branch
Accessibility Severity: --- → s3
Whiteboard: [access-s3]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: