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

SC 2.4.3 (Focus Order) requires that focus moves in a logical sequence; modal dialogs must also manage focus containment within them.

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

aria-live regions inform assistive technologies to announce dynamically updated content (e.g., status messages) without requiring user navigation.

Question 3

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

Accepted Answer

for (matching input's id)

Answer

The 'for' attribute on a <label> linked to the input's 'id' creates an explicit association that assistive technologies can communicate.

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 keyboard trap occurs when focus enters a component but the user cannot move focus away using standard keyboard commands, violating WCAG SC 2.1.2.

Question 5

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

Accepted Answer

Level AAA

Answer

WCAG SC 1.4.6 (Contrast Enhanced) at Level AAA requires a contrast ratio of at least 7:1 for normal text.

(PEAT) Practice Exam & Assessment Tool Practice Test