Search

Nalezeno "a11y": 12

a11y is web accessibility


Eric Bailey eviscerates the notion that the term “a11y” isn’t accessible. It’s a hot take that I’ve had myself, embarrassingly enough. I never see people asking why WWI is written out the way it is, either. Won’t people confuse that with the first Wonder Woman movie?...

a11y is web accessibility


Eric Bailey eviscerates the notion that the term “a11y” isn’t accessible. It’s a hot take that I’ve had myself, embarrassingly enough. I never see people asking why WWI is written out the way it is, either. Won’t people confuse that with the first Wonder Woman movie?...

Reduced Motion Picture Technique, Take Two


Did you see that neat technique for using the <picture> element with <source media=""> to serve an animated image (or not) based on a prefers-reduced-motion media query? After we shared that in our newsletter, we got an interesting reply from Michael Gale: What about folks who love...

The difference between keyboard and screen reader navigation


There are a few differences between keyboards and screen readers and Léonie Watson highlights of them: When using the tab key, keyboard focus and screen reader focus are synchronised with each other. The rest of the time, screen reader users have an enormous range of commands at their disposal...

Color contrast accessibility tools


Accessibility is all the rage these days, specifically when it comes to color contrast. I’ve stumbled upon a couple of tools this week that I think are pretty nifty for helping make sure that all of the text on our websites is legible regardless of what background color they might have. First...

Naming things to improve accessibility


I like the this wrap-up statement from Hidde de Vries: In modern browsers, our markup becomes an accessibility tree that ultimately informs what our interface looks like to assistive technologies. It doesn’t matter as much whether you’ve written this markup: in a .html file in Twig, Handlebars...

Some Notes About Accessibility


Earlier this month Eric Bailey wrote about the current state of accessibility on the web and why it felt like fighting an uphill battle: As someone with a good deal of interest in the digital accessibility space, I follow WebAIM’s work closely. Their survey results are priceless insights into...

Accessibility is not a “React Problem”


Leslie Cohn-Wein's main point: While [lots of divs, inline styles, focus management problems] are valid concerns, it should be noted that nothing in React prevents us from building accessible web apps. True. I'm quite capable (and sadly, guilty) of building inaccessible interfaces with React...

The ineffectiveness of lonely icons


Icons are great and all, but as we've been shown time and time again, they often don't do the job all by themselves. Even if you do a good job with the accessibility part and make sure there is accompanying text there for assistive technology, in an ironic twist, you might be confusing people...

Managing Heading Levels In Design Systems


Heydon Pickering looks into how to give a React component a certain heading (like <h1>, <h2>, etc.) depending on its context and thereby ensure that the DOM is still perfectly accessible for screen readers. Why is using the right heading important though? Heydon writes in...

Solved With CSS! Dropdown Menus


A common UI pattern that we see on the web are dropdown menus. They’re used to display related information in pieces, without overwhelming the user with buttons, text, and options. Somewhere that we see these a lot is inside of headers or navigation areas on websites. Let’s see if we can make...

Nahoru
Tento web používá k poskytování služeb a analýze návštěvnosti soubory cookie. Používáním tohoto webu s tímto souhlasíte. Další informace