You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The link (anchor tag) in the table of contents do not have accessible name.
Web browser and its version
Chrome Version 133.0.6943.142 (Official Build) (arm64)
Operating system and its version
Mac OS Ventura 13.7.4
PDF.js version
4.10.38
Is the bug present in the latest PDF.js version?
Yes
Is a browser extension
No
Steps to reproduce the problem
Open a pdf which has headers and navigate to table of contents in the side bar. The content list items are links which use anchor tags. They do not have accessible names.
What is the expected behavior?
The elements should have accessible name, role and state. We could use hidden buttons for accessibility purpose even though we need links on UI to navigate to the section upon click.
What went wrong?
Missing name, role and status of table of content list items
Link to a viewer
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Attach (recommended) or Link to PDF file
The link (anchor tag) in the table of contents do not have accessible name.
Web browser and its version
Chrome Version 133.0.6943.142 (Official Build) (arm64)
Operating system and its version
Mac OS Ventura 13.7.4
PDF.js version
4.10.38
Is the bug present in the latest PDF.js version?
Yes
Is a browser extension
No
Steps to reproduce the problem
Open a pdf which has headers and navigate to table of contents in the side bar. The content list items are links which use anchor tags. They do not have accessible names.
What is the expected behavior?
The elements should have accessible name, role and state. We could use hidden buttons for accessibility purpose even though we need links on UI to navigate to the section upon click.
What went wrong?
Missing name, role and status of table of content list items
Link to a viewer
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: