Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Yeah Section 508 compliance is really big in the US and it's starting to take shape in Europe now as well it's really not fun to code and you have to jump through lots of hoops in order to be fully compliant
Had my fair share of 508 projects I can tell ya 😋 -
jeeper59668yWhere's the money in this? I don't see where not being able to access a website entails payment to a litigant.
-
@jeeper if you visit a web site to purchase somethings you need to provide a quality of service to fully able and impaired users that is comparable. Therefore you need to consider things like color blindness (red/green for example) you can't represent items on a page just by using colour in those cases so you have to have descriptive text and also make the pages visible to screen reading software. Flickering images or animations that have a flickering effect are also issues as flickering at a certain frequency can trigger epileptic fits. Then there are the forms of user input such as screen keyboards and even the flow of the page.
You would be surprised exactly what you need to do to achieve full Section 508 compliance and it's taken very seriously in the US and is backed by the law. This doesn't just apply to ecommerce sites it also applied to any intranet enabler application ... For the same reasons given above
....... I've dealt with a few lol -
emes0013198yI don't think it's as wide-spread in the commercial sector as it is for federal. Having said that, here's a case study against Target (the store): https://w3.org/WAI/bcase/...
Some random company just sued one of my eCommerce client for web accessibility 🙌🏼
undefined