Input Methods

Question 1

Name 3 key concepts in keyboard accessibility.

Answer 1

• focus
• functionality
• user control

Question 2

What do you call a UI element that you can’t tab away from?

Answer 2

keyboard trap

Question 3

True or false: focused elements must always be visible on screen.

Answer 3

true

sighted users should be able to see focus at all times

Question 4

True or false: headings should be focusable when tabbing around the page

Answer 4

false

active UI elements must be focusable

inactive elements such as headings, paragraphs, lists, tables, images, and so on, should not be focusable when you tab around the page

Question 5

What’s the minimum pointer target size as of WCAG 2.2 AA?

Answer 5

24 x 24 px

Question 6

What’s the minimum touch target size of actionable elements?

Answer 6

44px x 44px with at least 6px space between elements

Question 7

What are the 5 allowable exceptions to the touch target size rules?

Answer 7

1. Spacing: The target offset is at least 24 CSS pixels to every adjacent target;
2. Equivalent: The function can be achieved through a different control on the same page that has an area of at least 24 by 24 CSS pixels;
3. Inline: The target is in a sentence or block of text;
4. User agent control: The size of the target is determined by the user agent and is not modified by the author;
5. Essential: A particular presentation of the target is essential or is legally required for the information being conveyed.

Question 8

What are the four input methods that must be supported for full accessibility?

Answer 8

1. mouse
2. keyboard
3. touch
4. voice

Question 9

The mouse cursor becomes a hand pointer when the mouse cursor hovers over which of the following native HTML elements?

A. Buttons
B. Links
C. Text fields
D. A and B

Answer 9

B. Links

Question 10

Which elements need to be keyboard-focusable?

Answer 10

Links, buttons, and anything interactive

Question 11

What should be the primary means of keyboard interaction within an ARIA widget?

Answer 11

users tab to the widget, then use the arrow keys to navigate within the widget

Question 12

What should be the logical progression of the focus when a person opens and then closes an ARIA dialog?

A. The focus should go to the dialog, then back to the original button that opened the dialog.
B. The focus should go to the dialog, then back to the top of the original web page.
C. The focus should go to the top of the page, then to the dialog, then back to the top of the page.
D. The focus should go to dialog, then back to the browser address bar.

Answer 12

A. The focus should go to the dialog, then back to the original button that opened the dialog.

Question 13

True or false: Screen readers automatically notify users when a web page implements custom keystrokes.

Answer 13

False

Question 14

True or false: If you code a widget to be fully keyboard-accessible when using the arrow keys, touch devices users (without keyboards) will still not be able to use the widget, in most cases.

Answer 14

True

Question 15

True or false: Custom JavaScript gesture events on web pages will probably not work when a touch device screen reader is turned on.

Answer 15

True

screen readers override most custom gestures

Question 16

True or False: The active tab of a custom tab widget should be set to tabindex=”0” so a user can tab to it.

Answer 16

True

All tab panels should have tabindex=”0”