DRYD-2130: Accessibility > Missing form label (Criteria 3.3.2) - #27
Merged
Conversation
mikejritter
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this do?
It fixes all the missing form label a11y issues. The main changes are:
Why are we doing this? (with JIRA link)
We need to fix the Missing form label (Criteria 3.3.2) across the application: https://collectionspace.atlassian.net/browse/DRYD-2130
How should this be tested? Do these changes have associated tests?
Please follow the steps in: collectionspace/cspace-ui.js#361
Dependencies for merging? Releasing to production?
no dependencies
Has the application documentation been updated for these changes?
changelog has been updates
Did someone actually run this code to verify it works?
@spirosdi ran it locally