microsoft / microsoft/BotFramework-WebChat

Accessibility Issue - Input fields and visual labels are not associated

Open
#4,468 1 comment 0 reactions 1 assignee View on GitHub

@compulim is already working on this.

Since Oct 27, 2022.

area-accessibility blocked customer-replied-to ExemptFromDailyDRIReport external-adaptive-cards icm
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

Issue Description : -

If a relationship between elements is expressed with visual cues, it also needs to be programmatically determined. This enables assistive technology to communicate the relationship to users. Content may otherwise seem unstructured or disorganised.
There are form fields that are not associated with their visual labels. The purpose of the form fields may be unclear to users.

Success Criteria : -

Any relationship presented through visual cues must also use the appropriate semantics. Make sure that form fields are associated with their visual labels. In this case, wrap the visual label such as “Please give us some more…”, “First name”, “Last name” and “Email address” within the element. For example:

<label for="i1"...>
<span ...>Please give us some more details to help us respond
<span...>Required

<textarea id="i1" aria-required="true" ...></textarea>

Avoid using multiple labelling techniques on the same form field. For example, using and aria-label together will cause the aria-label to overwrite the . As well, using aria-labelledby will overwrite any other labelling techniques.

17_1
17_2

Steps to reproduce

  1. Observe the visual labels for the form fields.
  2. Inspect the form fields and review the DOM.
  3. Observe that the visual labels are not associated with the form fields.
  4. Observe that there is not an alternative labelling method that serves the same purpose

Webchat Version :- 4.13.0

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.