Live data from Hacker News

Oh shit, my app is successful and I didn't think about accessibility

jacobbartlett.substack.com

71–80 of 302 posts

Re: Oh shit, my app is successful and I didn't think about accessibility

#71

It's amazing how many people in this thread are seriously suggesting that these a11y features are not important. Do HN readers not understand that someday they will grow old, and their eyesight will fail, and they will find themselves increasing the font size on their devices?

I used to bring up accessibility concerns quite a lot on HN. I have stopped however, because it is always the same story. It doesn't seem to matter how nice I am about it, or how accommodating I am towards people just hacking. I never want to stop people's creative spirit. Ever. But I'm one of those people who uses a screen reader. If your app does not work with them, it will not work for me. The amount of weirdly hostile responses I get really puts me off commenting here, so I just don't do it anymore. That doesn't make the issue go away, but it also just does not help. This isn't entirely unique to HN. It is very easy to dismiss accessibility concerns if you're not affected by them, or don't have anyone close that is. I try not to take it personally, but when many people chime in with comments like it's OK that you can't use this app, you're a minority, your burdens aren't anybody elses, and don't listen to them and go make a cool thing without regard, (not an exaggeration it's all in my comment history) it's a bit hard not to be put off by it. If I was able to change one or two minds with my little comments, then I'm very happy about that because maybe it means I get to use your next cool app too. I'm just not going to look for it here, and if I find an accessibility flaw, HN will definitely not be where I comment about it. I've gotten some genuinely good responses too. Some of you also tried to defend my point of view. Like Sam. And I'm very grateful for that. Sadly it's the same fight every single time, and I'm a little bit exhausted by it.

Re: Oh shit, my app is successful and I didn't think about accessibility

#73
I do my best to make all of my apps at least vision-impaired accessible.

The last app, I figured a way to make that easier to manage, and reward use by non-disabled folks.

I have a long-press help feature. If you long-press on any element in the UI, up pops a popover, with a header, and body text, pointing at the element. The popover explains that element.

It's fairly easy to have a long-press gesture recognizer applied to the main view, and dynamically figure out which element was hit. I then look for the accessibility items. If they are there, I do the popover.

I use the accessibilityLabel for the header, and the accessibilityHint for the text. It works extremely well, and no one has ever had it pop up when they weren't specifically trying for it.

Re: Oh shit, my app is successful and I didn't think about accessibility

#75

It's amazing how many people in this thread are seriously suggesting that these a11y features are not important. Do HN readers not understand that someday they will grow old, and their eyesight will fail, and they will find themselves increasing the font size on their devices?

Almost nobody is suggesting this and you can reply to whoever you think is wrong about something. It says 'sneer' in this thing but those are the values of 'sneer' that include 'harangue':

Please don't sneer, including at the rest of the community.

https://news.ycombinator.com/newsguidelines.html

Re: Oh shit, my app is successful and I didn't think about accessibility

#76
post #49

Earlier quoted context omitted.

[flagged]

Bad analogy. Preparing food unhygienically is bad for everyone at the picnic. A more appropriate analogy is disallowing watermelon at the picnic because one person can't eat watermelon. > Please go play badminton. Love the irony of including this comment in a post about making your app inclusive

>> Please go play badminton.

> Love the irony of including this comment in a post about making your app inclusive

Why is that ironic? There's a broad gap between being unable to use an app due to a disability, and unwilling to write apps that will be usable to people with disabilities. One is an immutable characteristic of a person, and the other is a personal choice to be calous. Inclusivity doesn't mean you can't kick people out for being jerks.

And in this case, if I were to hire a developer for an app, and they were so dismissive of accessibility concerns, I would end their interview with abrupt and direct feedback and the law would be on my side.

Re: Oh shit, my app is successful and I didn't think about accessibility

#77
Fun fact: it's far more than 16% because people tend to forget the two super most obvious accessibility requirements: being able to read text, and being able to interact with elements. About half of the planet has a visual disability that's bad enough to require a corrective medical device, and over 10% of the planet is just plain old. Tiny UI elements and small text are easily overlooked, huge problems.

Re: Oh shit, my app is successful and I didn't think about accessibility

#79
post #5

What is the real liability for a scenario like this? Is there any grace period when a new app or startup becomes far more successful far sooner than expected? I imagine A11Y isn't a massive concern when it's not certain an idea will even work; outside of California I can't imagine being legally skewered if, once you attain unexpected success, you devote A11Y resources to address this issue.

I've worked for a couple of large corporations who were sued for accessibility issues.

This was about 5-6 years ago though and I was told back then that there was a number of people who are deliberately scouring the internet for websites with accessibility issues so they can sue them for not complying with US accessibility laws. These lawsuits I believe can be fairly costly for large organisations – I know I was given numbers in the millions, but I was on the technical team so I can't say for sure whether that number is accurate.

In one of the cases I was involved with we were given a period of time to take remedial action to make our site accessible otherwise we could face additional fines. I'd assume if you have a reasonable excuse that the penalties and remediation period would be more lenient.

I'll also add I'm from the UK, but our websites served US customers and our lawsuits came from the US. I believe the UK has similar accessibility laws, but I guess we don't have the same culture of suing businesses.

Re: Oh shit, my app is successful and I didn't think about accessibility

#80
post #72

Isn't it quite ironic to use a numeronym like a11y for the word accessibility?

Amusingly: you'd think, but by being a uniquely new "word", it's actually far more discoverable.

Searching for "a11y" will find you results for accessibility specifically as it relates to web/app technologies, whereas searching for "accessibility" will find you results relating to everything. Of course that only works if everyone agrees to use it, but thankfully, everyone agreed to use it.

Post reply on HN