adobe / adobe/adobe.github.com
Export Report to PDF file (Table, Report etc.) consistently shows 16 accessibility failures with checked using Adobe Accessibility Checker (504.2.2 PDF Export)
- Dominant language
- CSS
- Stars
- 1.6k
- Forks
- 379
- PR merge metrics
- No merged PRs in 30d
Description
### Expected Behaviour
PDF file should not have any accessibility issue after converting it from Access.
### Actual Behaviour
Adobe Accessibility Checker shows 16 issues in PDF file.
### Reproduce Scenario (including but not limited to)
#### Steps to Reproduce
Step 1: Open Access application.
Step 2: Open Northwind document.
Step 3: Get the focus on ribbon using Ctrl + F6 key.
Step 4: Navigate on External Data Tab and activate it using keyboard.
Step 5: Navigate on PDF or XPS and activate it using keyboard.
Step 6: Export the file into PDF.
Step 7: Open Adobe Acrobat and navigate on accessibility check and activate it.
Step 8: Verify the accessibility issue on PDF file and observe the issue.
#### Platform and Version
Adobe Version: 2023
#### Sample Code that illustrates the problem
[frmMainMenu.pdf](https://github.com/adobe/adobe.github.com/files/13873589/frmMainMenu.pdf)
#### Logs taken while reproducing problem


Contributor guide
Research direction
Start by opening the linked frmMainMenu.pdf in Adobe Acrobat and running the accessibility checker, following the reported 16 failures. Reproduce the export from the Northwind document through Access's External Data PDF or XPS flow; done means the exported PDF no longer reports accessibility issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100