Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Contributions - No status message for saving changes

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
php
Domain
accessibility

Research direction

Start in the contributions page's add-a-new-type and contributor sections, and reproduce saving a new type and deleting a question. Inspect the existing status messages and how they are presented after returning to the contribution types page. Done means successful additions and deletions are announced automatically without moving focus, including in the contributor questions section.

Written by the indexing model from the issue text.

Description

a11y

"Description: On the contributions page, in the add a new type section and the contributor section, when users save changes and return to the contribution types page, the "Type successfully added" status message is not automatically announced for the type being added. There is also no status message announcement for deleting a question.

Note: this issue also occurs on the contributor questions section of the page.

Expected Results: When users save changes and add a new type, and a status message appears on the screen, the status message is automatically announced to users without taking focus. Usually with aria live regions.

Actual results: When users save changes and add a new type, there is no status message announcement notifying the user of a successful action."

4.1.3 Status Messages; Level AA; WCAG 2.1

Dominant language
PHP
Stars
10
Forks
14
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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

All issues in omeka/plugin-Contribution

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.