`.annotorious-popup-button` anchors exposed to screen reader / keyboard users on public side exhibit pages
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- accessibility, frontend
Research direction
Start by reproducing the issue on a public exhibit page containing an Image Annotation block, then inspect the non-visible .annotorious-popup-button anchors. Done means keyboard and screen-reader navigation no longer reaches or announces the EDIT and DELETE links, for both logged-in and logged-out views and whether or not annotations exist.
Written by the indexing model from the issue text.
Description
When navigating an exhibit page with Image Annotation blocks added to it, focus moves through the non-visible .annotorious-popup-button anchor elements, which produce screen reader announcements of "link, EDIT" and "link, DELETE":
https://github.com/user-attachments/assets/2c58be3c-e3b2-4d60-a4d2-1fd82a43a818
Video description: Navigating an exhibit page via keyboard with a VoiceOver dialog open. Within an Image Annotation block, under the image, focus grabs onto two non-visible elements in sequence, which read out as "link, EDIT" and "link, DELETE".
This is true for viewing as a logged in or logged out user and occurs in all Image Annotation blocks, regardless of if annotations have been added to a given image. These should be hidden to screen readers / keyboard users. This is not specific to a branch and is happening on both render-alt-text and master.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from omeka/plugin-ExhibitImageAnnotation
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
omeka/plugin-ExhibitImageAnnotation#13 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
omeka/plugin-ExhibitImageAnnotation#9 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in omeka/plugin-ExhibitImageAnnotation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cytoscape/cytoscape.js#3597 ·
Maintainers usually reply within 5 days
-
priority: low server testing
Difficulty 1/5 Under an hour Newbie friendliness 88/100
blamechris/chroxy#9277 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
sunososobro-hub/cloudball#191 ·
Maintainers usually reply within 1 day
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
primefaces/primefaces#15568 ·
Maintainers usually reply within 1 day