bcgov / bcgov/bcparks-ar-api

Accessibility -> Multiple form labels have been associated with the form controls

Open
#255 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2
Forks
12
PR merge metrics
No merged PRs in 30d

Description

## Description
**How to replicate:**
* Navigate to the A&R website on the test environment: [A&R Admin](https://d3ahrzu0mpndj3.cloudfront.net/enter-data/frontcountry-camping?date=202210&parkName=TEST%20PARK&subAreaId=TEST&subAreaName=TEST%20SUBAREA&orcs=TEST)
* Log in and navigate to the “Enter Data” page
* Select a month, Park and a Sub-area, and click “Go”
* From the list of facilities, select one to add information using the “Edit” option.
* On the resulting page check for the form labels.
eg:

![Image](https://github.com/bcgov/bcparks-ar-api/assets/145403218/3acb5612-b513-4c98-8739-b3547f4fbd83)

**Expected Behavior:**
* The form controls on all the pages should have relevant form labels to be able to read by assistive technologies. One label should be associated with one form control.

**Issues:**
* The form controls have been associated with multiple form labels. This issue can be seen on all form controls on the Enter data forms.
eg:

![Image](https://github.com/bcgov/bcparks-ar-api/assets/145403218/7a7eb94d-c662-4f75-8634-6ca2ca85eac8)

![Image](https://github.com/bcgov/bcparks-ar-api/assets/145403218/5ce38b03-8688-4365-b622-3633d400b80b)

## Linked issues

relates to
- [x] ~[BRS-822](https://bcparksdigital.atlassian.net/browse/BRS-822)~

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked A&R Admin test environment and follow the reproduction steps to inspect the Enter Data forms and their form labels. Review how each control is exposed to assistive technologies, then verify that every control has one relevant associated label across the Enter Data pages.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.