Recent submissions

Comment · 2 years ago
Cool. Now do google, amazon, fb, Verizon, att, chevron, exxon, gp, oracle, microsoft, etc.
Comment · 2 years ago
> 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.

Comment · 2 years ago
Look at way back machine
Comment · 2 years ago
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?
Comment · 2 years ago
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.
Comment · 2 years ago
It's very high contrast. The comment meta on these posts fail it. I'm pretty any text against the orange in this site fails it too.
Comment · 2 years ago
> 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.

Comment · 2 years ago
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.

Comment · 2 years ago
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.

Comment · 2 years ago
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.
Comment · 2 years ago
Honestly it's a mistake I would make too.
Comment · 2 years ago
I think you think I'm someone else.
Comment · 2 years ago
Not at all. It was still a really cool writeup. Worth the read but just wanted to see an electronics project.
Comment · 2 years ago
Then I wouldn't use Roundcube either.
Comment · 2 years ago
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.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton