Collection Tree list structure as it translates over to `select` options

Open
#40 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
28/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
php
Domain
accessibility

Research direction

The payload names no file, so start by locating where the collection select options for the collection edit form are built and where the dash prefixes for nested items are added. The issue asks which representation of hierarchy would work for VoiceOver, NVDA and JAWS, so first agree on an approach in the thread, such as a different text indentation or an optgroup structure. Done means a chosen representation that keeps the tree readable and has been checked with screen readers.

Written by the indexing model from the issue text.

Description

a11y

I'm wondering about an alternate way to represent the hierarchy and nested relationships of the collection tree within the select provided on collection edit forms. The dashes before nested list items are ignored by VoiceOver and NVDA, while JAWS announces each individual dash. So, is there another, better way to communicate these relationships that would also be more globally perceivable to screenreader users?

Dominant language
PHP
Stars
7
Forks
10
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-CollectionTree

All issues in omeka/plugin-CollectionTree

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.