PEAT User Interface & Accessibility 3

Question 1

A user testing a web app with a screen reader finds that a modal dialog does not trap keyboard focus. Which WCAG Success Criterion does this violate?

Accepted Answer

2.4.3 Focus Order

Answer

1.4.3 Contrast (Minimum)

Answer

2.1.2 No Keyboard Trap

Answer

4.1.2 Name, Role, Value

Question 2

What is the purpose of aria-live regions in a web application?

Accepted Answer

To announce dynamic content updates to screen readers without a page reload

Answer

To animate content on screen

Answer

To mark regions that require login

Answer

To specify the language of a section

Question 3

Which attribute associates a <label> element with its corresponding form input for accessibility?

Accepted Answer

for (matching input's id)

Answer

aria-label

Answer

name

Answer

placeholder

Question 4

In PEAT's UI accessibility assessment, which scenario is an example of a 'keyboard trap'?

Accepted Answer

Focus enters a widget but cannot be moved away with standard keys

Answer

A link opens in a new tab

Answer

A button requires double-clicking

Answer

An image has no alt text

Question 5

Which WCAG conformance level addresses enhanced contrast (7:1 ratio) for normal text?

Accepted Answer

Level AAA

Answer

Level A

Answer

Level AA

Answer

Level B

Question 6

What is the role of the 'tabindex' attribute in web accessibility?

Accepted Answer

It controls the order and focusability of elements via keyboard Tab key

Answer

It sets the font size for tab labels

Answer

It defines the number of tab stops on a page

Answer

It hides elements from the tab order completely when set to 1

Question 7

According to WCAG 2.1, which type of content is exempt from the color contrast requirement?

Accepted Answer

Inactive (disabled) user interface components

Answer

Body text smaller than 12px

Answer

Bold text at 14pt

Answer

Hyperlinks in navigation menus