nextcloud / nextcloud/calendar

Make sure that all input elements are connected to corresponding labels

Open
#4,269 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce

In general, most input fields lack label-texts. Placeholders are used instead, but since that text disappears as soon as the user starts to type in the field this is not enough to comply with this success criterion.

  1. Choose any of input element on the page.
  2. Check, if input has a connected label.
  3. If not - add a right label. If this label should be hidden - there are some techniques to do it:

Implementation suggestion: https://www.w3.org/WAI/tutorials/forms/labels/
https://austingil.com/how-to-build-html-forms-right-accessibility/#Labels

Expected behavior

Every input have to have connected label.

A label and the form-element it identifies must be connected in the code. That way users with assistive technology such as screen readers can easily understand the purpose of the form-element.

Unfortunately, we saw several places where labels and their form-elements aren’t connected, making them challenging to use for screen reader users.

Actual behaviour

Not every input has a label

Calendar app version

No response

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

No response

Database engine version

No response

PHP engine version

No response

Nextcloud version

3.3.2

Updated from an older installed version or fresh install

No response

List of activated apps

No response

Nextcloud configuration

No response

Web server error log

No response

Log file

No response

Browser log

No response

Additional info

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 auditing the Calendar app's pages for input elements and checking whether each has a connected label, using the WAI forms-label guidance linked in the issue. Done means every input has an accessible, connected label, including labels that are visually hidden where appropriate; the issue names no files or tests, so locating all affected views requires project-wide investigation.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, javascript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.