101–110 of 302 posts
Isn't it quite ironic to use a numeronym like a11y for the word accessibility?
Wasn't it chosen because it reads "ally" in leetspeak? Agree it's not incredibly accessible.
Isn't it quite ironic to use a numeronym like a11y for the word accessibility?
Wasn't it chosen because it reads "ally" in leetspeak? Agree it's not incredibly accessible.
>1 in 6 people think your app is broken >16% of people have some kind of accessibility requirement 16% is 4 in 25 people, also no guarantee you'll be able to accommodate their specific accessibility requirement, depending on the app, and depending on the requirement. That's not to say the app shouldn't be accessible, more that, you should think about when you spend the money to implement things like this, and how tha…
That aside, the work of prioritizing accommodations is already done. Just read through the WCAG criteria, start with level A, then AA. They already determined what the most critical issues are to accommodate everyone who uses your app. I find it extremely callous to frame people's ability to use your product in terms of the revenue they have to offer you. A storefront has to build a ramp because everyone deserves basic human decency, not because they want wheelchair users to spend money inside.
Your App is successful because you didn't spend time on useless things like a11y, i18n during the p-m-f stage. If you look at every successful product in history, they didn't focus on a11y or i18n right from the bat. Now, that it is successful, you can think about it and spend resources.
It seems like quite an indictment of the tech sector to say that success happens because accessibility is ignored.
For the last 12 years of his life, my father was in an electric wheelchair as a result of a stroke. Prior to that, I was vaguely aware of ADA compliance - basically because there were posted signs everywhere about parking spaces and restroom stalls. It was only after seeing the ease with which he could navigate the world in spite of his chair that I appreciated how important that law was, because I also saw so many t…
Isn't it quite ironic to use a numeronym like a11y for the word accessibility?
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?
Disability accommodations tend to also strongly benefit everyone else. I know this isn't a code thing, but the most useful one I can think of is curb cuts. All of this affects all of us.
>1 in 6 people think your app is broken >16% of people have some kind of accessibility requirement 16% is 4 in 25 people, also no guarantee you'll be able to accommodate their specific accessibility requirement, depending on the app, and depending on the requirement. That's not to say the app shouldn't be accessible, more that, you should think about when you spend the money to implement things like this, and how tha…
There is a middle ground. There are Free widgets that you can install [0] that can add some accessibility features on top of any existing website/app. Not perfect but takes care of a lot of low hanging fruits. https://userway.org/get/
[1] https://www.accessibility.works/blog/avoid-accessibility-ove...
Wheelchair ramps aren’t limited to wheelchairs. I have above average hearing despite my advancing age and I choose to apply subtitles to digital movies about half the time because it provides me a better more enriching experience. Solving for color contrast limitations benefits everyone even when people have perfect vision.
There are no blind soldiers in the army yet all Army digital communications are required to conform to federal regulations that accounts for accessibility. The result is higher quality products with greater availability.
Usually the best argument opposing accessibility is that the authors/developers don’t know what they are doing. When they say accessibility is too expensive that’s what they really mean, and it’s not a good argument.
I would never agree with this statement of the author: "You won’t stop until everybody is using your app." Why ? All the apps I ever build (or participate in their development) where targeted to the fit the most, without sacrificing the business requirements or other important/critical aspects of the app. Otherwise will end-up with an unusable product.
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.