Web Accessibility Principles

Question 1

True or False

Designating the language of a web page in the markup isn’t necessary because screen readers can rely on the user’s default settings.

Answer 1

False, If a user speaks two languages and visits web sites in both languages, the screen reader will not automatically switch between languages unless the web page itself specifies which language to use.

Question 2

How can you simplify the reading level of a page?

Answer 2

• Break up text into sections with headings, shorter paragraphs, and lists
• Include enough space between lines of text
• Avoid long, complex sentences that use unfamiliar words.
• Avoid unfamiliar technical jargon or slang.

Question 3

True or False

Using “slang” is “fire”

Answer 3

False! Using culturally-specific words or concepts can be confusing or easily misunderstood.

Question 4

True or False

Accessibility guidelines require us to provide alternative formats (images, audio, or video) for all text content to accomodate those who cannot read.

Answer 4

False, converting all text to images, audio, or video would be an undue burden on most organizations.

Question 5

Is consistancy related to accessibility?

Answer 5

Yes. A consistent look and feel, navigation, tab order, and componet design make the experience easier and more predictable for people with disabilites.

Question 6

When designing an input field with specific constraints, what types of information needs to be visibile to the user?

Answer 6

• A field is required
• A button is read-only or disabled
• The data must be in a certain format
• A password must be a minimum number of characters and/or it must consist of both numbers and letters, or must have an uppercase letter, or must have a special character, etc.
• The total number of characters cannot exceed a certain threshold

Question 7

True or False

When you are asking a user to input data, you need to provide instructions at the beginning of the interaction to explain what they should do.

Answer 7

True

Question 8

When a user submits a form or interacts with a component in a way that submits data to a server, you should confirm that the interaction has taken place right away and tell the user whether it was successful or not.

Answer 8

True

Question 9

What does POUR stand for?

Answer 9

The four accessability principles:
* Percievable
* Operable
* Understandable
* Robust

Question 10

True or False

Operability is about making the input methods of web content functionally available to a wide range of input devices.

Answer 10

True

Question 11

Explain the concept of “In, Within, Through, and Out” as it relates to operability.

Answer 11

A user has to be able to navigate into web components, use the features within them, navigate through them, and navigate out of all of them, no matter what input device they’re using.

For example, keyboard users must be able to navigate into a JavaScript drop-down menu, select a link within that menu, or move past the menu if they want to, all without using a mouse.

Question 12

True or False

You should use scripts to create dynamic interactions for all components.

Answer 12

False

You can break the functionality of native components or create device-specific custom components that are unusable with the input methods that you didn’t take into account.To the extent possible, you should use device-independent event handlers rather than device-specific event handlers.

Question 13

True or False

When creating dynamic interactions, it’s important to control the focus.

Answer 13

True

For example, when you create a popup modal dialog, ensure that the focus automatically lands on the modal dialog. When a user exits the modal dialog, ensure that the focus returns to the previous focus location. If the focus gets lost, it usually reverts back to the top of the document, and the user is forced to navigate back down to the previous location, wasting the user’s time and efforts.

Question 14

True or False

It’s important to consider how much time a user will need to complete a given task.

Answer 14

True

Some elements, such as forms, can take a long time to fill out. Forcing an automatic session timeout can cause the user to lose all of the data entered. Session timeouts are allowable as long as you give the user sufficient warning, for example in a popup notification (and ensure the notification is accessible).

Question 15

True or False

You can accomplish near-universal operability of your web content by making it keyboard-accessible.

Answer 15

True

You still need to make content accessible to mouse users and test for mouse accessibility. There are some specialized input devices that emulate mouse functionality, such as through eye gaze tracking or other means.

Question 16

True or False

If you can use web content with a keyboard and with a mouse, chances are very high that you can use it on most every other device.

Answer 16

True

There are exceptions, as you might imagine, but those exceptions are uncommon.

Question 17

True or False

ARIA (“Accessible Rich Internet Applications”) provides a wealth of capabilities for dynamic content that were very difficult or impossible to achieve before.

Robust

Answer 17

True

Question 18

What would you use to indicate the Name, Role and Value of interactive components?

Robust

Answer 18

ARIA (“Accessible Rich Internet Applications”)

Question 19

True or False

Robustness is about ensuring compatibility with a broad range of user agents, including assistive technologies.

Robust

Answer 19

True

Question 20

True or False

All screen readers handle content the same including all possible combinations of user agents.

Robust

Answer 20

False.

Different versions of screen readers also handle content differently, with newer versions featuring better support for newer technologies such as ARIA. It would be impossible to support all possible combinations of all user agents. There are too many to take into account, and some of them simply aren’t robust enough themselves to handle the kinds of things that are necessary for ideal accessibility.You’ll have to draw a line in the sand somewhere and say that you’ll support a specific browser only back to version X, or that you won’t support browser Y because its user base is so small and/or because the browser doesn’t have a feature set that is rich enough.