[CST] Review accessibility of claim letter PDFs

[davidakennedy]

Value Statement

As a Veteran I want to access accessible claim letter PDFs So that I can read them and store them how I want to on my own device

---

Background Context

New Feature

We suspect that claim letter PDFs aren't accessible, but we don't exactly what's wrong with the PDFs. In order to potentially deliver accessible PDFs, we need to understand what's making them inaccessible. According to @jstrothman - "While our team doesn't generate the letters, we do deliver them, so I think we should at the very least know what, if any, accessibility issues exist." For more, check out this Slack thread.

Outcome, Success Measure, KPI(S), and Tracking Link

• Add here

Design

From an accessibility perspective, we will:

• Test at one type of each letter via Adobe Acrobat Pro, and via screen reader, and document accessibility problems.

List of letters:

• 184 (doc type) - Decision Notices
• 34 - Correspondence
• 408 - VA Examination Letter
• 700 - MAP-D Development Letter
• 859 - Subsequent Development Letter
• 940 - Final Attempt Letter
• 864 - General Records Request (Medical)
• 1605 - General Records Request (Non-Medical)
• 704 - 5103
• 706 - 5103
• 858 - 5103

Enablement team (if needed)

@jstrothman, for awareness.

Engineering

N/A.

Out of scope

• A lot of the possible fixes may be out of our team's control, and would need to be shared with other teams.

Open questions

• Here, I want to outline what teams control the PDFs, so I can talk to them, if nevessary.

Tasks

• [ ] Audit roughly nine letters.
• [ ] Write recommendations for improvements.

Definition of Done

• [ ] Meets acceptance criteria
• [ ] Passed E2E testing (90% coverage)
• [ ] Passed unit testing (90% coverage)
• [ ] Passed integration testing (if applicable)
• [ ] Code reviewed (internal)
• [ ] Submitted to staging
• [ ] Team approved production verification process
• [ ] Design performs design QA and verifies the implementation matches the design spec
• [ ] Accessibility specialist performs accessibility review (in code or design)
• [ ] Engineering identifies staging users required to test and shares account and credentials with design and product
• [ ] Product performs functional QA and verifies acceptance criteria was met

Acceptance Criteria

• [ ] Mini audit created.
• [ ] Suggest recommendations for improvement

[davidakennedy]

Providing an in-progress update of my work so far:

• I've tested three of the PDF types. None are accessible by meeting requirements per the Adobe Acrobat Pro accessibility checker.
• I'm still tracking down the rest of the PDFs to test.
• Most of the issues are basic, and easy to fix, but that will depend on how they get made, which I'll dig into in another ticket.