You should see how ADA requirements are practically impossible or completely break design. The high contrast of font to background requirement is so extreme that most major sites and even ADA related sites fail. Things like alt text is so time consuming it would be incredibly expensive to label all the images. Facebook has long resorted to using AI descriptions.
Really it shouldn't be up to the developer it should be up to the disabled person to buy tools. Just like someone may need to buy a wheelchair to move around, they should have to buy a specialty browser that handles their limited visibility needs or brail tool interface.
> “Really it shouldn't be up to the developer it should be up to the disabled person to buy tools. Just like someone may need to buy a wheelchair to move around, they should have to buy a specialty browser that handles their limited visibility needs or brail tool interface.”
No, that’s the wrong analogy. The ADA is there to ensure that people with wheelchairs can find a barrier-free entrance to a building, and a curb cut at an intersection.
It should be on us, the developers, to ensure our apps work with the tools of the trade to enable people with limitations. So, our apps should be usable by screen readers. The screen reader is the analogue to the wheelchair here.
This is one of the great things about HTML. Even ignorant / lazy / time-constrained developers are likely to output something that sorta works, just since they’re using divs and imgs and whatnot.
And the bar is so low! Adding accessibility labels takes not much effort at all. And, as an added bonus, accessible apps are easier to test, since testing frameworks like Playwright can hook into accessibility info directly to validate assertions.
> find a barrier-free entrance to a building, and a curb cut at an intersection
I disagree with this too. It's a social nicety but shouldn't be a requirement.
> It should be on us, the developers, to ensure our apps work with the tools of the trade to enable people with limitations
Why? I argue it should be on the disabled person.
> The bar is so low.
Not really. There are groups of lowers running around looking for people to shake down for ADA misses. To really protect yourself it takes a lot of time.
> high contrast of font to background requirement is so extreme
Extreme? The WCAG standard for text most organizations use (Level AA) is 4.5:1 with 1:1 being black-on-black and 21:1 being black-on-white (or vice versa). The higher standard (Level AAA) is only 7:1. Most people wouldn't want to read your content if everything was 7:1 or lower.
> Facebook has long resorted to using AI descriptions
Facebook didn't upload those images, their users did, Facebook isn't responsible for them having good text alternatives.
> Just like someone may need to buy a wheelchair to move around
To go along with your poor analogy, blind people have "wheelchair" equivalents, called screen readers. They're useless if don't build "ramps" that meet established building standards, websites and apps that follow established standards.
> Things like alt text is so time consuming it would be incredibly expensive to label all the images. Facebook has long resorted to using AI descriptions.
> Really it shouldn't be up to the developer it should be up to the disabled person to buy tools. Just like someone may need to buy a wheelchair to move around, they should have to buy a specialty browser that handles their limited visibility needs or brail tool interface.
How can buying a specialty browser solve a problem of a blind person needing alt text for images?
You, as a developer, can determine when AI-generated text is good enough for your images—sometimes it is, and sometimes it isn't. A specialty browser cannot, and should not, be trusted to make that decision, so it will need hints from the developer. And, once the developer offers those hints, any mainstream browser, not just specialty products, can make use of them.
It sucks to be disabled and this is why it sucks. People shouldn't be wasting lifetimes of time to so that visually disabled people can be slightly more convenienced to browse the internet or play with an app. Especially with alt-text. Minimal effort is fine. Well structured HTML is all that should be needed.
> How can buying a specialty browser solve a problem of a blind person needing alt text for images?
If a picture is worth a thousand words you're never going to get the alt text right. There can always be complaints it's not good enough. Look at what happened to Dominoes. They made efforts but it wasn't good enough.
> It sucks to be disabled and this is why it sucks. People shouldn't be wasting lifetimes of time to so that visually disabled people can be slightly more convenienced to browse the internet or play with an app.
I think that a big part of why it sucks is that people feel comfortable expressing the idea that working to allow people of all abilities to enjoy the same conveniences is wasting time.
Domino's did not make an effort until they lost in court. They even admitted during the course of the case that the requested fixes would cost like $58,000 to make, far less than the lawyers cost in the case and appeals.
You are arguing they should have been forced to pay 58k for unnecessary site improvements when each place has a phone line that can be called. They did have alt text but it was deemed not good enough. What real value did disabled customers miss out on?
> They did have alt text but it was deemed not good enough.
Did they? Because the suit alleges that they did not have alt text.
> each place has a phone line that can be called.
Ok but what if the person has troubles talking or hearing or dialing the phone?
Accessibility doesn't even take that long. I updated a site I run to be compliant in less than a day. Corporations can afford to meet regulations.
Edit:
According to the lawsuit the phone number was not added too the website until after.
Also from the lawsuit
> But there are substantial reasons to believe that the
phone number does not provide the same level of independence and convenience as does the website and the
mobile app. In particular, as the district court noted,
"callers may experience delays and be placed on hold." Pet. App. 24a. Ambient noise may distract from and interfere with the accurate taking of orders. See p. 8, supra. And giving a credit card number to a live human
being over the phone may create a greater risk to privacy than does submitting that information through a
secure website. See DCt. Dkt. No. 33 at 15.
> But there are substantial reasons to believe that the phone number does not provide the same level of independence and convenience as does the website and the mobile app. In particular, as the district court noted, "callers may experience delays and be placed on hold." Pet. App. 24a. Ambient noise may distract from and interfere with the accurate taking of orders. See p. 8, supra. And giving a credit card number to a live human being over the phone may create a greater risk to privacy than does submitting that information through a secure website. See DCt. Dkt. No. 33 at 15.
This is pure nonsense. So what if you may experience delays or be put on hold. Just because something exists doesn't mean you're obligated to provide it.
"credit card number to a live human being over the phone may create a greater risk to privacy" is absurd, it's the way people been taking credit cards from inception to very recently, either it's not good enough and should be banned all together or it's an acceptable means of charging a card. Plus there is protection from the CC company.
Text contrast multiplies with the monitor contrast, which then multiplies again with eyesight quality. The high contrast requirement is to make it readable for someone with poor eyesight on a low-quality monitor...
Which then makes it downright painful for someone with regular eyesight, who sets their monitor to high contrast to improve photo rendering. Grey-on-grey is the only website design that doesn't make me immediately back away.
As you are using a site that is almost black text against a tan/grey background? For most copy I agree with you. But requiring that level of high contrast for titles, informational text, text over images, or some measure of flair so your site stands out a little it's too much of a requirement.
I get it. It'd be nice if all these major companies used both in and cm. Americans have to go back and forth with metric a lot and it would be useful to think of every day items in terms of both inches and cm.
I guess you still think about PHP when it was version 3 or 4... we're at version 8.3 now and it's definitely not the same thing. Both for language and performance.
I remember looking at some new features and was so hopeful the language would get better but they had some super cargo culty take on something borrowed from another language that completely missed the point. It's a horribly done me too language where the developers don't fully understand what they are "me too"ing.
7.0 had some issues so bad it's almost impossible to find anymore. Seems like they tried to erase it from the internet. The language itself is an attack vector.
You saying I'm flamebaiting? I doubt anyone is going to be offended by PHP being trash, especially anyone that has spent any serious time working with it.
If you are hobbling with a PI it's all about the community support, form factor, low power and the header pins. Hopefully if you are buying a Pi you already have a specific project in mind.
For example: I use a few zero 2 w's with shairport-sync to make Airplay stereos. I use the header pins to control a relay to turn on and off an audio amp. Pi 4+ would actually work a lot better for this especially when playing audio on multiple of these setups at once. A Lenovo mini pc wouldn't be as easy to hide.
I wouldn't go too far down the "community support" thing with the RPi foundation. Careful if you say anything negative, even in a constructive tone, in case Liz shuts your threads down. I had some problems with brownouts on the RPi 2 and posted a technical thread. It was deleted and my account terminated. There are various reports of this from community refugees who switched to other platforms.
I guess by community support is if you want to build something you'll find 100 tutorials on how to do it or it will even be part of the GitHub project. I never visit the official forums. These community mods are crazy with the little bit of power given. I had similar issues with arstechnica.com before it became an echo chamber.
This part is great:
> If anyone at Sony is reading this, please consider that you have (in my opinion) two equally good options: either let it be, or shut this thing down and get a real remaster going.
