3 ms·

> Making your site accessible isn't just a good practice, in the US, it is the law > Courts have rules that the ADA applies to web sites along with any other t

> Making your site accessible isn't just a good practice, in the US, it is the law > Courts have rules that the ADA applies to web sites along with any other type of business For a business like a coffee shop I'd imagine that accessibility is codified in law through things like building regulations (ie, you must have n disabled parking spots per square foot, a disabled toilet, etc) Is there an equivalent legally codified and enforceable standard for the web?

rstupek 6y ago
There is not a codified standard however that doesn't stop websites from being sued
- ogre_codes 6y ago
  If you comply with the WCAG 2.1, you have a pretty good legal defense. While it isn't "Law", it is the most widely known published standard and likely to be added to the law soon. https://www.w3.org/TR/WCAG21/ https://www.w3.org/TR/WCAG21/
udia 6y ago
I have had a lot of success with this course (Web Accessibility, by Google): https://www.udacity.com/course/web-accessibility--ud891 https://www.udacity.com/course/web-accessibility--ud891 > In this course you’ll get hands-on experience making web applications accessible. You’ll understand when and why users need accessibility. Then you’ll dive into the "how": making a page work properly with screen readers, and managing input focus (e.g. the highlight you see when tabbing through a form.) You’ll understand what "semantics" and "semantic markup" mean for web pages and add ARIA markup to enable navigating the interface with a range of assistive devices. Finally, you’ll learn styling techniques that help users with partial vision navigate your pages easily and reliably.
ogre_codes 6y ago
> Is there an equivalent legally codified and enforceable standard for the web? More or less yes. The link I posted has a few good resources, but generally speaking sites need to work with a screen reader and they need to be accessible via the keyboard (which by extension enables other accessibility devices). This site has some more guidelines. https://www.essentialaccessibility.com/blog/ada-guidelines https://www.essentialaccessibility.com/blog/ada-guidelines Generally speaking, if you start with existing components that do the thing you want done, you have a huge leg up. If you try to reinvent the wheel, you are likely in for a lot of trouble. The more complex the control, the harder it is to roll your own. Calendar controls and Selects are particularly tough to get right. UPDATE: Also, the wc3 has some good guidelines which should cover your ass. https://www.w3.org/TR/WCAG21/ https://www.w3.org/TR/WCAG21/
deleted 6y ago
[deleted]

rstupek 6y ago

There is not a codified standard however that doesn't stop websites from being sued

ogre_codes 6y ago
If you comply with the WCAG 2.1, you have a pretty good legal defense. While it isn't "Law", it is the most widely known published standard and likely to be added to the law soon. https://www.w3.org/TR/WCAG21/ https://www.w3.org/TR/WCAG21/

udia 6y ago

I have had a lot of success with this course (Web Accessibility, by Google): https://www.udacity.com/course/web-accessibility--ud891 https://www.udacity.com/course/web-accessibility--ud891 > In this course you’ll get hands-on experience making web applications accessible. You’ll understand when and why users need accessibility. Then you’ll dive into the "how": making a page work properly with screen readers, and managing input focus (e.g. the highlight you see when tabbing through a form.) You’ll understand what "semantics" and "semantic markup" mean for web pages and add ARIA markup to enable navigating the interface with a range of assistive devices. Finally, you’ll learn styling techniques that help users with partial vision navigate your pages easily and reliably.

ogre_codes 6y ago

> Is there an equivalent legally codified and enforceable standard for the web? More or less yes. The link I posted has a few good resources, but generally speaking sites need to work with a screen reader and they need to be accessible via the keyboard (which by extension enables other accessibility devices). This site has some more guidelines. https://www.essentialaccessibility.com/blog/ada-guidelines https://www.essentialaccessibility.com/blog/ada-guidelines Generally speaking, if you start with existing components that do the thing you want done, you have a huge leg up. If you try to reinvent the wheel, you are likely in for a lot of trouble. The more complex the control, the harder it is to roll your own. Calendar controls and Selects are particularly tough to get right. UPDATE: Also, the wc3 has some good guidelines which should cover your ass. https://www.w3.org/TR/WCAG21/ https://www.w3.org/TR/WCAG21/

deleted 6y ago

[deleted]