Design, before Any SoftwareLesson 63 of 74

Module 6 · Real screens, real thumbs, real paper

The accessibility requirements that are design decisions

In this lesson

  • 9 min read
  • 5 reading sections
  • Knowledge check
  • Lesson 8 of 10 in this chapter

This chapter’s goalProduce a layout that works at 360 CSS pixels one-handed in daylight, at 400% zoom, and on paper with correct bleed and resolution, naming for each constraint the specific number it imposes and which design decisions change because of it.

This chapter’s media

The film explains chapter ideas. The audiobook narrates the complete teaching text.

FormatEnglishहिंदी
Chapter filmWatch1:49Not available
Full audiobookNot availableNot available

A little at a time

Explore an idea, try it, then check what stays.

Step 1 of 7Free · no account needed
Lesson steps

Follow the task with a keyboard

Start at the top of a page and use Tab, Shift+Tab, Enter and Space. You should be able to tell which control has focus, activate it and recover from an error. Keep the browser’s focus indicator or provide a visible one that works on every surface it crosses. Focus Visible and Focus Not Obscured (Minimum) are separate WCAG 2.2 AA criteria. A sticky footer can entirely cover a focused control even when its ring would otherwise be visible.

CSS
:focus-visible {
  outline: 2px solid currentColor;
  outline-offset: 2px;
}

Your place and first choices stay on this browser. Classroom credit is recorded separately.

Stuck on something?Ask Meher, your AI tutor

How to cite: Addaly (2026) ‘The accessibility requirements that are design decisions’, in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/accessibility-beyond-contrast (Accessed: 21 November 2026).