Bird
Raised Fist0
SASSmarkup~10 mins

Accessibility utility generation in SASS - Interactive Code Practice

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to create a utility class that visually hides content but keeps it accessible to screen readers.

SASS
.sr-only {
  position: [1];
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
  border: 0;
}
Drag options to blanks, or click blank then click option'
Aabsolute
Bstatic
Cfixed
Drelative
Attempts:
3 left
💡 Hint
Common Mistakes
Using position: relative or static which keeps the element visible.
Not setting clip or overflow properties.
2fill in blank
medium

Complete the mixin to generate a utility class that hides content visually but keeps it accessible.

SASS
@mixin sr-only {
  position: [1];
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
  border: 0;
}
Drag options to blanks, or click blank then click option'
Astatic
Babsolute
Csticky
Dfixed
Attempts:
3 left
💡 Hint
Common Mistakes
Using fixed or static positioning which either fixes the element or keeps it visible.
Forgetting to set clip or overflow properties.
3fill in blank
hard

Fix the error in the utility class that should visually hide content but keep it accessible.

SASS
.sr-only {
  position: [1];
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
  border: 0;
}
Drag options to blanks, or click blank then click option'
Aabsolute
Brelative
Cfixed
Dstatic
Attempts:
3 left
💡 Hint
Common Mistakes
Using relative or static position which keeps the element visible.
Incorrect clip syntax without commas.
4fill in blank
hard

Fill both blanks to create a mixin that generates a utility class for screen reader only content.

SASS
@mixin sr-only {
  position: [1];
  clip: [2];
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  white-space: nowrap;
  border: 0;
}
Drag options to blanks, or click blank then click option'
Aabsolute
Brect(0, 0, 0, 0)
Cfixed
Drelative
Attempts:
3 left
💡 Hint
Common Mistakes
Using fixed or relative position which does not hide the element properly.
Using clip without commas or incorrect values.
5fill in blank
hard

Fill all three blanks to create a reusable accessibility utility mixin with customizable position, clip, and white-space properties.

SASS
@mixin sr-utility($pos: [1], $clip: [2], $ws: [3]) {
  position: $pos;
  clip: $clip;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  white-space: $ws;
  border: 0;
}
Drag options to blanks, or click blank then click option'
Afixed
Brect(0, 0, 0, 0)
Cnowrap
Drelative
Attempts:
3 left
💡 Hint
Common Mistakes
Using fixed position which may cause unexpected behavior.
Forgetting commas in clip property.
Using normal white-space which allows wrapping.

Practice

(1/5)
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