Transcript Web Accessibility Standards

Enterprise Web
Accessibility
Standards
Version 2.0
WebMASSters Presentation
2/23/2005
2/23/2005
1
Introduction
A workgroup of 15 agency webmasters
reviewed and revised the Enterprise Web
Accessibility Standards published in 2000.
 These slides highlight:

 The
changes to the Standards
 Implementation challenges
 Details regarding the standards
 Resources for more information
2/23/2005
2
Topics of Discussion
Changes in Version 2.0
 Implementation challenges
 Discussion regarding the standards
 For more information…

2/23/2005
3
What has changed?
Introduction Added the benchmark of applicable
and Scope Federal Section 508 standards
1.1 Markup Added HTML markup requirements
related to accessibility
1.5 Forms
Added a new standard requiring
accessible forms
1.6 Timed
Added a new standard requiring that
responses
users be given the option to request
additional time
2/23/2005
4
What has changed? (cont.)
2.1
Navigation
3.6 Image
Maps
Added the requirement of a visible or
hidden skip navigation link
Added a new standard requiring the
use of accessible client-side image
maps, when possible.
4.1 Content Provided recommendations for use
Formats
of HTML, PDFs, and other formats
5.1 File
Provided guidance on optimizing file
Optimization size
2/23/2005
5
What has changed? (cont.)
6 Web
Accessibility
Statement
7 Web Site
Validation
8 Web
Applications
2/23/2005
Required a link to a web accessibility
statement and provided sample text
for the statement
Added accessibility requirements for
web site validation
Added a new section adopting
Section 508 requirements for webbased applications
6
What are the
implementation challenges?
Executive management support
 Allocation of skilled resources
 Tools and software acquisition
 Training and support
 Time

2/23/2005
7
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
2/23/2005
8
Layout and Design
1.1 - A state agency web page must use
HTML markup tags according to industry
standards.
 1.2 - 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.

2/23/2005
9
Layout and Design (cont.)
1.3 - A state agency web page should
avoid using frames.
 1.4 - State agencies must ensure that their
web pages are usable when scripts,
applets, or other programmed objects are
turned off or are not supported.

2/23/2005
10
Layout and Design (cont.)
1.5 - Forms designed to be completed
online, and other interactive interface
elements, must be accessible by people
using assistive technology.
 1.6 - 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.

2/23/2005
11
Navigation
2.1 - A state agency web page must use
clear and consistent navigation
mechanisms.
 2.2 - A state agency must ensure that
users are able to interact with web page
elements in a device independent manner.

2/23/2005
12
Graphics and Sound
3.1 - A state agency web page must
provide a text equivalent for every non-text
element.
 3.2 - 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.

2/23/2005
13
Graphics and Sound (cont.)
3.3 - A state agency web page must
provide a text equivalent for information
provided in audio format.
 3.4 - A state agency web page that uses
motion must ensure that the motion is
integral to the content of the site, usercontrolled, and limited to three cycles and
then stopped automatically.

2/23/2005
14
Graphics and Sound (cont.)
3.5 - A state agency must ensure that the
use and selection of color do not affect the
information conveyed on a page.
 3.6 - Client-side image maps are
recommended. If server-side image maps
must be used, provide redundant text links
for each active region.

2/23/2005
15
Content Requiring
Additional Software


4.1 - All information published on a state agency
web page must be published in HTML,
whenever possible, to eliminate the need for
additional software.
4.2 - 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.
2/23/2005
16
File Size

5.1 - A state agency must optimize files to
improve download time.
2/23/2005
17
Web Accessibility
Statement

6.1 - A state agency web site must provide
a link to a web accessibility statement.
2/23/2005
18
Web Site Validation

7.1 - A state agency must validate web
content against these Standards prior to
posting and at regular intervals after
posting.
2/23/2005
19
Web-Based Applications

Section 1194.21 of Federal Section 508
2/23/2005
20
For More Information…
Refer to the Enterprise Web Accessibility
Standards (http://www.mass.gov/itd,
Policies and Standards link)
 Visit the Mass.Gov Portal Services Web
Site (http://www.mass.gov/portalservices)
 Use your favorite web search engine

2/23/2005
21