Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Accessibility] User is unable to access/read the text using screen reader #514

Closed
4 tasks done
mayukh-ms opened this issue Jan 20, 2020 · 5 comments
Closed
4 tasks done
Assignees
Labels
enhancement New feature or request

Comments

@mayukh-ms
Copy link

mayukh-ms commented Jan 20, 2020

Before you start - checklist

  • I followed instructions in documentation written for my React-PDF version
  • I have checked if this bug is not already reported
  • I have checked if an issue is not listed in Known issues
  • If I have a problem with PDF rendering, I checked if my PDF renders properly in Mozilla Firefox

Description The screen reader doesn't read out the text content of the pdf file being loaded.

Steps to reproduce

  1. Open pdf
  2. Use screen reader to navigate to the content inside pdf.

Expected behavior Screen reader should read out the information.

Additional information
If applicable, add screenshots (preferably with browser console open) and files you have an issue with to help explain your problem.

Environment

  • OS version: 1903 (OS Build: 18362.175)
  • Browser: Microsoft Edge 44.18362.1.0
  • Screen reader: Narrator.
  • React-PDF version: 3.0.6
  • React version: 16.5.2
  • Webpack version: 4.41.2
@wojtekmaj
Copy link
Owner

By default, text layer should be enabled (renderTextLayer should be true). Is that not the case?

@wojtekmaj wojtekmaj self-assigned this Jan 20, 2020
@bjmcc1984
Copy link

Is other accessibility Metadata preserved like semantic structure for headings, form fields, ordered/unordered lists, tables, etc.? Having the text layer is not sufficient for meeting user needs for accessibility all up.

@wojtekmaj
Copy link
Owner

I believe we don't have such information to play with. If you know the exact PDF file being rendered you can create a custom renderer that creates headings e.g. based on font size, but that seems like a horrible idea to me...

@github-actions github-actions bot added the stale label Mar 21, 2022
@wojtekmaj
Copy link
Owner

wojtekmaj commented Mar 21, 2022

Note to self: there's includeMarkedContent option in page.getTextContent. We would need to handle these items somehow though.

Might also be fixed by #944.

Repository owner deleted a comment from github-actions bot Mar 21, 2022
@wojtekmaj wojtekmaj added enhancement New feature or request fresh and removed stale labels Mar 21, 2022
@wojtekmaj
Copy link
Owner

Resolved in #1498.

@wojtekmaj wojtekmaj removed the fresh label Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants