`.annotorious-popup-button` anchors exposed to screen reader / keyboard users on public side exhibit pages

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

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

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from omeka/plugin-ExhibitImageAnnotation

All issues in omeka/plugin-ExhibitImageAnnotation

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.