DQ – Module 11: Custom JavaScript ARIA Widgets ARIA Concepts

Created on January 01, 2023

DQ - Module 11: Custom JavaScript/ARIA Widgets ARIA Concepts

1 / 11

ARIA attributes like aria-expanded, aria-checked, and aria-busy convey what information to screen reader users?

The roles of elements.

The states of elements.

None of the above.

The names of elements.

2 / 11

It is best to use actual HTML elements instead of pseudo HTML roles so developers don't always have to create functionality for elements by using JavaScript.

False

True

3 / 11

The difference between aria-live="assertive" and aria-live="polite" is that aria-live="assertive" waits for a screen reader to finish its current statement before announcing new content.

False

True

4 / 11

All of the following are ways to communicate the names of elements, EXCEPT:

role="name"

<label>

aria-labelledby

aria-label

5 / 11

Which type of ARIA roles are used to convey the layout of a web page?

Landmark roles

Widget roles

Pseudo HTML roles.

Abstract roles

6 / 11

ARIA is a programming language that communicates information like names, roles, and values to screen readers.

True

False

7 / 11

Which ARIA attribute is used to provide additional information about an element?

aria-label

role="description"

aria-describedby

aria-labelledby

8 / 11

Which role should be assigned within an application region to give screen readers access to regular text in the region?

Main role

Document role

Note role

Presentation role

9 / 11

The purpose of ARIA roles is to:

Define what the element is.

Identify the state of the element.

Provide the name of the element.

None of the above.

10 / 11

aria-label and aria-labelledby consistently work for labelling non-semantic elements such as <div> and <span>.

False

True

11 / 11

Assigning role="application" to a region disables most screen reader keystrokes within the region to allow developers to create custom keystrokes.

True

False

Your score is

The average score is 0%

0%