nextcloud / nextcloud/mail

Connect error messages with corresponding input elements

Open
#6,876 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Is your feature request related to a problem? Please describe.

Accessibility issue.

Error messages should be better connected to the input fields they are belongs to. In mail app there is one place, where it takes place: form "connect your mail account".

Error messages were improved within this PR: https://github.com/nextcloud/mail/pull/6099. For good accessibility frontend- and backend error messages have to be connected to the corresponding input fields.

For example the error message: "IMAP username or password is wrong" has no connection to username or password input fields. That the user, which can use only a screen reader will never recognize this error and will not be connected to the input field, where this error belongs to.

Also all frontend messages have to be connected to corresponding input fields.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the “connect your mail account” form and the error-message changes in pull request #6099. Trace the frontend and backend messages for the IMAP username and password fields, then verify that every message is programmatically associated with its corresponding input and is discoverable with a screen reader.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
accessibility, backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.