Carousel Block a11y improvements

Open
#147 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
php

Research direction

No files or tests are named. Locate the Carousel block implementation and reproduce keyboard navigation, checking pagination dots and next/previous arrows for accessible names and focus loss, especially when navigating backwards. Done means those controls are named and focus remains usable throughout keyboard navigation, with additional findings addressed or documented.

Written by the indexing model from the issue text.

Description

a11y

Carousel blocks need another look to fix some accessibility issues, to start:

  • Pagination dots and next/prev arrows are lacking accessible names.
  • Focus becomes lost at times when navigating via keyboard, especially backwards.

There are likely more issues to dig into here, but I just wanted to get an issue up while it was fresh.

Dominant language
PHP
Stars
25
Forks
37
Avg merge
5d 19h
Merged PRs (30d)
1

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-ExhibitBuilder

All issues in omeka/plugin-ExhibitBuilder

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.