4.2 Accessibility Basics (ARIA) Flashcards

(18 cards)

1
Q

What is accessibility (e11y) in web development?

A

Designing websites so the all users, including those with disabilities, can use them.

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

Why does accessibility matters?

A

It promotes inclusions, improves usability, & may be required by law.

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

How does semantic HTML improve accessibility?

A

Screen readers can understand page structure without extra attributes.

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

When should you leave alt=””?

A

For decorative images that don’t convey information.

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

What is the <label> tag role in accessibility?</label>

A

Associates text with form controls, improving usability for screen readers.

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

What is ARIA in web development?

A

ARIA ( Accessible Rich Internet Applications) is a set of HTML attributes that add accessibility features to complex UI elements.

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

What does aria-label do?

A

Adds a text label to an element when a visible label isn’t available.

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

What does aria-labelledby do?

A

Links an element to another element’s ID that serves as a label.

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

What is an ARIA role?

A

Defines the purpose of an element for assistive tech, e.g, role=”button”.

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

Should ARIA attributes replace semantic HTML?

A

No, use semantic HTML first; ARIA should only enhance when necessary.

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

What is a screen reader?

A

A tool that reads aloud content on a web page for visually impaired users.

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

How do screen readers interpret the page structure?

A

They use HTML semantics & ARIA to announce headings, roles, & landmarks.

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

What are landmark roles in ARIA?

A

Predefined roles like banner, navigation, main, and contentinfo that help users navigate by region.

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

Can aria-hidden=”true” hide elements from screen readers?

A

Yes, it removes the element from accessibility APIs.

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

What’s a common accessibility mistake with ARIA?

A

Overusing it instead of relaying on semantic HTML.

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

What browser tools help test accessibility?

A

Tools like lighthouse, axe, & browser dev tools with accessibility tabs.

17
Q

What should every <form> control have for accessibility?

A

An associated <label>, aria-label, or aria-labelledby.</label>

18
Q

Should form validation use visual cues only?

A

No, it should include text & ARIA alerts for screen reader compatibility.