The Best Of The Internets

This is a great resource for understanding how to use the power of CSS when working in multiple languages.

I love this portmanteau!

Lableism: The act of intentionally removing web form labels and replacing them with placeholder text. Usually done in an effort to make form fields more aesthetically pleasing, while leaving blind and low vision users out in the cold.

This brief post offers some great advice for building resilient designs for any time, but which are especially relevant right now. In particular:

This isn’t the time to get precious about your favourite design and development tools. Use progressive enhancement as your philosophy. Your service might have to be accessed on old devices, in hospitals with outdated tech, or unsupported operating systems. HTML+CSS is your best bet to ensure that the service can be accessed in unlikely scenarios you haven’t even considered. Do you want to take that risk at a time like this? Me neither. Save the React squabbles for another time. Make it accessible and robust from day 1. Use the tools and components already at your disposal, and rely on the work others have done, to make them usable by everyone, to get you further more quickly.

Loving this easy to follow guide to inclusive design in Adobe’s Spectrum design system docs!

This is an exhaustive look at CSS counters and is well worth your time.

Oftentimes, if you cannot do something on your own, the common response is “just ask for help.” However, this is not an appropriate response to a person with a cognitive disability, as they should be able to access the web with the same independence as a person without a disability.

Amen!

This is a must-read!

Ethan delivered a powerful talk at New Adventures. It covers a wide range of topics including design, power, inequality, and more. Moreover it offers some suggestions for what we can do to make the web (and the world) better.

David does a great job of selling devs on PWA as a viable approach for their projects in this extensive post.

The bigger the pipe, the more we’ll shove into it. This is an important piece from Scott Jehl. You should give it a read.

This problem is on us. Yes, we need to better prioritize our asset delivery, but most importantly, we need to stop delivering so much JavaScript. We need to audit our script inventory, and scrutinize our 3rd party integrations regularly, as many of these packages are abandoned or meant to be short-lived. … We should do whatever we can to keep our team members aware of their own impact, across all roles.

Following up on Jason’s post, Adrian offers some forms advice to Indiegogo.

It was immediately apparent that the fields had no accessible name. Despite the visible text label, nothing was programmatically associated.

C’mon people. It’s 2019. Use a fucking label and associate it with the field using the for attribute. If you can figure out React (or Angular or whatever), you can absolutely figure this out.