Ensure Clientside Validation error messages are accessible.
WCAG Criteria: 3.3 Input Assistance -> 3.3.1 Error Identification
aria-invalid=trueWCAG Criteria: 3.3 Input Assistance -> 3.3.3 Error Suggestion
role="alert" so that they are announced when users tab out of the field.Logic was added to toggle true/false for the attribute aria-invalid on all form elements. Also the aria-describedby attribute is added to the form element if the element is in an error state referencing the error message.
Logic was added to add role="alert" to the error messages so that they are announced when users tab out of the field.
This patch represents a quick fix, since it only addresses
case 5: // CLIENTSIDE_VALIDATION_AFTER_INPUT
of the Webform Validation component.
I am working on a more complete fix, adding the Accessibility attributes wherever they are needed, which I plan to report as a Feature Request to the 7.x-1.46+0-dev branch.
Active
4.0
Code
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Let's make this a feature request.
Would probably be good to review the description again after 5 and a half years.
Tasks:
aria-live="assertive" or role="alert" on error message containers. This ensures screen readers announce new errors as soon as they appear.aria-describedby.