Do you have a website? Do you want to get sued?
0 likes48 views
The document discusses the importance of website accessibility, detailing the legal landscape surrounding ADA compliance, which saw a surge in lawsuits in 2017. It emphasizes that inclusive design benefits all users, outlines the Web Content Accessibility Guidelines (WCAG) and their principles, and highlights the upcoming WCAG 2.1 updates. Accessibility is framed as a civil rights issue, emphasizing the need for developers to create websites that are usable by individuals with disabilities to avoid litigation and improve overall user experience.
Do you have a website? Do you want to get sued?
- 1. Do you have a website? Do you want to get sued?
- 3. • MicroAge, Inc • MicroTech • Sierra Nevada Corporation • Honeywell • Allied Signal • Red Bull • US Air • The Salvation Army • Bureau of Land Management • US Fish & Wildlife Service Master Solutioneer, Red Pill Now Devin Olson
- 4. Roy Rumaner • I have been working with IBM/Lotus Notes, • Domino & XPages since 1994 • This is my 6th time presenting at MWLUG • I am currently working for Christian Brothers Services as a Consultant • Previous clients include: Bank of America, Canal Barge Company, PNC Bank, ABN-AMRO, Teledyne, Sierra Nevada Corp., Morey Corp, 4C Technologies, TeamSpace, Uline, Abbott Labs, Tenneco, YMCA, McDonald’s and many more
- 5. “If you can design a website, you can design an accessible one” University of Washington, Do-IT
- 6. Do you have a website? No user should be excluded because of a disability
- 7. Inclusive design is better design for everyone
- 8. You cannot meet the Accessibility Standards without designing for and researching with users with access needs.
- 9. Everyone has abilities, and limits to those abilities
- 10. Remediation takes money and time. Prevention saves money and time
- 11. 2017 Website Accessibility Lawsuit Recap: A Tough Year for Businesses • 2017 saw an unprecedented number of website accessibility lawsuits filed in federal and state courts, and few courts willing to grant early motions to dismiss. • Plaintiffs were very busy in 2017 filing ADA Title III lawsuits alleging that public accommodations’ websites are not accessible to individuals with disabilities. • In 2017, plaintiffs filed at least 814 federal lawsuits about allegedly inaccessible websites, including a number of putative class actions.
- 13. List of Web Accessibility-Related Litigation and Settlements https://github.com/karlgroves/a11y-lawsuits
- 14. The Department of Justice’s (DOJ) rulemaking to create new website accessibility regulations is now officially dead, as was recently blogged. The lack of clear rules will lead to more litigation and inconsistent judicially-made law. In fact, it appears that the DOJ will not be issuing any new regulations under Title III of the ADA about any subject, according to the agency’s December 26 announcement in the Federal Register repealing all pending ADA Title III rulemakings.
- 15. Accessibility Matters If you don’t have to use the Web with a screen reader or without a mouse, you really don’t know what it is like for people with certain disabilities to try use most websites. If you don’t believe what I say about the difficulties, unplug your mouse for the day. Still not convinced?
- 16. • There are nearly 70 automatically detectable issues on each page of the web – before accounting for contrast issues. • Color contrast issues are, by far, the most pervasive issues. • 28% of all images on the web have no alt attribute at all. • Another 15% of alt attribute values are completely worthless things like “graphic”. • role attributes, when used, are equally likely to be used wrong – for arbitrary string values that have no basis at all in the ARIA specification. • 81% of buttons on the web have no useful text for their accessible name.
- 17. Beyond raw numbers, it is important to remember that this is a civil rights issue and accessibility both in the physical world and on the Web is, in a word: abysmal. There is no epidemic of people with disabilities going from website to website suing people. The epidemic is that we’re 19 years after the formation of the Web Accessibility Initiative and yet developers at the largest websites in the world can’t figure out the alt attribute or how to put meaningful text in buttons. However, if you do get sued, nobody will have pity on you for doing subpar work.
- 18. Design accessible websites ▪ Inclusive design is better design for everyone. ▪ Researching with people with disabilities quickly highlights usability issues. ▪ No user should be excluded because of disability. ▪ Everyone has abilities , and limits to those abilities. ▪ We are all only temporarily not disabled. ▪ Accessible servers are cheaper.
- 22. The Web Content Accessibility Guidelines are a set of technical standards. – The WCAG has 4 Principles (P-O-U-R) that are broken down into 12 Guidelines – Those 12 Guidelines are further broken down into Success Criteria – For each Success Criteria there are 3 levels of Conformance A, AA, AAA
- 23. Each of the guidelines in WCAG have measurable success criteria divided into the levels of A (lowest), AA and AAA (highest). More A’s equals more demands, but better accessibility when met.
- 24. POUR – Four Principles of Accessibility – Content must be Perceivable – Interface components in the content must be Operable – Content and controls must be Understandable – Content should be Robust enough to work with current and future assistive technologies (AT)
- 25. • Level A We must satisfy these requirements, otherwise it will be impossible for one or more groups to access the web content • Level AA We should satisfy these requirements, otherwise some groups will find it difficult to access the web content • Level AAA We may satisfy these requirements, in order to make it easier for some groups to access the web content
- 26. • 1. Perceivable – 1.1 Provide text alternatives for non-text content like images – 1.2 Offer captions or text summaries for audio and video – 1.3 Structure content to be programmatically identified and write it to be presented in different ways – 1.4 Design content to be easy to read and listened to (good contrast, volume control) • 2. Operable – 2.1 All functionality should be available just using a keyboard – 2.2 There should be enough time to read content and perform wanted tasks – 2.3 Avoid designing content that might cause seizures – 2.4 Help users navigate and find content as much as possible • 3. Understandable – 3.1Write easy-to-read text with assistive technologies in mind – 3.2 Design content and the interface to behave in predictable ways – 3.3 Help users to avoid and correct mistakes when entering input • 4. Robust – 4.1 Provide maximum compatibility with as many web browsers as possible
- 29. What’s New in WCAG 2.1 In the Summer of 2018, WCAG 2.1 is set to be released with seventeen new guidelines that focus on improving accessibility for users with cognitive disabilities and for users who browse websites on mobile devices like tablets and smartphones.
- 30. New guidelines in WCAG 2.1 Before explaining the new guidelines in WCAG 2.1, you should know that WCAG 2.1 is backward compatible with WCAG 2.0. This means that: – The previous categories and guidelines still apply – The numbering still applies – The basic principles still apply – The three levels of success criteria (A, AA, AAA) still apply
- 31. 1.3.4 Identify Common Purpose (AA) For the following this guideline, the meaning of each input field must be able to be determined programmatically. In other words, a piece of code must be able to tell what is expected to be entered by a user or what’s the meaning of a piece of entered information. Doing this correctly will make it possible for a user’s browser to autofill input fields based on data previously entered by the user. Great! Having to enter less input is always nice. Technically, this has to be true if: • The implementation is done using technologies for identifying expected meaning of input data. • The input field uses the Autofill markup like in the following code snippet <form> <label for="input-email">Email adress</label> <input id="input-email" autocomplete="email" type="email"> <label for="input-password">Password</label> <input id="input-password" autocomplete="current-password" type="password"> <button name="button-sign-in">Sign in</button> </form>
- 32. 1.3.5 Identify Purpose (AAA) This guideline says that the purpose of interface components, icons and certain sections must be able to be identified programmatically. For example: The user should not just understand that a button is a button. He or she should understand what the button does, what its purpose is. HTML should always be written correctly, so that assistive technologies like screen readers can do things like: •Identify sections like header, navigation, main content area and so on for easier navigation. •Provide text alternatives to icons, which otherwise can sound weird when being read to users. •Differentiate between different subheadings like H2, H3 and H3 subheadings for finding wanted content faster. Following this guideline will improve accessibility for users of assistive technologies like screen readers.
- 33. 1.4.10 Reflow (AA) This guideline states that users must be able to browse a website using a 320 pixel wide screen without having to scroll horizontally. In other words, your website must be responsive. Why a width of 320 pixels? Probably because this is the smallest device width of a lot of popular smartphones. Following this guideline will improve accessibility for all users visiting your website on a smartphone. It will also benefit users with visual impairment who definitely will zoom in (up to 400 % ) on desktop browsers. Note: It’s acceptable to allow horizontal scrolling for content that often requires it like maps, data tables with many columns and wide diagrams.
- 34. 1.4.11 Non-text contrast (AA) Having high contrast between pieces of text and their backgrounds is one of the best and most important things you can do to ensure great accessibility on your website. In this guideline the requirement for high contrast extends from regular page text, to text on interface components (buttons) as well as for colors used in non-text content (infographics and diagrams). Tip: For measuring contrast, I recommend Lea Verou’s excellent tool at: leaverou.github.io/contrast-ratio Following this guideline will improve accessibility for all users with different kinds of visual impairment.
- 35. How to contact Roy Email: rrumaner@gmail.com Twitter (and most everywhere else): rrumaner LinkedIn: RoyRumaner AccessibilityWebsiteBlog.com
- 36. How to contact Devin Email: devin@redpillnow.com Twitter (and most everywhere else): spanky762 LinkedIn: Devin Olson Facebook: default.xsp