adobe / adobe/pdfservices-node-sdk-samples
Missing Issue Location
- Dominant language
- HTML
- Stars
- 109
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
The PDF accessibility check outputs accessibility issues it encounters but fails to identify where those issues occur. Is there any way to add the location of the failure?
When scanning a document that has lots of pages, it's hard to understand where the failure is.
Attaching example output from the services API. This output was achieved using the [basic demo.](https://developer.adobe.com/document-services/docs/overview/pdf-services-api/howtos/pdf-accessibility-checker-api/)
[accessibilityChecker2025-04-04T23-56-29.json](https://github.com/user-attachments/files/19760763/accessibilityChecker2025-04-04T23-56-29.json)
Contributor guide
Research direction
Start with the attached accessibility checker JSON and the linked basic demo to determine what location information the services API currently returns. Trace how that response is presented in this Node.js samples repository; done means the reported accessibility failures identify their document locations when the API provides them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- accessibility, api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100