Responsive and Accessible Design
Transcript
Made automatically from the video's sound, so it may contain mistakes. Click a line to play from there.
Right, let's jump straight into this explainer and kick off arc 4. We're skipping the absolute basics today, so no colour wheels or font anatomy, and we're diving straight into making our entire interface bend fluidly. We are going to engineer visual clarity for every single human eye, thumb and keyboard out there.
So having completely dialed in our depth, surfaces, and motion physics in our last session, really perfecting that Z-axis elevation, those concentric corners and the 180 millisecond motion physics. We're now ready to take our fictional canopy app to the absolute next level.
We want it to bend flawlessly from tiny 320 pixel phone screens and 400% zoom settings right the way up to ultra-wide displays without missing a single beat. Here is our roadmap for today. First, we'll move beyond breakpoint slop, tackle intrinsic containers, accessible tables and typography, focus rings, visual archetypes, and finish off with a quantified craft checklist.
Okay, section one. Beyond the breakpoint slop. Let's look at fixing those brittle layouts. We have all seen these common mistakes, especially in typical AI-generated SAS templates.
Just look at the left side. This is what happens when a developer just slaps a three-column grid onto a desktop breakpoint. At an 820 pixel tablet split screen, you get these completely crushed 18-character columns.
It's unreadable. Bump the browser zoom to 400%, which is actually a WCAG 1.4.10 reflow requirement, and you get those disastrous horizontal scroll bars. Plus, you'll spot 14 pixel mobile inputs triggering that incredibly jarring iOS Safari auto zoom, and that low contrast grey-on-gray text, which is quite literally the number one accessibility defect on the web.
Oh, and relying purely on red colour for validation errors? Massive fail. But the absolute worst part is that the keyboard focus states have been completely stripped out.
On the right, though, we have intrinsic accessible craft. This completely shatters the myth that WCAG 2.2 compliance forces you into some sterile government form aesthetic. Intrinsic and fluid containers.
Now, what's brilliant about container queries is that by defining a container type of inline size, we finally stop guessing viewport widths and start responding to the actual available space. For years, media queries forced us to style components based on the entire screen, but now an element just queries the size of its parent's box.
So a card component knows exactly how much room it has, whether it's sitting luxuriously in a wide main content area, or squashed up into a narrow sidebar. It's a total game changer. If we apply this to canopy and isolate just the fluid responsiveness, first we bin those rigid desktop grid columns entirely.
Then, taking a page out of Ahmad Shadid and every layout book, we wrap Canopy's feature cards in intrinsic container queries. The result? These cards pivot beautifully between a horizontal layout and a vertical stack based purely on the parent width.
No more viewport guesswork. Alright, section three. Accessible tables and typography. Let's talk about scaling data elegantly.
This quote from accessibility expert Adrian Roselli is absolutely crucial. It reminds us that using CSS Clamp for fluid typography isn't some magic bullet. Don't get me wrong, Clamp is fantastic. It lets us set a minimum size, a preferred fluid size, and a maximum, but you have to ensure it passes WACAG 1.4.4 resize text requirements.
If you lock down that maximum too aggressively, a user literally might not be able to scale the text to 200%. So we have to rigorously test with browser zoom, perhaps even using a fallback class to revert to standard relative REM units if a zoom event is detected.
Now let's see how we refactor Canopy's wide three-tier pricing comparison for a narrow 320 pixel phone. It is vital that we use native HTML table tags here. If you try to force a reflow using CSS display properties, some browsers will literally break the semantics, leaving screen reader users completely stranded.
And please do not just slap ARIA grid rolls on there as a quick fix. Those are for interactive widgets, not data. Instead, we use sticky headers to keep context when scrolling, and we test mercilessly at 400% zoom to ensure we pass that WCAG reflow requirement without causing a horizontal scrolling nightmare.
Up next, section 4 focus rings and thumb targets. Let's make things properly interactive. Okay, using the focus visible pseudo class is how we maintain gorgeous aesthetics for mouse users while keeping critical wayfinding for keyboard users.
Historically, the standard focus pseudo class added a ring every single time a user clicked a button with a mouse. Designers obviously hated that and just stripped it out using outline non, which is a complete disaster for anyone navigating via keyboard.
Focus Visible actually fixes this by using browser heuristics to figure out the input modality. Click with a mouse, no ring. Tab with a keyboard, the focus ring appears clearly exactly when it's needed.
Sticking to these exact mathematical constraints doesn't restrict your design, it actually engineers a vastly more tactile and resilient experience. We lock sign-up inputs to at least 16 pixels to kill that annoying iOS autozoom. We ensure touch targets are a generous 44 by 44 pixels.
Yes, WCAG 2.5.8 requires 24 by 24, but aiming for 44 accounts for hand tremors and makes it infinitely more touchable. For focus rings, they must have at least a two-pixel thick perimeter and a 3 to 1 contrast ratio.
Honestly, you should implement Sarah Suaden's brilliant dual-band focus rings. They remain perfectly legible over light backgrounds, dark mode, or even busy hero photos. Let's look at section 5, three distinct visual archetypes, balancing all this accessibility with actual aesthetics.
Because the truth is, accessibility and stunning design are not mutually exclusive. If anything, WCAG AA constraints sharpen your brand character. Archetype A proves this. It's a warm editorial vibe that uses fluid typography with beautiful optical serifs.
It hits that strict 4.5 to 1 text-contrast ratio, but does it using rich, warm incon paper tones instead of harsh black and white. And the mobile pricing tables stack flawlessly, giving you a premium reading experience that just so happens to be highly accessible.
But hey, if your brand leans more technical, the exact same math creates a razor-sharp, data-dense interface. Crisp Suisse uses those intrinsic container queries to build dense, highly readable data grids.
The focus rings are high contrast, jewel-band keylines that look intentionally engineered. We also ensure that one-pixel borders survive forced colours mode, so users with high contrast OS settings still get a perfectly structured utilitarian look.
And finally, our third archetype, the Tactile Craft Brand. This shows how these specs naturally support a very friendly, touchable aesthetic. We're talking generous 44 to 48 pixel thumb-friendly controls and ample mobile safe areas so you aren't stretching your thumb across the glass.
The focus visible states aren't harsh lines, they are warm, glowing dual ring halos that practically invite you to interact. It feels incredibly polished without looking generic. The Quantified Craft Checklist.
I highly recommend grabbing a quick screenshot of this slide. These are the exact Figma auto layout thresholds, webflow breakpoints, and CSS specs you need to anchor your logic. Always check your reflow at 320 CSS pixels for that 400% zoom check.
Lock in 4.5 to 1 contrast for normal text and 3 to 1 for UI borders and focus rings. Keep your mobile text inputs at 16 pixels or larger, and give your focus rings a solid 2 pixel perimeter with a 2 pixel offset. By baking these numbers straight into your workflow, accessibility just becomes an automatic byproduct of your design.
So, with the maths and the methods fully laid out, the question isn't whether you have to design accessibly, but why you would ever choose not to. Once you understand the why behind these constraints, you're empowered to build incredibly resilient digital spaces.
Make sure you stick around because up next we have a 15 minute exercise where we'll design a 320 pixel, 400% zoom pricing table with custom focus rings. That's going to perfectly tee up our next session on creating a consistent visual system.
Until then, keep crafting.