You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2024. It is now read-only.
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) 2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA) 3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
It is a failure if a form element isn’t programmatically associated with all instructions. This includes legends, labels, hint text and tooltips.
A common way of achieving this is using fieldset and legend tags. Fieldset is used to group a set of elements. Legend is the first child of a fieldset tag and provides context for those fields.
The text was updated successfully, but these errors were encountered:
I noted in the bug tracker that no ARIA labels were found.
This resource identifies all the WCAG success criteria for proper labelling of a form and providing instructions.
Similarly the heading levels on this page don't guide me through the form.
Also, the Month/day/year do not include elements referenced:
The issues I noted above were in Storybook; when I tried accessing anything through VDI it didn't work. The system must be down (VDI, not our app). Will try again next week.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The MVP is ready for form instructions associated with inputs accessibility review:
Log into VDI
Access Benefits Finder MVP in a browser (Try Chrome or Edge)
https://bears-waf.app.cloud.gov/bears/life_event/death
Document issues here
https://docs.google.com/document/d/1DuIBVSXNBw8UmxvrZXEX8pb6MRklNw5vRYDpFLajux8/edit
Focus on form instructions and inputs to follow the 18F recommended critical checklist
https://docs.google.com/document/d/1YLwn3_N9XeeluZNerTojZTc71C1sDhNPDE2OrkU7GOE/edit?usp=sharing
WCAG form guidance is here
18F form testing guidance is here https://accessibility.18f.gov/forms/
Success Criteria:
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA)
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A)
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
It is a failure if a form element isn’t programmatically associated with all instructions. This includes legends, labels, hint text and tooltips.
A common way of achieving this is using fieldset and legend tags. Fieldset is used to group a set of elements. Legend is the first child of a fieldset tag and provides context for those fields.
The text was updated successfully, but these errors were encountered: