Accessibility utility generation in SASS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of accessibility utilities in web development?

Accessibility utilities help make websites usable for everyone, including people with disabilities, by improving keyboard navigation, screen reader support, and visual clarity.

intermediate

In Sass, how can you create a reusable accessibility utility for visually hiding content but keeping it readable by screen readers?

You can create a mixin that applies styles like position: absolute;, width: 1px;, height: 1px;, overflow: hidden;, and clip: rect(0, 0, 0, 0); to hide content visually but keep it accessible.

beginner

Why should accessibility utilities use semantic HTML elements along with CSS?

Semantic HTML provides meaning and structure to content, which helps assistive technologies understand the page better. CSS alone cannot convey meaning, so combining both ensures better accessibility.

intermediate

What Sass feature allows you to generate multiple accessibility utility classes efficiently?

Sass @mixin and @each loops let you create reusable styles and generate multiple utility classes by iterating over lists or maps, reducing repetitive code.

beginner

Name two common accessibility utilities you might generate with Sass.

1. Visually hidden text utility for screen readers.
2. Focus outline utilities to improve keyboard navigation visibility.

Which CSS property is commonly used in accessibility utilities to hide content visually but keep it readable by screen readers?

A opacity: 0;

B clip: rect(0, 0, 0, 0);

C visibility: hidden;

D display: none;

Using clip: rect(0, 0, 0, 0); along with other styles hides content visually but keeps it accessible to screen readers. display: none; and visibility: hidden; hide content from all users including screen readers.

In Sass, which directive helps you create reusable style blocks for accessibility utilities?

A @import

B @function

C @mixin

D @extend

@mixin defines reusable style blocks you can include in multiple places, perfect for accessibility utilities.

Why is it important to include focus styles in accessibility utilities?

A To improve keyboard navigation visibility

B To hide elements from screen readers

C To change font size

D To add animations

Focus styles help keyboard users see which element is active, improving navigation and usability.

Which Sass feature allows generating multiple utility classes by looping over a list?

A @each

B @if

C @while

D @import

@each loops over lists or maps to generate multiple classes or styles efficiently.

What is a key benefit of using accessibility utilities in your CSS?

A They add animations

B They reduce page load time

C They change the site color scheme

D They make your site usable for people with disabilities

Accessibility utilities improve usability for people with disabilities by enhancing navigation, readability, and screen reader support.

Explain how you would create a Sass mixin for a visually hidden accessibility utility and why it is useful.

Think about how to hide content from sight but not from assistive technology.

Describe two accessibility utilities you can generate with Sass and how they improve user experience.

Consider utilities that help users who rely on keyboard or screen readers.

Practice

1. What is the main purpose of accessibility utilities in SASS?

easy

A. To add colorful backgrounds to web pages

B. To make websites easier to use for everyone, including people with disabilities

C. To speed up website loading times

D. To create animations for buttons

Solution

1. Step 1: Understand accessibility utilities

   Accessibility utilities are styles or code that help users with disabilities navigate and use websites better.

2. Step 2: Identify the main goal

   The main goal is to improve usability for everyone, especially those with disabilities, not visual decoration or speed.

3. Final Answer:

   To make websites easier to use for everyone, including people with disabilities -> Option B

4. Quick Check:

   Accessibility = usability for all [OK]

Hint: Accessibility utilities improve usability for all users [OK]

Common Mistakes:

• Confusing accessibility with visual design
• Thinking accessibility speeds up loading
• Assuming accessibility is only for animations

2. Which SASS syntax correctly defines a mixin for hiding content visually but keeping it accessible to screen readers?

easy

A. @mixin sr-only { position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0 0 0 0); }

B. @mixin sr-only { display: none; }

C. @mixin sr-only { visibility: hidden; }

D. @mixin sr-only { opacity: 0; pointer-events: none; }

Solution

1. Step 1: Recall screen-reader-only styles

   Screen-reader-only styles hide content visually but keep it accessible by positioning it off-screen and clipping it.

2. Step 2: Check each option

   @mixin sr-only { position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0 0 0 0); } uses position absolute, tiny size, overflow hidden, and clip to hide visually but keep accessible. The other options hide content completely from screen readers.

3. Final Answer:

   @mixin sr-only { position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0 0 0 0); } -> Option A

4. Quick Check:

   Screen-reader-only = off-screen + clip [OK]

Hint: Use position absolute and clip for screen-reader-only [OK]

Common Mistakes:

• Using display:none hides from screen readers
• Using visibility:hidden also hides from screen readers
• Using opacity:0 does not remove from layout

3. Given this SASS mixin for focus outline:

@mixin focus-outline($color) {
  outline: 2px solid $color;
  outline-offset: 2px;
}

What CSS will be generated by @include focus-outline(blue);?

medium

A. outline: 2px dashed blue; outline-offset: 2px;

B. outline: 2px solid red; outline-offset: 2px;

C. border: 2px solid blue; outline-offset: 2px;

D. outline: 2px solid blue; outline-offset: 2px;

Solution

1. Step 1: Understand mixin parameters

   The mixin takes a color parameter and sets outline with that color and offset 2px.

2. Step 2: Substitute parameter with 'blue'

   Replacing $color with blue gives outline: 2px solid blue; outline-offset: 2px;

3. Final Answer:

   outline: 2px solid blue; outline-offset: 2px; -> Option D

4. Quick Check:

   Mixin color param = blue output [OK]

Hint: Replace $color with argument in mixin output [OK]

Common Mistakes:

• Confusing border with outline
• Using wrong outline style like dashed
• Mixing up color values

4. Identify the error in this SASS mixin for focus outline utility:

@mixin focus-outline($color) {
  outline: 2px solid $color
  outline-offset: 2px;
}

medium

A. Missing semicolon after outline property

B. Incorrect property name 'outline-offset'

C. Using $color without quotes

D. Outline width should be 1px, not 2px

Solution

1. Step 1: Check SASS property syntax

   Each property must end with a semicolon to separate declarations.

2. Step 2: Locate missing semicolon

   The line 'outline: 2px solid $color' lacks a semicolon at the end, causing syntax error.

3. Final Answer:

   Missing semicolon after outline property -> Option A

4. Quick Check:

   Missing semicolon = syntax error [OK]

Hint: Always end SASS properties with semicolons [OK]

Common Mistakes:

• Forgetting semicolons between properties
• Thinking $color needs quotes
• Confusing property names

5. You want to create a reusable SASS utility mixin that generates both a focus outline and a screen-reader-only style. Which of the following is the best combined mixin code?

hard

A. @mixin accessibility-utility($color) {
outline: 2px solid $color;
outline-offset: 2px;
position: absolute;
width: 1px;
height: 1px;
overflow: hidden;
clip: rect(0 0 0 0);
}

B. @mixin accessibility-utility($color) {
border: 2px solid $color;
clip-path: inset(50%);
}

C. @mixin accessibility-utility($color) {
@include focus-outline($color);
@include sr-only;
}

D. @mixin accessibility-utility {
outline: 2px solid black;
display: none;
}

Solution

1. Step 1: Understand mixin reuse

   Best practice is to reuse existing mixins inside a combined mixin for clarity and maintainability.

2. Step 2: Analyze options

   @mixin accessibility-utility($color) { @include focus-outline($color); @include sr-only; } calls existing mixins focus-outline and sr-only, combining their functionality cleanly. @mixin accessibility-utility($color) { outline: 2px solid $color; outline-offset: 2px; position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0 0 0 0); } mixes unrelated styles in one block, which is less maintainable. The other options have incorrect or incomplete styles.

3. Final Answer:

   @mixin accessibility-utility($color) { @include focus-outline($color); @include sr-only; } -> Option C

4. Quick Check:

   Reuse mixins for combined utilities [OK]

Hint: Combine utilities by including existing mixins [OK]

Common Mistakes:

• Writing all styles manually instead of reusing mixins
• Using display:none hides content from screen readers
• Confusing border with outline