2/23/ Enterprise Web Accessibility Standards Version 2.0 WebMASSters Presentation 2/23/2005

2 2/23/2005 Introduction A workgroup of 15 agency webmasters reviewed and revised the Enterprise Web Accessibility Standards published in These slides highlight:  The changes to the Standards  Implementation challenges  Details regarding the standards  Resources for more information

3 2/23/2005 Topics of Discussion Changes in Version 2.0 Implementation challenges Discussion regarding the standards For more information…

4 2/23/2005 What has changed? Introduction and Scope Added the benchmark of applicable Federal Section 508 standards 1.1 MarkupAdded HTML markup requirements related to accessibility 1.5 FormsAdded a new standard requiring accessible forms 1.6 Timed responses Added a new standard requiring that users be given the option to request additional time

5 2/23/2005 What has changed? (cont.) 2.1 Navigation Added the requirement of a visible or hidden skip navigation link 3.6 Image Maps Added a new standard requiring the use of accessible client-side image maps, when possible. 4.1 Content Formats Provided recommendations for use of HTML, PDFs, and other formats 5.1 File Optimization Provided guidance on optimizing file size

6 2/23/2005 What has changed? (cont.) 6 Web Accessibility Statement Required a link to a web accessibility statement and provided sample text for the statement 7 Web Site Validation Added accessibility requirements for web site validation 8 Web Applications Added a new section adopting Section 508 requirements for web- based applications

7 2/23/2005 What are the implementation challenges? Executive management support Allocation of skilled resources Tools and software acquisition Training and support Time

8 2/23/2005 How do we foster compliance? Educate executive management about the legal requirements of web accessibility. Ensure the provision of adequate resources at the agency level to achieve compliance Provide support for agency webmasters, web developers, and content providers Share resources via the Mass.Gov portal services pages Provide informal training and sharing via WebMASSters meetings and other forums

9 2/23/2005 Layout and Design A state agency web page must use HTML markup tags according to industry standards A state agency web page should control presentation with style sheets, but the web pages must be organized so they are readable without requiring an associated style sheet.

10 2/23/2005 Layout and Design (cont.) A state agency web page should avoid using frames State agencies must ensure that their web pages are usable when scripts, applets, or other programmed objects are turned off or are not supported.

11 2/23/2005 Layout and Design (cont.) Forms designed to be completed online, and other interactive interface elements, must be accessible by people using assistive technology When a timed response is required, the user must be provided the opportunity to request additional time to continue working before the time-out occurs.

12 2/23/2005 Navigation A state agency web page must use clear and consistent navigation mechanisms A state agency must ensure that users are able to interact with web page elements in a device independent manner.

13 2/23/2005 Graphics and Sound A state agency web page must provide a text equivalent for every non-text element A state agency web page must provide synchronized auditory and readable text descriptions of the important information of the visual track of a multimedia presentation.

14 2/23/2005 Graphics and Sound (cont.) A state agency web page must provide a text equivalent for information provided in audio format A state agency web page that uses motion must ensure that the motion is integral to the content of the site, user- controlled, and limited to three cycles and then stopped automatically.

15 2/23/2005 Graphics and Sound (cont.) A state agency must ensure that the use and selection of color do not affect the information conveyed on a page Client-side image maps are recommended. If server-side image maps must be used, provide redundant text links for each active region.

16 2/23/2005 Content Requiring Additional Software All information published on a state agency web page must be published in HTML, whenever possible, to eliminate the need for additional software A state agency that offers files to download in compressed format (Zip files, for example) must also provide the same information in its uncompressed format or as a self extracting file.

17 2/23/2005 File Size A state agency must optimize files to improve download time.

18 2/23/2005 Web Accessibility Statement A state agency web site must provide a link to a web accessibility statement.

19 2/23/2005 Web Site Validation A state agency must validate web content against these Standards prior to posting and at regular intervals after posting.

20 2/23/2005 Web-Based Applications Section of Federal Section 508

21 2/23/2005 For More Information… Refer to the Enterprise Web Accessibility Standards ( Policies and Standards link) Visit the Mass.Gov Portal Services Web Site ( Use your favorite web search engine