Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

T's IAAP WAS Study Notes > 1.4 Accessibility Techniques > Flashcards

1.4 Accessibility Techniques Flashcards

1
Q

Why is it important to code to standards, rather than to the quirks or features of only one set of technologies?

A

Because technologies continually change while standards do not.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Explain the concept of progressive enhancement

A

It is a web design technique that progresses the user experience from basic (on older browsers) up to a more-compelling, fully-featured experience for users of newer browsers and devices with richer capabilities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How is progressive enhancement implemented?

What is the best tool for feature detection?

A

The basic content is served immediately
Then, feature detection (not browser sniffing) determines what else is loaded.
Modernizer is a feature detection tool that works for both CSS and JavaScript.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Why is progressive enhancement important?

A

browsers that don’t support the features you are using in your code won’t display your sites properly and will just fail, creating a bad user experience.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the importance of testing web designs for accessibility across a variety of platforms, browsers, and assistive technologies?

A

To go beyond just conformance and ensure the site works for everyone.
Developers need to be aware of the limitations of specific technologies and provide content in a way that is accessible to people with disabilities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the best browser/SR combos for these platforms: Window, MAC, iOS, Adroid?

A 
Windows = Chrome/NVDA
MAC = Safari/VO
iPhone/iOS = Safari/VO
Adroid = Chrome/TalkBack
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

How to tell if elements or features are inaccessible because of the site design or because of bad technology support?

A

Try coding it to be accessible. *** answer this again once finished with the testing courses at deque.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

how to tell the difference between inaccessible content and incomplete or
faulty accessibility testing techniques.

A

*** answer after studying testing with deque

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

When is it appropriate to write code that overrides, supplements, or fixes bugs in browsers or assistive technologies? (do this only with great
caution!).

A

*** need the answer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What two types of checklists are needed to develop accessible sites?

A

Content Designer Checklist

Content Developer Checklist

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What things should designers keep in mind about the page title? (2)

A

It should describe the topic or purpose of the page

It should be an H1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What things should designers keep in mind about Headings? (2)

A

The headings should look and act like such and be in proper hierarchal order
Do not style headings with html

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What things should designers keep in mind about Navigation? (3)

A

Provide a Skip to Link
Make use of landmarks and regions
Make the content’s reading and focus order logical and intuitive.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What things should designers keep in mind about Links?

A

The text should describe the purpose and destination

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What things should designers keep in mind about Color and Contrast? (4)

A

Information cannot be conveyed by color alone.
Contrast should be at least 4.5 to 1 (3 to 1 for large text)
Links should be distinguished by more than just color.
Interactive elements must show clear focus indicator
Non-text elements important for accessing and understanding content have color contrast of at least 3 to 1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What things should designers keep in mind about Magnification and Responsive Design? (3)

A

Zoom must work on any device
Eliminate horizontal scroll on zoom
Zoom must work in either orientation

17
Q

What things should designers keep in mind about Images? (5)

A

Alt text should provide same information
Alt text for interactive images provides purpose/destination
Info graphics explained fully in the page content and with a short alternative text description
Decorative images defined as such. (no alts)
Use plain text instead of images with text

18
Q

What things should designers keep in mind about Tables?

A

Should have a caption
Should have row and columns identified
Table is simple, has no compound rows or columns

19
Q

What things should designers keep in mind about Forms? (5)

A

Label for each field is visible and adjacent to the field
Labels are descriptive and instructive
Controls must be in close proximity (edit, delete)
Error messages tell how to solve error
Autofill is enabled where useful

20
Q

What things should designers keep in mind about Dynamic Content? (3)

A

Make users aware of new content or put it next in flow
Keyboard-only and touch screen interactions follow expected patterns
Design success and failure feedback into all interactions

21
Q

What things should designers keep in mind about Custom Widgets? (3)

A

Design for standard HTML
Make them keyboard accessible
Must follow WCAG ATAF guidelines

22
Q

What things should designers keep in mind about Touch Devices? (2)

A

Targets need to be large enough and far enough apart

Custom swipe and gestures need an alternate (when screen readers are on)

23
Q

What things should developers keep in mind about Semantics and Structure? (2)

A

Use proper HTML tags for their semantics

Use HTML to define structure, information, relationships

24
Q

What things should developers keep in mind about Readability? (1)

A

The order should be logical for AT users

25
Q

What things should developers keep in mind about Images? (2)

A

Linked or informative images need alt text

Decorative images do not need alt text

26
Q

What things should developers keep in mind about Keyboard and TouchScreen Navigation? (4)

A

Focus is visible, managed, and in a logical order
Functionality can be achieved with just the keyboard
Keyboard and touch interaction follows standards
There are no focus traps

27
Q

What things should developers keep in mind about Tables? (2)

A

Column and row headers convey relationships

Tables used for layout contain only elements

28
Q

What things should developers keep in mind about Form Labels?

A

Programmatically match label to input field
Label is visible
Related fields are grouped and group has own label

29
Q

What things should developers keep in mind about Form Errors? (2)

A

Errors are programmatically matched with field.

SR users are made aware of errors

30
Q

What things should developers keep in mind about Custom Controls? (1)

A

Custom controls need names and roles defined if the HTML does not convey it

31
Q

What things should developers keep in mind about Context Changes (what two things should not trigger them)?

A

Context changes are not triggered by tabbing

Settings changes for user interface controls should not trigger context change

32
Q

What things should developers keep in mind about Timing? (3)

A

The user needs to control scrolling, moving, blinking, dynamic or auto-updating content with stop, pause, hide.
Time limits can be eliminated, adjusted, or extended.
Users are aware of time limits

T's IAAP WAS Study Notes (20 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions