{"id":2171,"date":"2018-11-19T15:12:29","date_gmt":"2018-11-19T21:12:29","guid":{"rendered":"http:\/\/blogs.luc.edu\/compliance\/?p=2171"},"modified":"2018-11-19T15:12:29","modified_gmt":"2018-11-19T21:12:29","slug":"accessible-ui-ux-design-making-websites-ada-compliant","status":"publish","type":"post","link":"https:\/\/blogs.luc.edu\/compliance\/?p=2171","title":{"rendered":"Accessible UI\/UX Design: Making Websites ADA Compliant"},"content":{"rendered":"

Sei Unno<\/em><\/p>\n

Associate Editor<\/em><\/p>\n

Loyola University Chicago School of Law, JD 2019<\/em><\/p>\n

The World Wide Web Consortium<\/a>\u00a0(\u201cW3C”) is a collaborative community that develops standards for the Internet. One of W3C’s goals<\/a>\u00a0is to make the web accessible to everyone, regardless of an individual\u2019s accessibility needs. Section 508 of the Rehabilitation Act<\/a>\u00a0requires that the electronic and information technology of federal agencies are accessible to people with disabilities, whether they are employees or members of the public. W3C publishes the Web Content Accessibility Guide<\/a>\u00a0(WCAG), which addresses how to create accessible websites. The WCAG was used by the U.S. Access Board<\/a>\u00a0to create standards for Section 508. Recent cases like Gorecki v. Hobby Lobby Stores, Inc.<\/em><\/a>\u00a0<\/em>and Gil v. Winn-Dixie Stores, Inc.<\/em><\/a>\u00a0<\/em>reveal the need to not only comply with these laws and regulations, but to adopt a culture that goes above and beyond the minimum.<\/p>\n

<\/p>\n

What makes a website accessible?<\/strong><\/p>\n

Section 508 was published in the Federal Register on December 21, 2000<\/a>. However, the U.S. Access Board recently promulgated a final rule that will update Section 508<\/a>\u00a0in January 2018. The U.S. Access Board<\/a>\u00a0is a federal agency that promotes equality and accessibility for people with accessibility needs. The U.S. Access Board\u2019s final rule adopted the WCAG 2.0<\/a>\u00a0recommendations. The revisions made to the information and communication technologies performance requirements<\/a>\u00a0include changing speech-based modes for input, control, or operation that can also be used without speech and manual operations, which should be accessible for those who need mobility accommodations.<\/p>\n

Since the passage of the new final rule, W3C has created new guidelines. WCAG 2.1<\/a>\u00a0was published in June 2018. Some of the new requirements within WCAG 2.1 includes giving users enough time<\/a>\u00a0to read and interact with content and making it easier for users to use inputs other than a keyboard<\/a>. Alternative inputs<\/a>\u00a0methods include mouth sticks, eye movement tracking, and pointers.<\/p>\n

Web Design in the Courts<\/strong><\/p>\n

In Gil v. Winn-Dixie Stores, Inc.<\/em><\/a>, the plaintiff, Juan Carlos Gil, alleged that Winn-Dixie\u2019s website was not accessible to the visually impaired. Winn-Dixie\u2019s grocery stores and pharmacies were categorized as public accommodations under the ADA<\/u><\/a>, but at the time of the case, they did not have an ADA policy for its website. An issue in this case was whether the website itself is a public accommodation. Mr. Gil claimed that he could not see computer screens so he would use screen reader software. Without access to the website, Mr. Gil was unable to get coupons easily without having to depend on others, like friends or Winn-Dixie employees. The court found that the cost to make the Winn-Dixie website accessible for Mr. Gil and others who use screen reader software would amount to $250,000, and reasoned that the ADA not only dictates physical access to public accommodations, but also websites.<\/p>\n

Similarly, in\u00a0Gorecki v. Hobby Lobby Stores, Inc.<\/em><\/a>, the plaintiff, Sean Gorecki, could not access Hobby Lobby\u2019s website using his screen reading software. The court cites that the Department of Justice has affirmed that Title III of the ADA applies to websites that meet the definition of public accommodation.<\/p>\n

Both Mr. Gil and Mr. Gorecki used the screen reader JAWS (Job Access with Speech)<\/a>. JAWS is able to read the screen or display the text through a braille display<\/a>. Developing websites that are compatible with JAWS and other similar devices and software is difficult. JAWS identifies content on the web page and announces what the particular object is (like a checkbox) and what it says<\/a>. However, it uses the context on the webpage to figure out exactly what to relay to the user. For example, for text boxes, JAWS communicates to the user what the nearest text that comes before the text box; for checkboxes, JAWS communicates what comes after the box. Therefore, what may look visually appealing is not enough for developers of this type of software. Extra lines of code such as labels are necessary to allow JAWS to understand what text goes with what element or feature.<\/p>\n

In both Gil\u00a0<\/em>and Gorecki<\/em>, the need for websites to be maintained not only to the new final rule but also updates like WCAG 2.1 demonstrate that web designers and businesses must be informed and proactive. Waiting to update a website until it is absolutely necessary can be costly, not just in consulting fees but in legal fees if the company gets caught not being in compliance with these new regulations.<\/p>\n

Takeaways<\/strong><\/p>\n

Although U.S. governmental regulations may not keep pace with developments in web design, user interface design, and user experience design should always have every user in mind and keep pace with W3C guidelines. Although some situations may be dismissed as edge cases, developing web experiences that are accessible<\/a>\u00a0to all is not only legally savvy but important for all consumers.<\/p>\n","protected":false},"excerpt":{"rendered":"

The World Wide Web Consortium\u00a0(\u201cW3C”) is a collaborative community that develops standards for the Internet. One of W3C’s goals\u00a0is to make the web accessible to everyone, regardless of an individual\u2019s accessibility needs. Section 508 of the Rehabilitation Act\u00a0requires that the electronic and information technology of federal agencies are accessible to people with disabilities, whether they are employees or members of the public. W3C publishes the Web Content Accessibility Guide\u00a0(WCAG), which addresses how to create accessible websites. The WCAG was used by the U.S. Access Board\u00a0to create standards for Section 508. Recent cases like Gorecki v. Hobby Lobby Stores, Inc.\u00a0and Gil v. Winn-Dixie Stores, Inc.\u00a0reveal the need to not only comply with these laws and regulations, but to adopt a culture that goes above and beyond the minimum.<\/p>\n","protected":false},"author":23,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[124,951,952,964,965,1121,1189,1205,2037,2069,2070,2079,2109,2124,2125],"class_list":["post-2171","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-ada","tag-gil","tag-gil-v-winn-dixie-stores","tag-gorecki","tag-gorecki-v-hobby-lobby-stores","tag-inc","tag-jaws","tag-journal-of-regulatory-compliance","tag-ui","tag-user-experience","tag-user-interface","tag-ux","tag-w3c","tag-wcag","tag-web-design"],"_links":{"self":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts\/2171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/users\/23"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2171"}],"version-history":[{"count":0,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts\/2171\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}