However, today I would like to talk about an area of the framework that is a bit understated. I believe our industry as a whole seriously underestimates the value of customization and user personalization, i.e. users being able to set their own design preferences. Chris has written before about knowing who a design system is made for, pointing out a spectrum of flexibility depending on who a system is meant to help.
I have written a bunch about responsive tables. Maybe too much. This post is meant to simplify that. It will reference previous work, but mostly I am just going to show you the bare minimum you need to make a WCAG-compliant responsive HTML table.
Welcome to Designing in the Browser with our host, Una Kravets. Today we’re diving into navigation and keyboard accessibility. We’ll go over semantic HTML and ARIA roles, document structure (landmark roles), tab-index, and stylized states using :focus as well as the new :focus-within styling.
Interactive touches can be great for user understanding in a digital environment, but they can also leave some of your users disoriented and frustrated, the opposite of the intended effect. So let’s talk about how we can avoid that, and how we can be sure to include our cute animated SVGs and button hovers while also ensuring that users who might get a bit nauseous when seeing a lot of animation in front of them, can also enjoy your site. We’ll be demonstrating how to use the “prefers-reduced-motion” media query to progressively enhance animation into your website, as well as show you how to build a simple “reduce animation” switch.