Web Accessibility

Question 1

Who published the Web Content Accessibility Guidelines (WCAG)?

Answer 1

the World Wide Web Consortium (W3C)

Question 2

What does WCAG stand for?

Answer 2

Web Content Accessibility Guidelines (WCAG)

Question 3

What does ATAG stand for?

Answer 3

Authoring Tool Accessibility Guidelines

Question 4

Design consideration for blindness: Why should all web content be presented in text or via a text equivalent (alt text)?

Answer 4

Screen readers cannot read non-text content (e.g. images) directly but they can read alt text that you provide.

Question 5

Design consideration for blindness: Why should information not be conveyed by visual attributes alone? (e.g. color, spatial location, thickness of text)

Answer 5

Not all visual information is available to screen readers.

Question 6

Design consideration for blindness: Why should ALL functionality be available using the keyboard?

Answer 6

It is more effective for them to navigate by the keyboard.

Question 7

Design consideration for blindness: Why should all web content use markup with good structure and semantics (headings, landmarks, tables, lists, etc.).

Answer 7

Screen reader users often pull up lists of headings, landmarks, and other semantic elements to help them understand what is on the page. They can also navigate by these elements

Question 8

Design consideration for blindness: Why should all custom controls (expand/collapse buttons) have the correct correct name/label, role, and value, and must change value when appropriate (aria-expanded=”false” changes to aria-expanded=”true”)?

Answer 8

Unlike native HTML elements, custom controls have no semantic parts natively, so screen readers can’t tell users what the widget is and can’t update users on the properties of the widget unless you supply that information via ARIA names, roles, states, and properties.