DQ – Module 9: Form Labels, Instructions, and Validation

  • Fee: Free Practice Tests (based on WAS Guide https://www.accessibilityassociation.org/ )
  • Passing score: 95%
  • Time limit: 30 minutes
  • Number of questions: 33
  • Format: Multiple Choice, Multi Answer and True/False
  • Difficulty: Advance
Created on

DQ - Module 9: Form Labels, Instructions, and Validation

DQ - Module 9: Form Labels, Instructions, and Validation

1 / 33

Which of the code examples below best adheres to the requirements and best practices for error feedback?

2 / 33

Which one of the following is NOT a screen reader mode?

3 / 33

Which of the following methods is NOT a best practice for progressive form updates?

4 / 33

Which is NOT a good technique for preventing errors in forms?

5 / 33

Adding the ARIA attribute aria-required="true" tells every user that a form input is required.

6 / 33

The basic keyboard commands for interacting with HTML form controls are common across all screen reader / browser combinations.

7 / 33

Which of the following is the most semantically-appropriate way to associate instructions with an input?

8 / 33

To conform to ARIA specification, all of the following methods should be applied when creating a custom checkbox within a form EXCEPT:

9 / 33

Color must never be used in labels.

10 / 33

Instructions that aren't placed visually near their corresponding form fields can negatively impact which of the following user categories?

11 / 33

Group labels must be available to all users — sighted and non-sighted alike.

12 / 33

What might happen if an aria-live announcement is tied to a blur event in a form?

13 / 33

Which ARIA attribute should be used to provide more information about an error in a form element?

14 / 33

Which of the following statements about labels is NOT correct?

15 / 33

What should happen to the page title if a form submission causes the same page to reload?

16 / 33

As long as a group label is programmatically associated with the group of fields it labels, its location in the DOM does not matter.

17 / 33

The default mode for most screen readers is forms mode.

18 / 33

In terms of accessibility, if error messages are programmatically associated with their form inputs, then providing visible error messages for form inputs is optional.

19 / 33

Why is the use of placeholder text as a form label bad for accessibility?

20 / 33

When multiple visible labels are used to label one field, the best attribute to associate each label with the field is aria-label.

21 / 33

Changes in context can inhibit accessibility when those changes happen automatically and users aren't allowed to request the changes in context.

22 / 33

Using the Tab key to move through a page will put focus on all of the following elements EXCEPT:

23 / 33

Which of the following methods does NOT programmatically associate form instructions with their associated fields?

24 / 33

Which ARIA attribute should be used to identify which form elements have errors?

25 / 33

Regions like aria-live and role="alert" can be used to convey success messages as long as success messages aren't hidden from visual users.

26 / 33

Icons must not be used as labels.

27 / 33

From an accessibility perspective, focusing on a form element must not cause a change of context, but context changes may occur when a user hovers over a form element.

28 / 33

Since plain text is non-focusable, text such as instructions or formatting hints should not be placed in the middle of a form unless the text is programmatically associated with a focusable element.

29 / 33

Custom form elements should be modeled after native HTML form elements.

30 / 33

Which of the following methods can NOT be used to associate a group label with the fields it labels?

31 / 33

The most recommended method to programmatically associate a label and form field is:

32 / 33

Using a different text color for an input's label to convey that input is required may exclude all of the following user categories EXCEPT:

33 / 33

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.

Your score is

The average score is 0%


error: Content is protected !!
Scroll to Top