Forms Flashcards
What are the most important attributes of accessible labels?
- Labels must be meaningful, i.e., they must clearly explain the purpose of the field.
- Labels must be programmatically associated with their control.
- Labels must be visible at all times.
- Labels must be in close proximity to their control.
What’s a form input’s “accessible name”?
its label
True or False: icons should not be used as form labels.
False
Icons MAY be used as visual labels (without visual text) if the meaning of the icon is visually self-evident AND if there is a programmatically associated semantic label available to assistive technologies.
The most recommended method to programmatically associate a label and form field is:
A. aria-label attribute
B. title attribute
C. Explicit <label> association
D. Implicit <label> association</label></label>
C. Explicit <label> association</label>
Why is the use of placeholder text as a form label bad for accessibility?
A. The default color for placeholder text does not meet color contrast requirements
B. Placeholder text disappears when data is entered in the field
C. Placeholder text is not supported in most browsers
D. A and B
E. All of the above
D. A and B
The default color for placeholder text does not meet color contrast requirements
Placeholder text disappears when data is entered in the field
Which of the following statements about labels is NOT correct?
A. Labels should be visually close to their corresponding form fields.
B. Labels must be programmatically associated with their matching elements.
C. Labels should be close to their corresponding form fields in the DOM.
D. Labels should be close in length to the other labels on the page.
D. Labels should be close in length to the other labels on the page.
True or false: When multiple visible labels are used to label one field, the best attribute to associate each label with the field is aria-label.
False
use ` aria-labelledby`
True or false: When one visible label is used to label multiple fields, such as the three parts of a telephone number, each individual field must have a screen reader accessible label.
True
What are two ways related form controls can be programmatically grouped?
- The HTML solution consists of using a <fieldset> to semantically group the form fields and a <legend> to provide a semantic group label.
- The ARIA solution consists of semantically grouping fields within a group region and providing a semantic group label using the aria-labelledby attribute.
NOTE: VoiceOver does not yet support role=”group” as a way to label a group of form elements. For this reason, <fieldset> and <legend> are still preferred over role=”group”.
What are three options for adding instructions to a group of form fields?
- add instruction text to the
legend
of afieldset
(only if short) - Associate the instructions with one of the fields (usually the first field is best) within the group, using
aria-describedby
- Put the instructions before the start of the whole form, as regular text not associated with anything, and hope that screen reader users read them before jumping in to form mode.
Putting regular text in the middle of a form runs the risk that screen reader users will not hear it because if they’re tabbing only to focusable elements, they will skip over all non-focusable text, unless that text is programmatically associated with a group label or an input.
How should you identify required form fields?
- The
aria-required="true"
indicator should be set on the input. The HTMLrequired
attribute would also work, but it changes browser behavior. - A supplemental visible indicator should be available to sighted users.
Which of the following methods does NOT programmatically associate form instructions with their associated fields?
A. Using aria-describedby on the <input></input> element
B. Providing instructions in regular text nearby the <input></input> element
C. Placing instructions in the <label> element
D. Placing instructions for a group of fields in the legend</label>
B. Providing instructions in regular text nearby the <input></input> element
Instructions that aren’t placed visually near their corresponding form fields can negatively impact which of the following user categories?
A. Users who are blind
B. Users who have low vision
C. Users with vestibular disorders
D. All of the above
B. Users who have low vision
Which of the following methods is NOT a best practice for progressive form updates?
A. Provide a summary of users’ choices at the end of the form before submission
B. Include only one step on the screen at a time
C. Number the steps in the form
D. Manage keyboard focus as users move forward and backward through the form
E. Make dynamic changes in the form anywhere in the DOM
E. Make dynamic changes in the form anywhere in the DOM
Changes should only occur later in the DOM
To conform to ARIA specification, all of the following methods should be applied when creating a custom checkbox within a form EXCEPT:
A. Provide a visible and programmatically-associated label for the checkbox
B. Ensure the checkbox is assigned role=”checkbox”
C. Convey to users the state of the checkbox through toggling aria-expanded values
D. Make sure the Space bar can be used to change the state of the checkbox
C. Convey to users the state of the checkbox through toggling aria-expanded values