First, because actual accessibility. Second, because it’s a whole lot easier for me to quickly scroll through a transcript to find the thing I was interested in.
a production-ready output file.
While some static site generators have a standardized way of handling assets, Eleventy does not. That’s a good thing – it gives you the flexibility to
handle this any way you want, rather than forcing an opinionated way of doing things on you that might not fit your specific needs.
That flexibility comes at a price though: you need to figure out your preferred setup first.
Hopefully soon, we’ll be able to define the highlight color or radios and checkboxes using the accent-color CSS property.
I 100% agree with this proposal. Users can only choose to opt in or out if they’re able to make an informed decision about this, and for better or worse, they can’t do that. I’m pretty sure Google will market this as some sort of user-beneficial feature, assuming they tell non-technical users anything at all about this. WordPress, according to its own “bragging”, (I’m using that loosely), powers something like 40% of the web. We can’t continue as a project to pretend we have no impact on it.
Don’t get me wrong. Awareness is great. But we’ve been doing awareness now for I don’t know how many years or even decades, and it just seems to me that for every step forward we take, there are six more going backwards.
If awareness doesn’t become actuion, it’s just feel-good talk. And I’m starting to wonder if all the talk being generated around accessibility isn’t getting to a point where we’re seeing diminishing returns.