ADA compliancy and your website. Ensuring that people with disabilities have full access to your website opens the door to a wider audience

Similar documents
Fusion 4 General Help VPAT

DESIGNING WITH ACCESSIBILITY IN MIND ACCESSIBILITY TRAINING

Axway Voluntary Product Accessibility Template (VPAT)

Accessibility for Sugar 6.7

Networx Enterprise Proposal for Internet Protocol (IP)-Based Services. Supporting Features. Criteria. Remarks and explanations

Section Web-based Internet information and applications - Incident Response Service (INRS) - Detail Voluntary Product Accessibility Template

Titan HST - Android Administrator Interface Voluntary Product Accessibility Statement February 2018

Science. Voluntary Product Accessibility Template: Section 508

Date: April 3, 2017 Name of Product: Cisco Prime Infrastructure v3.1 Contact for more information:

Date: March 15, 2017 Name of Product: Cisco Umbrella version Dashboard 2 Contact for more information:

Adobe Experience Manager (AEM) 6.2 Forms - Output Voluntary Product Accessibility Template

Date: September 5, 2017 Name of Product: Cisco WebEx Product (web) Pages WBS32.3 Contact for more information:

All contents are Copyright Cisco Systems, Inc. All rights reserved.

Networx Universal. Supporting Features. Criteria. Remarks and explanations

Lectora 508 Compliance Document

Voluntary Product Accessibility Template

ACCESSIBILITY POLICY Effective Date: March 20, 2017

Section Software Applications and Operating Systems - Detail Voluntary Product Accessibility PageCenterX

Adobe LiveCycle Rights Management ES3 Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

Date: December 21, 2017 Name of Product: Cisco WebEx Web App Meeting Center v3.4 Contact for more information:

Adobe LiveCycle PDF Generator ES4 Voluntary Product Accessibility Template

Adobe Experience Manager (AEM) 6.2 Forms - Reader Extensions Voluntary Product Accessibility

Adobe LiveCycle Reader Extensions ES3 Voluntary Product Accessibility Template

Adobe Sign Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

VMware vrealize Operations Manager 6.0 VPAT

Adobe LiveCycle Digital Signatures ES3 Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

VPAT. Voluntary Product Accessibility Template. Version 1.3

VMware ESXi Host Client 6.5 VPAT

VMware vsphere Client 6.5 VPAT

Adobe Experience Manager (AEM) 6.2 Forms - Digital Signatures Voluntary Product Accessibility Template

VPAT for View 5.1 Client Documentation and Online Help

SmartBuilder Section 508 Accessibility Guidelines

Section 508 Evaluation Template

Adobe Acrobat.com Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Voluntary Product Accessibility Template

VPAT. Event Log Management v10 Accessibility. Version 1.3 of the VPAT Template

Adobe LiveCycle Correspondence Management ES4 Voluntary Product Accessibility Template

Adobe Digital Publishing Solution for Windows Voluntary Product Accessibility Template

Adobe Business Catalyst Voluntary Product Accessibility Template

Adobe LiveCycle Mobile Forms ES4 Voluntary Product Accessibility Template

Section Software Applications and Operating Systems Web Conferencing Service (WCS) Detail Voluntary Product Accessibility Template

IP Office Contact Center 10.X Wallboard Voluntary Product Accessibility Template (VPAT)

Rapid7 Nexpose: Voluntary Product Accessibility Template

Schedule Planner Section 508 Voluntary Product Accessibility Template

VMware Horizon View Connection Server 6.0 Documentation and Online Help VPAT

Adobe Story CC Plus Voluntary Product Accessibility Template

Adobe Contribute 6.5 Voluntary Product Accessibility Template

Blackboard Voluntary Product Accessibility Template September 2015

Adobe LiveCycle Server Administration ES3 Voluntary Product Accessibility Template

Adobe Experience Manager (AEM) 6.2 Forms Workbench Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

Note: This document describes normal operational functionality. It does not include maintenance and troubleshooting procedures.

Note: This document describes normal operational functionality. It does not include maintenance and troubleshooting procedures.

Adobe Omniture Discover Voluntary Product Accessibility Template

VMware vrealize Operations Manager 6.1 VPAT

VPAT. Voluntary Product Accessibility Template

Summary Table Section 508 Voluntary Product Accessibility Template. Criteria Supporting Features Remarks and explanations Section 1194.

Adobe Experience Manager (AEM) 5.6 for Forms Portal Voluntary Product Accessibility Template

Adobe EchoSign Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Adobe Dreamweaver CC Voluntary Product Accessibility Template

Adobe Experience Manager (AEM) 6.2 Forms - Server Administration Voluntary Product Accessibility Template

Adobe FormsCentral (Desktop Application) Voluntary Product Accessibility Template

It should be noted that this document describes administrative access to Content Sharing Suite via the Web Admin UI.

Summary Table Voluntary Product Accessibility Template

VMware vcenter Site Recovery Manager 6.1 VPAT

Criteria Supporting Features Remarks and explanations Section Software Applications and Operating Systems. possible exceptions

VPAT. Voluntary Product Accessibility Template. Version 1.3

Summary Table for SolarWinds MFT Server

VPAT. Voluntary Product Accessibility Template. Version 1.3. Summary Table VPAT. Voluntary Product Accessibility Template. Supporting Features

Summary Table Voluntary Product Accessibility Template

VMware vfabric Hyperic 5.0 VPAT

VMware vsphere Web Client 6.5 VPAT

VMware vsphere Update Manager 6.0 VPAT

Voluntary Product Accessibility Template Retina Network Security Scanner

Adobe Illustrator CS5.1 Voluntary Product Accessibility Template

Voluntary Product Accessibility Template PowerBroker Identity Services

VPAT Voluntary Product Accessibility Template. Summary Table

Voluntary Product Accessibility Report

Adobe Experience Manager 6.0 Voluntary Product Accessibility Template

VPAT for View 5.1 Server

Accessibility Analysis

Adobe Illustrator CC Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Voluntary Product Accessibility Template

Voluntary Product Accessibility. Retina CS Enterprise Vulnerability Management

Voluntary Product Accessibility Template

Section 508 Compliance: Ensuring Accessibility to Web-Based Information

Voluntary Product Accessibility Template

Adobe Bridge CS5.1 Voluntary Product Accessibility Template

Wimba Voice VPAT. Date: March 25, 2008 Name of Product: Wimba Voice Tools version Contact for more Information:

Google Forms. Summary Table. Date: 11/2014 Name of Product: Google Forms Point of Contact: Richard Wu. Criteria Supporting features Remarks

Student Schedule Planner Section 508 Voluntary Product Accessibility Template

VMware vcenter Orchestrator 5.5 VPAT

Exhibit A. Voluntary Product Assessment Template SUMMARY TABLE. Section Software Applications and Operating Systems Applicable Partial Support

VPAT. Voluntary Product Accessibility Template

Transcription:

ADA compliancy and your website Ensuring that people with disabilities have full access to your website opens the door to a wider audience

We rebrand. DAAKE is one of the nation s few rebranding specialty firms. daake.com

Federal Regulations Two words that make everyone in your organization cringe, from the CEO on down to the latest hire: federal regulations. These are the regulations that can permeate every level and range from complicated to downright confounding. But many are designed to be helpful, to make things better, and though the actual regulations may require a translator to fully comprehend, in the end, someone or something benefits. That is the goal behind the regulations currently being developed by the federal government regarding the Americans with Disabilities Act (ADA) and the effort to create a world of websites that are ADA compliant, meaning that everyone including people with disabilities has equal accessibility to online resources. It is projected that the U.S. Department of Justice will complete these regulations by 2018. Subsequent enforcement, it has been said, will be on a case by case basis. Will these regulations be issued in time to meet the government s self-imposed deadline? We don t know. Should you just wait and see? NO. Why not? Because compliancy in many cases will not be extraordinarily difficult. New websites can be designed with ADA compliancy in mind, while current websites can be adjusted and renovated. Granted, there is no single button that a web designer can push to suddenly transform a website into one that is fully compliant. But there are different levels of compliancy. Deciding which level is right for your website and your brand as well as how to reach it, will require time. Patience. Guidance. And experience. The more a design team works with ADA requirements, the more the regulations become second nature. We have been examining these requirements and monitoring their development. And while every detail isn t yet set in code, we have compiled a few things you can start thinking about regarding your website and its future ADA compliancy: 3

ADA COMPLIANCY AND YOUR WEBSITE BACKGROUND The ADA was passed into law in 1990. Title III of the act requires businesses and nonprofit services providers to make it possible for the disabled public to access the same services as people who are not disabled. In 2010, the U.S. Department of Justice issued the ADA Standards for Accessible Design. Originally applied chiefly to physical spaces, application of the accessible design requirements are evolving to electronic spaces, including websites when engaged by people with physical, sensory or cognitive disabilities. The United States Access Board, originally the Architectural and Transportation Barriers Compliance Board, is an independent federal agency created to promote equality for people with disabilities through leadership in accessible design and the development of accessibility guidelines and standards. The board has proposed updating existing Electronic and Information Technology Accessibility Standards under Section 508 of the Rehabilitation Act ( 508 Standards ). Since the existing 508 Standards were issued in 2000, mobile phones moved from devices with voice-only capability to so-called smartphones offering voice, text and video communications. Desktop computers are no longer the only information processing hardware: mobile devices and tablets, which have very different input and output characteristics, can typically process vast amounts of electronic information, the board writes (www.access-board.gov/guidelines-and-standards/communications-and-it/ about-the-ict-refresh/proposed-rule/ii-executive-summary). 4

daake.com In recognition of these converging technologies, one of the primary purposes of the proposed rule is to replace the current product-based approach with requirements based on functionality, and, thereby, ensure that accessibility for people with disabilities keeps pace with advances in electronic and information technology. Federal agencies, as well as entities that work directly with, or those that accept money from, the federal government are governed under Section 508 and those directives can have a significant effect on website design. Why is accessibility important? According to the U.S. Department of Health & Human Services (HHS), worldwide there are 285 million people with some sort of visual impairment, 275 million people with moderate-to-profound hearing impairment, and many more with physical, speech, cognitive and neurological disabilities. Much the same as a ramp allows a person in a wheelchair access to a building, assistive technologies enable many people with disabilities to use a computer. These technologies include screen readers, text-to-speech and speech-to-text converters, text enlargement software and computer programs that allow disabled persons to control the computer with their voices. Other assistive technology is built into computer operating systems. Some people with low vision are able to see computer displays by adjusting color schemes, contrast settings and font sizes. Others with limited manual dexterity use key strokes instead of a standard mouse. MAKING THE ONLINE WORLD MORE ACCESSIBLE TO THEM IS ADMIRABLE. IT ALSO MEANS SEEING AND HEARING, SENSING AND CONVEYING THINGS DIFFERENTLY THAN A LOT OF WEBSITES DO TODAY. 5

ADA COMPLIANCY AND YOUR WEBSITE COMPLIANCY DEFINED What is accessible when it comes to websites? Here is the government checklist, courtesy of the HHS (1194.22 Web-Based Intranet and Internet Information and Applications): A text equivalent for every non-text element shall be provided (e.g., via alt, longdesc, or in element content). Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Documents shall be organized so they are readable without requiring an associated style sheet. Redundant text links shall be provided for each active region of a server-side image map. Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Row and column headers shall be identified for data tables. Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Frames shall be titled with text that facilitates frame identification and navigation. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with (regulation) 1194.21(a) through (l). When electronic forms are designed to be completed online, the form shall allow people using assistive technology to access the information, field elements and functionality required for completion and submission of the form, including all directions and cues. A method shall be provided that permits users to skip repetitive navigation links. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. 55 Hz. 6

daake.com Got all that? Not likely. Put simply, it really is difficult to put simply. It basically means every page and every line of text, every color, graphic, video, chart and other element has to be examined from another perspective that of someone with a disability. It may be easier to understand with a couple examples: Here is how the site appears online. A look behind the scenes using the web accessibility evaluation tool (WAVE). 7

ADA COMPLIANCY AND YOUR WEBSITE EQUIVALENT ALTERNATIVES FOR ANY MULTIMEDIA PRESENTATION SHALL BE SYNCHRONIZED WITH THE PRESENTATION. Questions to be asked to check compliancy: Does the multimedia presentation have captions? Are the captions large enough to be read? Are the captions presented on a solid background with high contrast so that they can be distinguished from the pictorial content? Are the captions synchronized with the audio in the presentation? Does the multimedia presentation have video description? WEB PAGES SHALL BE DESIGNED SO THAT ALL INFORMATION CONVEYED WITH COLOR IS ALSO AVAILABLE WITHOUT COLOR, FOR EXAMPLE FROM CONTEXT OR MARKUP. Questions to check compliancy: If color is used to convey information, is the information presented by another method? Are meaningful text equivalents readily apparent for any color-coded screen element? 8

daake.com In addition, the Access Board s proposed revision would incorporate by reference the Web Content Accessibility Guidelines (WCAG) 2.0, a voluntary consensus standard developed by information and communication technology (ICT) industry representatives and other experts. It would also make WCAG 2.0 Success Criteria applicable not only to content on the World Wide Web but also to non-web electronic documents and software such as word processing documents, portable document format files and project management software. There are three levels of conformance with WCAG 2.0: A, which is the lowest; AA, and AAA, the highest. Determining which level you aim to meet depends on your users needs and website objectives. Level A conformity offers very little to impaired users. It largely makes it easier for browser readers to navigate and translate the website. This is like providing a step stool when the U.S. Department of Justice might prefer LEVEL AAA a ladder. Level AA makes sites accessible to people with a wider range of disabilities but won t change the appearance of your website as much as Level AAA. It s likely that the majority of websites will aim for Level AA. While WCAG 2.0 Level AA closely mirrors the standards in LEVEL AA Section 508, WCAG documentation is more detailed. Level AAA is the most demanding level of accessibility compliance and will significantly alter the design of the site. Even the WCAG discourages aiming for Level LEVEL A AAA conformance for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content. There are variances in each level s specific requirements. For example, WCAG 2.0 requires that foreground and background colors have a 4.5:1 contrast ratio at Level AA, but a 7:1 contrast ratio at Level AAA. 9

ADA COMPLIANCY AND YOUR WEBSITE WHAT S RIGHT FOR OUR SITE? That is a gray area with considerable contrast. To be a little clearer, becoming ADA compliant will mean the same thing for every website. A site for a regional medical center must think of users beyond that of a commercial or retail site. But while their users intentions and goals may be different, the users limitations as defined by their disabilities remain the same. In the end, it s not about meeting the easiest level or the most difficult. It s about good business. YOUR WEBSITE IS YOUR FRONT DOOR TO THE WORLD, AND IF THAT FRONT DOOR ISN T WIDE OPEN TO EVERYONE WHO WANTS TO GET IN, WHY HAVE ONE AT ALL? 10

Considering a rebrand? CALL US: 402.933.2959 daake.com

More titles from DAAKE: daake.com/ebooks Connect with DAAKE enewsletter: Stay in touch with our latest work, our thinking and rebranding news and trends. daake.com/blog We rebrand. DAAKE is one of the nation s few rebranding specialty firms. 2017 Daake Design, Inc. All rights reserved. daake.com