Given the sheer amount of cyclist who think that cars should be banned with no consideration for anything else, I think that this is a common observation.
Where I live, the pro-cyclist mayor (whose husband owns a bike rental shop, by pure coincidence) closed a road for cars without consultation, now the firemen along with residents are protesting because emergency and delivery vehicles can't access a large part of the city (car parked can't get out!). This is the average behavior you can expect from militant cyclists, from my experience.
Riga. Of course, all of the cyclist absolutely LOVE it, and now want to remove cobblestones, which could lead to a removal of the city from the UNESCO World Heritage list. But they don't care.
Based on the photo, it looks like it’s pretty easily rectified by emergency bollards that can be lifted / lowered by emergency crews, though those may be expensive to procure.
I think accessibility is a really admirable thing and helpful to society (like ramps or parking). But stop shoving your wants on others when you can fix it on your own. Just write a chrome plugin using ai that adjusts css to set contrast ratio of your choice. Can even use a local llm to figure out replacement colors.
Accessibility that can be had on client side should not be a concern on server side.
That's a really terrible option for the vast majority of people who simply lack that kind of tech savviness to be able to do it. And in my opinion, it's kind of selfish.
It also doesn't solve the issue if somebody is browsing your site on a mobile phone where the extension might not even work properly.
WCAG is not difficult - but it does require some modicum of effort.
Obligatory “have Claude write one for you” (in jest of course). All kidding aside, folks have always underestimated how much accessibility helps even those who don’t think they need it.
Right? "Build your own extension" to fix a website's accessibility problems is the equivalent of telling somebody who is disabled to stop complaining about the lack of ramps when they can just modify their wheelchair with a jetpack.
stop shoving your wants on others when you can fix it on your own. Just write a chrome plugin using ai that adjusts css to set contrast ratio of your choice. Can even use a local llm to figure out replacement colors.
Stop shoving your wants on others when you can fix it yourself.
Just get some concrete and some lumber, and build that wheelchair ramp.
You can even hire a contractor to follow you around town all day building them as needed.
as a comparison, i think the wheelchair itself is people making their own accessibility.
the wheelchair is not built into the site, and only requires a few hooks or the odd helping hand to work.
mapping back to software, and especially websites, your user agent is your user agent. it should render websites in the way you want to see them, regardless of what colours the designer chose.
an AI accessibility browser is more like a wheel chair than a ramp
I opened a blank document and pasted a fairly large markdown text. Converting it to word (or html) formatting is easy, there are online tools and/or any other LLM can do it. This one time I opened the Copilot willingly and was excited about getting it done with a few keystrokes: "convert to word formatting".
It generates a formatted response but cant edit the document. How stupid you have to be to integrate copilot and not allow it to update text in a text editor??!
reply