This technique demonstrates how aria-invalid may be employed to specifically identify fields that have failed validation. Its use is most suitable when:
The error description does not programmatically identify the failed fields
The failed fields are identified in a manner that is not available to some users - for example by using an error-icon rendered visually by some technique that does not rely on color such as a visual cue like a border.
Note: One of the above two situations may be true for a field which has programmatically associated label and / or instructions that conveys data format, a data range, or the required property.
While it is always preferable to programmatically associate specific error description with the failed field, the page's design or the framework employed may sometimes constrain the author's ability to do so. In these cases, authors may programmatically set aria-invalid to "true" on the fields that have failed validation. This is interpretable mainly by assistive technologies (like screen readers / screen magnifiers) employed by users who are vision impaired. When a field has aria-invalid set to “true”, VoiceOver in Safari announces “invalid data” when the field gets focus; JAWS and NVDA notify the error as an “invalid entry”.
This ARIA attribute has to be set / turned on programmatically. It should not be set to “true” before input validation is performed or the form is submitted. Setting aria-invalid to “false” is the same as not placing the attribute for the form control at all. Quite understandably, nothing is conveyed by assistive technology to users in this case.
When visible text is used to programmatically identify a failed field and / or convey how the error can be corrected, setting aria-invalid to "true" is not required from a strict compliance standpoint but may still provide helpful information for users.
Aria-invalid and aria-describedby are used together to indicate an error when the personal identification number (PIN), email address, or start date are not in the expected format. The error message is associated with the field using aria-describedby, and aria-invalid makes it easier to programmatically find fields with errors.
Below is the rendered HTML code for the email address field in Example 1: When an invalid email address is entered by the user such as "samexample.com" (instead of sam@example.com), the HTML code is:
<div class="control"><p><label for="email">Email address: [*]</label> <input type="text" name="email" id="email" class="error" aria-invalid="true" aria-describedBy="err_1" /></p> <span class="errtext" id="err_1">Error: Incorrect data</span></div> And when no data is entered in the email field, the HTML code is:
<div class="control"><p><label for="email">Email address: [*]</label> <input type="text" name="email" id="email" class="error" aria-invalid="true" aria-describedBy="err_2" /></p><span class="errtext" id="err_2"> Error: Input data missing</span></div> jQuery code: jQuery is used to add aria-invalid or aria-describedby attributes as well as the class attribute and append the error text. This is the code that inserts aria-invalid and class="error" but does not associate the error text "incorrect data" with the control programmatically:
$(errFld).attr("aria-invalid", "true").attr("class", "error");// Suffix error text: $(errFld).parent().append('<span class="errtext">Error: Incorrect data</span>'); CSS Code:
input.error { border: red thin solid;}span.errtext {margin-bottom: 1em; padding: .25em 1.4em .25em .25em;border: red thin solid; background-color: #EEEEFF;background-image:url('images/iconError.gif');background-repeat:no-repeat; background-position:right;} Resources are for information purposes only, no endorsem*nt implied.
- G83: Providing text descriptions to identify required fields that were not completed
- G85: Providing a text description when user input falls outside the required format or values
- G139: Creating a mechanism that allows users to jump to errors
- SCR32: Providing client-side validation and adding error text via the DOM
- ARIA18: Using aria-alertdialog to Identify Errors
- ARIA19: Using ARIA role=alert or Live Regions to Identify Errors
Procedure
For each form control that relies on aria-invalid to convey a validation failure:
Check that
aria-invalidis not set to true when a validation failure does not exist.Check that
aria-invalidis set to true when a validation failure does exist.Check that the programmatically associated labels / programmatically associated instructional text for the field provide enough information to understand the error.
Expected Results
Checks #1-3 are true.
If this is a sufficient technique for a success criterion, failing this test procedure does not necessarily mean that the success criterion has not been satisfied in some other way, only that this technique has not been successfully implemented and can not be used to claim conformance.
