Voluntary Product Accessibility Template® Section 508 Standards Compliancy (1194)

Voluntary Product Accessibility Template®
Section 508 Standards Compliancy (1194)
COMPANY NAME Section 508 Standards Compliancy PRODUCT

Contents
1. Overview...........................................................................................5
The 508/255 Refresh..............................................................................5
2. Information on this VPAT...................................................................6
3. VPAT Sections Summary..................................................................7
4. Compliancy.......................................................................................8
A. Section 1194.31 Functional Performance Criteria..........................35
B. Section 1194.41 Product Information, Documentation and Support
37
C. Supporting Information for this VPAT..............................................38

List of Tables
Table 1: Acronyms 4
Table 2: Summary Table: Voluntary Product Accessibility Template 7
Table 3: Compliancy by Criteria - Mapping Section 508 to WCAG 1.0 & WCAG 2.0 with
specific remarks on the COMPANY NAMEcompliancy 9
Table 4: Functional Performance Criteria 35
Table 5: Product Help and Support 37
COMPANY NAME 508 VPAT PRODUCT December 9, 2021

3
Acronyms
Table 1: Acronyms
Acronym Definition
VPAT Voluntary Product Accessibility Template (this document)

details how the COMPANY NAME web application meets the
accessibility requirements of the ADA by mapping to the
WCAG 2.0, 508 Refresh standard
ADA Americans with Disabilities Act
WCAG (1.0 & 2.0) Web Content Accessibility Guidelines
http://www.w3.org/TR/WCAG10/ (1.0)
http://www.w3.org/TR/WCAG20/ (2.0)
WAI Web Accessibility Initiative body that created the WCAG and
is under the umbrella of the W3C
http://www.w3.org/WAI/
W3C World Wide Web Consortium is an international community
working together to develop web standards and maintain their
specifications. WAI is the W3C’s accessibility initiative
http://www.w3.org
FAR Federal Acquisition Regulations systems who publishes all
policies and procedures for all executive agencies.
https://www.acquisition.gov/Far/
508/255 Refresh Reflects WCAG 2.0 and is passed draft stage. It is the
product of the working group that the Access Board
requested in 2006 to update the accessibility standards for
Rehabilitation Act (Section 508 1973) and the
Telecommunications Act (Section 255 1996)
http://508-255-refresh.trace.wisc.edu/
508 Section 508 of the American Disabilities Act (reflects WCAG
1.0 level 1)
http://www.section508.gov/
255 Section 255 of the Telecommunications Act
JAWS 11 JAWS® for Windows Screen Reading Software (Assistive
Technology)
http://www.freedomscientific.com/products/fs/jaws-product-
page.asp
NVDA 2010.1 NonVisual Desktop Access is a free and open source screen
reader for the Microsoft Windows operating system (Assistive
Technology)
http://www.nvda-project.org/

4
Overview
1. Overview
The purpose of this Voluntary Product Accessibility Template (VPAT) is to assist Federal
contracting officials, users of assistive technologies, and others in making preliminary
assessments regarding the availability of Information Technology products and services
with features that support accessibility, and highlight our compliancy.
This VPAT applies the following sections of the Section 508 Standards for Electronic and
Information Technology of the Americans with Disabilities Act (ADA) to the COMPANY
NAME web sites/web applications and its VeriSign Identity Protection.
 Section 1194.22, for Web-based Intranet and Internet Information and Applications.
 Sections 1194.31 and 1194.41 (Functional Performance and
Information/Documentation)
Additionally, this VPAT details the success criteria used to show compliance to these
sections.
The 508/255 Refresh

In 2006, the Access Board started an update of the accessibility laws due to technology
changes, differences in interpretation, and international harmonization. Since the Web
Content Accessibility Guidelines (WCAG) had been updated to 2.0 officially in December
of 2008, the 2.0 version of the WCAG was used heavily in this update effort. This effort to
reconcile WCAG 1.0 level one (the basis for the existing Section 508) to WCAG 2.0 is
called the 508/255 Refresh.
In July of 2009, the Ad Hoc Committee presented its final draft for Access Board
approval, and the final rule of 508 was published with Federal Acquisition Regulations
(FAR) and moved into the public involvement stage. Since then, it has gone through sub-
committee, public information meetings, and open question/feedback periods. Though
currently a recommendation, the updated draft of Section 508/255 is expected to be
finalized in 2010, close to if not exactly as it stands currently.

2. Information on this VPAT
This VPAT describes the following web site/application:
Web Site/Application
Name
URLs
Web Site Owner
Scope of
Assessment
Compliance Level
Initial Testing for this VPAT was completed on XXXXXXX:

 Release Version Tested was
 Assistive Technologies used to test: XXXXX
 Automated Tools and Hand Validation were also used
This site relies on the following Accessibility Supported Technologies:

 XXXXXX

6
3. VPAT Sections Summary
Table 2: Summary Table: Voluntary Product Accessibility Template

Criteria Supporting Features Remarks and Explanations
Section 1194.21 Software Applications
and Operating Systems
Section 1194.22 Web-based internet
information and applications
Section 1194.23 Telecommunications
Products
Section 1194.24 Video and Multi-media
Products
Section 1194.25 Self-Contained, Closed
Products
Section 1194.26 Desktop and Portable
Computers
Section 1194.31 Functional Performance
Criteria
Section 1194.41 Information,
Documentation and Support - Detail

7
4. Compliancy
The following tables indicate the code section, compliance criteria, success criteria, and
any explanatory text needed to show the support for Section 508 and it’s corresponding
WCAG 2.0 (508/255 Refresh) criteria. Remarks add additional clarification specific to the
COMPANY NAME web application.
For more detailed information, the 508-specific paragraph information in the Statement
column of the compliancy table is linked to the Access Board site through the section
letters (A). WCAG 1 Checkpoints are linked to the W3C specific guideline, and WCAG
2.0 success criteria in Techniques are linked to the W3C WCAG 2.0 full reference.
As shown in these tables, COMPANY NAME complies with the standards as defined for
an accessible website.

8
Compliancy
Table 3: Compliancy by Criteria - Mapping Section 508 to WCAG 1.0 & WCAG 2.0 with specific remarks on the COMPANY NAMEcompliancy
1 2
Criteria Section 508 (22) 508 Mapped to WCAG WebAim Recommendation to Our Compliancy Remarks
Meet Success Criteria WCAG2 Supporting Features Explanations
3 4 5
Statement, Need, Goal Checkpoint, Principal, Guideline,
Success Criteria, Techniques
Statement (508 WCAG 1 Checkpoint Success Criteria Detail What we Support Site or Screen
Wording): WCAG 2 Principal Specific
WCAG 2 Guideline
(A) 1.1 Non-text elements 1.1.1 All images, form image
A text equivalent for every non- buttons, and image map hot
text element shall be provided 1 Perceivable spots have appropriate,
(e.g., via "alt", "longdesc", or in equivalent alternative text. Not Applicable
element content). 1.1 Text Alternatives, 1.3 Images that do not convey
Adaptable content, are decorative, or with
content that is already conveyed
in text are given null alt text
(alt="") or implemented as CSS
backgrounds. All linked images
have descriptive alternative text.
Equivalent alternatives to
complex images are provided in
context or on a separate (linked
and/or referenced via longdesc)
page.
Form buttons have a descriptive
1
Taken from the California State University Equally Effective Access HTTP://WWW.CSULB.EDU/~WED/PUBLIC/EQEFFACC/INDEX.HTML
2
Taken from WebAim (Web Accessibility in Mind) How to Meet WCAG 2.0 Success Criteria HTTP://WWW.W3.ORG/WAI/WCAG20/QUICKREF/
3
Statement Taken Directly from § 1194.22 Web-based intranet and internet information and applications
HTTP://WWW.SECTION508.GOV/INDEX.CFM?FUSEACTION=STDSDOC
4
Taken from the California State University Equally Effective Access HTTP://WWW.CSULB.EDU/~WED/PUBLIC/EQEFFACC/INDEX.HTML
5
Taken from the Access Board Section 508 Standards HTTP://WWW.ACCESS-BOARD.GOV/SEC508/STANDARDS.HTM , California State University
Equally Effective Access HTTP://WWW.CSULB.EDU/~WED/PUBLIC/EQEFFACC/INDEX.HTML and WebAim WAI Guidelines and Techniques
HTTP://WWW.W3.ORG/WAI/GUID-TECH.HTML
Symantec Corporation 508 VPAT VIP December 9, 2021

9
Compliancy
value.
Form inputs have associated
text labels or, if labels cannot be
used, a descriptive title attribute.
Embedded multimedia is
identified via accessible text.
Frames are appropriately titled.
1.3.3 Semantic markup is used
to designate headings (<h1>),
lists (<ul>, <ol>, and <dl>),
emphasized or special text
(<strong>, <code>, <abbr>,
<blockquote>, for example), etc.
Semantic markup is used
appropriately.
Tables are used for tabular
data. Where necessary, data
cells are associated with their
headers. Data table captions
and summaries are used where
appropriate.
Text labels are associated with
form input elements. Related
form elements are grouped with
fieldset/legend.
Need: Success Criteria: Supports with
Exceptions
Non textual information like 1.1.1: Non-Text Content, 1.3.3
pictures, graphs or charts Sensory Characteristics
cannot be perceived by many
users. Assistive technology
cannot identify a non-text
element or recognize the
meaning of a non-text element
without textual content to
describe it.

10
Compliancy
Goal For Equally Techniques for Equally Doesn’t Support

Effective Access: Effective Access:
Text must be provided for non- Successful removal of the need
text elements so that the identified by 11194.22(a) at the
identity and meaning can be level of equally effective access
convey by assistive technology is met by techniques sufficient
in a mode that the user can for WCAG 2.0 Success Criteria
perceive. 1.1.1 and 1.3.3.
WCAG 2 Guideline
(B) 1.4 Multimedia presentation 1.2 .1 A descriptive text
Equivalent alternatives for any transcript (including all relevant
multimedia presentation shall 1 Perceivable visual and auditory clues and Not Applicable
be synchronized with the indicators) is provided for non-
presentation. 1.2 Time-based Media live, web-based audio (audio
podcasts, MP3 files, etc.).
A text or audio description is
Need: Success Criteria: provided for non-live, web-
Supports with
based video-only (e.g., video Exceptions
Multimedia differs from text, 1.2.1 Audio-only and Video Only that has no audio track).
pictures or pure audio in two (Prerecorded), 1.2.2 Captions
important ways: (1) more than (Prerecorded); 1.2.3 Audio 1.2.2 Synchronized captions are
one perceptual mode is used to Description or Full Text provided for non-live, web-
convey the content and (2) the Alternative. based video (YouTube videos,
meaning of the material etc.) Note: This is an AA
frequently depends on requirement in WCAG 2.0
synchronizing the information
presented in different modes. 1.2.3 A descriptive text
This requires text alternatives transcript OR audio description
for non-text elements and a audio track is provided for non-
synchronized time-based live, web-based video
delivery of text alternatives for
non-text items. The
synchronized text for audio is

11
Compliancy
called captioning.
Synchronized captioning is the See, how to meet 1.2.1, 1.2.2
solution for multi-media sound. and 1.2.3 depending on the case
If the medium has audio mode at hand.
then a text equivalent must be
present and synchronize with
video. If the video portion has
content that is essential to
understanding the
presentation, then there must
be audio description or a full
text equivalent for this video
content. This audio or text
description must also be
synchronize with the graphical
information in the presentation.
For completeness, all time
based media should be
addressed. For Audio Only a
full text alternative is provided.
For Video only either a text
alternative or audio track is
provided.
WCAG 2 Guideline
(C) 2.1 Color 1.4.1 Color is not used as the
Web pages shall be designed sole method of conveying
so that all information 1 Perceivable content or distinguishing visual
conveyed with color is also elements. Not Applicable
available without color, for 1.4 Distinguishable Color alone is not used to
example from context or distinguish links from
markup. surrounding text unless the

12
Compliancy
luminance contrast between the

link and the surrounding text is
at least 3:1 and an additional
differentiation (e.g., it becomes
underlined) is provided when
the link is hovered over or
receives focus.
Exceptions
Users who cannot perceive 1.4.1 Use of Color
differences in color cannot use
information that is only
conveyed through color.
Provide additional cues that See How to Meet 1.4.1
convey the same differences
without using color.
WCAG 2 Guideline
(D) 6.1 Style Sheets 1.3 Semantic markup is used to
Documents shall be organized designate headings (<h1>), lists
so they are readable without 1 Perceivable (<ul>, <ol>, and <dl>), Not Applicable
requiring an associated style emphasized or special text
sheet. 1.3 Adaptable (<strong>, <code>, <abbr>,
<blockquote>, for example), etc.
Semantic markup is used
appropriately.
Tables are used for tabular
data. Where necessary, data
cells are associated with their
headers. Data table captions
and summaries are used where
appropriate.

13
Compliancy
Text labels are associated with

form input elements. Related
form elements are grouped with
fieldset/legend.
Exceptions
The organizational structure of 1.3.1 Info and Relationships and
information in a document and 1.3.2 Meaningful Sequence.
its associated meaning may
depend on a presentation style
that some users cannot
perceive.
Create a flexible data format 1.3.1 and 1.3.2 cover Section
that preserves the 508 1194.22 (d). The sufficient
organizational structure of the techniques to satisfy 1194.22 (d)
document when the material is can be found through the link
presented in an alternative How to Meet 1.3.1 and How to
mode required by the user to Meet 1.3.2. For 1.3.1 use the
perceive the document. techniques 1–4 in Situation A for
technologies with semantic
structure to meet 1194.22(d).
Plain text and HTML preformated
text can easily violate 508 (d) as
well as 1.3.1 and 1.3.2. For
these cases use the sufficient
techniques in Situation B, the
technology in use does not
provide semantic structure, to
comply.
WCAG 2 Guideline

14
Compliancy
( E) 1.2 Server-side image maps 2.1.1 All page functionality is

Redundant text links shall be available using the keyboard,
provided for each active region 2 Operable unless the functionality cannot
of a server-side image map. be accomplished in any known
Not Applicable
2.1 Keyboard Accessible way using a keyboard (e.g., free
hand drawing).
Page-specified shortcut keys
and accesskeys (accesskey
should typically be avoided) do
not conflict with existing browser
and screen reader shortcuts.
2.1.2 Keyboard focus is never
locked or trapped at one
particular page element. The
user can navigate to and from
all navigable page elements
using only a keyboard.

Exceptions
Without redundant links there is 2.1.1 Keyboard
no URL on the page that can
be located and and activated
with a keyboard. The server
side maps do not provide this.
In any map provide full The inclusion of redundant links
keyboard access to all on the page just creates a client-
functionality - no exceptions. side method of activating the
links in a keyboard accessible
way. If the client side links invoke
Scripts to implement functionality
then use How to Meet 2.1.1.
Even client side image maps

15
Compliancy
should include redundant textual

links.
WCAG 2 Guideline
(F) 9.1 Client-side image maps See 2.1 Above
Client-side image maps shall
be provided instead of server- 2 Operable
side image maps except where Not Applicable
the regions cannot be defined 2.1 Keyboard Accessible
with an available geometric
shape.

Exceptions
Same as (e), server side maps, 2.1.1 Keyboard
there must be a keyboard
accessible method to activate
the hot spots in the map. Client
side map elements provide
semantic code that contains all
the properties needed to
support the other criteria (like
text for non-text items etc.) and
they are navigable by
keyboard.
In any map provide full If the client side links invoke
keyboard access to all Scripts to implement functionality
functionality - no exceptions. then use How to Meet 2.1.1.
Today server side maps are
never required. When using
maps use client side maps only

16
Compliancy
WCAG 2 Guideline
( G) 5.1 Data tables See 1.3 above
Row and column headers shall
be identified for data tables. 1 Perceivable Not Applicable
1.3 Adaptable

Exceptions
A data table is a rectangular 1.3.1 Info and Relationships
configuration of textual data
divided into horizontal rows and
vertical columns. Each entry
within a table has a specific
meaning that depends upon its
location within the table.
Usually the first text item in a
row and / or column of the table
identifies the meaning of the
data in the rest of the row and /
or column. These values are
called the row and column
headers. Unless these items
are marked as header
elements assistive technology
may not recognize their
significance to the table, and a
user of assistive technology
cannot know the meaning of
cells within a table.
Create a flexible table format Success Criterion 1.3.1 covers

17
Compliancy
that preserves the Section 508 1194.22 (g). The

organizational structure of the sufficient techniques to satisfy
table when the material is 1194.22 (g) can be found
presented in an alternative through the link How to Meet
mode required by the user to 1.3.1. Look at Situation B, group
perceive the table. In particular, 4, techniques: H51: Use table
the location of data cells must markup to present tabular
be identifiable in terms of the information, H63: Using the
row and column that hold the scope attribute to associate
data cell. Headers must be header cells and data cells in
used so the assistive data tables. You may use H43:
technology can inform the user Using id and header attributes to
of the row and column headers associate data cells with header
associated with a given data cells in data tables, but it is not
entry within the interior of the required for simple data tables.
table.
WCAG 2 Guideline
(H) 5.2 Markup & tables See 1.3 above
Markup shall be used to
associate data cells and 1 Perceivable
header cells for data tables that Not Applicable
have two or more logical levels 1.3 Adaptable
of row or column headers.

Exceptions
With two or more levels of table 1.3.1 Info and Relationships
headers the connection of a
header to a cell may not be
determined by physical position
as in the case of simple data

18
Compliancy
tables. To understand the

meaning of data in a table cell
when one cannot perceive the
associated header values one
must have a way to identify the
complete collection of headers
associated with a given cell.
All users have full knowledge of See How to Meet 1.3.1 . Look
the values and relationships of specifically at H63: Using the
headers associated with all scope attribute to associate
data cells in order to interpret header cells and data cells in
the meaning of each data data tables (HTML) and H43:
value. Using id and headers attributes
to associate data cells with
header cells in data tables
(HTML).
WCAG 2 Guideline
(I) 12.1 Frames 2.4.1 A link is provided to skip
Frames shall be titled with text navigation and other page
that facilitates frame 2 Operable elements that are repeated
identification and navigation. across web pages.
Not Applicable
2.4 Navigable If a page has a proper heading
structure, this may be
considered a sufficient
technique instead of a "Skip to
main content" link. Note that
navigating by headings is not
yet supported in all browsers.
If a page uses frames and the
frames are appropriately titled,
this is a sufficient technique for

19
Compliancy
bypassing individual frames.

2.4.2 The web page has a
descriptive and informative page
title.
2.4.3 The navigation order of
links, form elements, etc. is
logical and intuitive.
2.4.4 The purpose of each link
(or form image button or image
map hotspot) can be determined
from the link text alone, or from
the link text and it's context
(e.g., surrounding paragraph,
list item, table cell, or table
headers).
Links (or form image buttons)
with the same text that go to
different locations are readily
distinguishable.
Exceptions
Frames are a technique to 2.4.1 Bypass Blocks
group material that is used on
multiple pages. Without
meaningful titles a user may
not perceive the purpose of the
grouping that may be apparent
from other perceptual cues.
Give all frames in a frame set See How to meet 2.4.1. There is
meaningful titles that identify controversy concerning the use
the function of their content. of frames. In particular, they do
not linearize well. If frames are
not already deployed, consider
using other methods to group

20
Compliancy
repeated items. Note: The

Success Criterion 2.4.2 Page
Titles should also apply here
because framesets are really
multi-page pages and the frame
titles identify independent pages,
but there is no mention of frames
in the success criteria for 2.4.2.
The specific technique for frame
titles is H64: Using the title
attribute of the frame and iframe
elements.
WCAG 2 Guideline
(J) 7.1 Flickering 2.3.1 No page content flashes
Pages shall be designed to more than 3 times per second
avoid causing the screen to 2 Operable unless that flashing content is
flicker with a frequency greater sufficiently small and the flashes Not Applicable
than 2 Hz and lower than 55 2.3 Seizures are of low contrast and do not
Hz. contain too much red.

Exceptions
Flicker can cause seizures. 2.3.1 Three Flash or Below
Threshold
Never cause seizures. Provide See How to meet 2.3.1. Follow
a means to avoid flicker, and these instructions precisely.
never flicker within the
specified range.

21
Compliancy

WCAG 2 Guideline
(K) 11.4 Text-only page See 1.3 above
A text-only page, with
equivalent information or 1 Perceivable
functionality, shall be provided
to make a web site comply with 1.3 Adaptable
the provisions of these
standards, when compliance Not Applicable
cannot be accomplished in any
other way. The content of the
text-only page shall be updated
whenever the primary page
changes.

Exceptions
If a technology exists that 1.3.1 Info and Relationships
cannot be made accessible in
any other way, then text may
be the only way to convey the
content. This situation is almost
nonexistent. Ajax, Applets,
Objects and Multimedia can all
be addressed using techniques
given here. There are
accessible Flash guidelines.
PDF can be made accessible.
It is almost impossible to See, How to meet 1.3.1. In this
achieve equally effective case use Situation B (The
access with text-only data technology in use does NOT
except for textual data itself. provide the semantic structure)

22
Compliancy
One thing that can get the text- and use the method given here
only document closer is to to represent tabular data. It is
provide up to date content much easier to create an
equivalence and provide text accessible medium in the first
cues that indicate document place than it is to create an
structure. equally effective text-only
substitute. Note 1: The
techniques for 1.3.1 Situation B
do not describe how to
implement text only tables. Here
is a technique that is faithful.
Linearized Tables: To represent
a textual data table use a
relational data format in a linear
order. That is, use the set of
column headers for field names.
Each row is a list of ordered
pairs field names paired with its
data values. If row headers are
present then use these names
as row titles. One per table row.
The list of all such rows is the
table. This document is an
example of a linearized table in
relational form. The<h2>
elements are row headers. The
<h3> elements are column
headers. The data values are the
text contents associated with the
<h3> elements.
WCAG 2 Guideline
(L) 8.1 Scripting languages 4.1.1 Significant HTML/XHTML

23
Compliancy
When pages utilize scripting Priority 2 WCAG1, part of 508 validation/parsing errors are Not Applicable
languages to display content, avoided. Check at
or to create interface elements, 4 Robust http://validator.w3.org/
the information provided by the 4.1.2 Markup is used in a way
script shall be identified with 4.1 Compatible that facilitates accessibility. This
functional text that can be read includes following the
by assistive technology. HTML/XHTML specifications
and using forms, form labels,
frame titles, etc. appropriately.
Exceptions
Script can change the page 4.1.2 Name, Role, Value
environment without notifying
the user agent. It can also
create functionality for grouping
elements like <span> and
<div> that duplicates or
extends the underlying markup
language. In both cases the
standard application program
interfaces provided by
operating system environments
can be bypassed and assistive
technology cannot interact with
what is occurring at a given
time. This locks the user with a
disability out of the process.
Script must communicate See How to use 4.1.2. As of this
through the standard writing the WAI ARIA documents
accessibility application are still working drafts. However,
programming interface WAI ARIA techniques provide
provided by system so that accessible interfaces to Scripting
compliant assistive technology languages that follow the
will function as needed. protocols and several browsers

24
Compliancy
and took kits support them.

WCAG 2 Guideline
(M) 6.3, 6.4, 8.1 Applets, plug-ins or Accessibility Supported
When a web page requires that other applications Using a technology in a way that
an applet, plug-in, or other Priority 2 WCAG1, part of 508 is accessibility supported means
application be present on the that it works with assistive
client system to interpret page ALL technologies (AT) and the
content, the page must provide accessibility features of Not Applicable
a link to a plug-in or applet that As apply to the UI of the specific operating systems, browsers,
complies with §194.21(a) technology. Accessibility and other user agents.
through (l). Supported Technology features can only
be relied upon to conform to
WCAG 2.0 success criteria if
they are used in a way that is
"accessibility supported".
Technology features can be
used in ways that are not
accessibility supported (do not
work with assistive
technologies, etc.) as long as
they are not relied upon to
conform to any success criterion
F ULL DESCRIPTION
Exceptions
An object or applet is free to As apply to the UI of the specific
use any interface it chooses to technology. Accessibility
display within its user agent. It Supported
is generic software running in a
browser or media player. To
function properly it must satisfy
the software paragraph of

25
Compliancy
Section 508.
The interface must be See in the WCAG 2.0 Guidelines
perceivable, operable, the parts relating to Accessibility
understandable and robust. Supported: Important Terms in
The W3C term for this type of WCAG 2.0 —Accessibility
Web technology is accessibility Supported, and Conformance
supported Requirements —4. Accessibility
Supported is Required. Also, see
Understanding Accessibility
Supported.
WCAG 2 Guideline
(N) 10.2, 12.4, 9.3 Electronic forms See 1.3 above
When electronic forms are Priority 2 WCAG1, part of 508 See 2.1 above
designed to be completed on- 3.2 .1 When a page element
line, the form shall allow people 1 Perceivable, 2 Operable and 3 receives focus, it does not result
using assistive technology to Understandable in a substantial change to the
access the information, field page, the spawning of a pop-up
elements, and functionality 1.3 Adaptable, 2.1 Keyboard window, an additional change of
Not Applicable
required for completion and Accessible, 3.2 Predictable, and keyboard focus, or any other
submission of the form, 3.3 Input Assistance. change that could confuse or
including all directions and disorient the user.
cues. 3.2.2 When a user inputs
information or interacts with a
control, it does not result in a
substantial change to the page,
the spawning of a pop-up
window, an additional change of
keyboard focus, or any other
change that could confuse or
disorient the user unless the
user is informed of the change

26
Compliancy
ahead of time.
3.3.1 Required form elements or
form elements that require a
specific format, value, or length
provide this information within
the element's label (or if a label
is not provided, within the
element's title attribute).
If utilized, form validation cues
and errors (client-side or server-
side) alert users to errors in an
efficient, intuitive, and
accessible manner. The error is
clearly identified, quick access
to the problematic element is
provided, and user is allowed to
easily fix the error and resubmit
the form.
3.3.2 Sufficient labels, cues, and
instructions for required
interactive elements are
provided via instructions,
examples, properly positioned
form labels, and/or
fieldsets/legends.
Exceptions
Lack of access to online forms 1.3.1 Info and Relationships,
means loss of access to real 2.1.1 Keyboard, and 2.1.2 No
world services. For example, a Keyboard Traps, 3.2.1 On
person who uses an a human Focus, 3.2.2 On Input, 3.3.1
operator to schedule a flight will Error Suggestion and 3.3.2
usually pay more than a person Labels or Instructions.
who orders on the web.

27
Compliancy
Everyone can read and operate See How to meet 1.3.1 , parts
all forms. relating to Forms: H44: Using
label elements to associate text
labels with form controls , H65:
Using the title attribute to identify
form controls when the label
element cannot be used , H71:
Providing a description for
groups of form controls using
fieldset and legend elements ,
H85: Using OPTGROUP to
group OPTION elements inside a
SELECT, H82: Grouping form
controls with FIELDSET and
LEGEND. Also see How to meet
2.1.1 and How to meet 2.1.2 as
well as How to Meet 3.2.1, How
to Meet 3.2.2, and How to Meet
3.3.2. Keyboard control, freedom
from keyboard traps, safe
behavior on focus and on input
are all necessary for effective
online form handling. See How to
Meet 3.3.1 and How to Meet
3.3.2 for providing a minimum
level of help for input.
WCAG 2 Guideline
(O) 13.5, 13.6 Navigation links See 2.4 above
A method shall be provided
that permits users to skip Priority 2 WCAG1, part of 508
repetitive navigation links. Not Applicable
2 Operable, 2.4 Navigable

28
Compliancy

Exceptions
The ability to skip repeated 2.4.1 Bypass Blocks
links saves lots of time
stepping through links one by
one looking for the piece of
information you want.
Links should be grouped in See How to meet 2.4.1. The
identifiable ways and a method techniques: H69: Providing
to jump to of from them using heading elements at the
assistive technology must exist. beginning of each section of
content; H50: Using structural
elements to group links; H70:
Using frame elements to group
blocks of repeated material AND
H64: Using the title attribute of
the frame and iframe elements
are guaranteed to provide
equally effective access. Skip
links are less reliable, and often
produce a maze of links that
obscure page meaning.
WCAG 2 Guideline
(P) Timed response 2.2.1 If a page or application
When a timed response is has a time limit, the user is
required, the user shall be No Equivalent in WCAG 1.0 given options to turn off, adjust,
alerted and given sufficient or extend that time limit. This is Not Applicable
time to indicate more time is 2 Operable, 2.2 Enough Time not a requirement for real-time
required events (e.g., an auction), where
the time limit is absolutely
required, or if the time limit is

29
Compliancy
longer than 20 hours.

2.2.2 Automatically moving,
blinking, or scrolling content that
lasts longer than 3 seconds can
be paused, stopped, or hidden
by the user. Moving, blinking, or
scrolling can be used to draw
attention to or highlight content
as long as it lasts less than 3
seconds.
Automatically updating content
(e.g., automatically redirecting
or refreshing a page, a news
ticker, AJAX updated field, a
notification alert, etc.) can be
paused, stopped, or hidden by
the user or the user can
manually control the timing of
the updates.
Exceptions
People with disabilities need 2.2.1 Timing Adjustment, 2.2.2
more time to complete many Pause, Stop, Hide.
tasks.
A method to provide sufficient See How to meet 2.2.1 and How
time to complete an on-line to Meet 2.2.2. The first
task without penalty. techniques address user control
over timed events. The second
techniques provide user control
over intrusive timed events.
WCAG 2 Guideline

30
Compliancy
Doesn’t Exist 1.4.2 A mechanism is provided

to stop, pause, mute, or adjust
To meet level A perceivable volume for audio that Not Applicable
Guideline 1.4 Distinguishable automatically plays on a page
for more than 3 seconds.

Exceptions
1.4.2 Audio Control. Users must
be able to shut off or control the
volume of a sound that lasts
more than 3 seconds.
See How to Meet 1.4.2.
WCAG 2 Guideline
Doesn’t Exist See 2.4.2 above
To meet level A operable:
Guideline 2.4 Navigable Not Applicable

Exceptions
2.4.2 Page Titles. Surprisingly
508 does not require page titles.
Frame titles are only implied by
their use in grouping repeated
links

31
Compliancy

Use, How to Meet 2.4.2 for
techniques.
WCAG 2 Guideline
Doesn’t Exist 3.1.1 The language of the page
is identified using the HTML
To meet level A understandable lang attribute (<html lang="en">, Not Applicable
Guideline 3.1 Readable for example).

Exceptions
3.1.1 Language of the Page
The default human language of
each web page should be
programmatically determined.
Use, How to Meet 3.1.1
WCAG 2 Guideline
Doesn’t Exist See 4.1.1 above
To meet level A robust
Guideline 4.1
Need: Success Criteria: Not Applicable

Compatible, 4.1.1 Parsing: In
content implemented using
markup languages, elements

32
Compliancy
have complete start and end Supports with

tags, elements are nested
according to their specifications,
Exceptions
elements do not contain
duplicate attributes, and any IDs
are unique, except where the
specifications allow these Doesn’t Support
features.
Goal For Equally Techniques for Equally

This really says follow standards,
and don't use silly shortcuts. See
Understanding 4.1.1.

33
Supporting Information for this VPAT
A. Section 1194.31 Functional Performance Criteria

Table 4: Functional Performance Criteria
508 Clause Criteria Supporting Remarks and
Features Explanations
1194.31(a) At least one mode of

operation and information
retrieval that does not require
user vision shall be provided,
or support for Assistive
Technology used by people
who are blind or visually
impaired shall be provided.
1194.31(b) At least one mode of
visual acuity greater than
20/70 shall be provided in
audio and enlarged print
output working together or
independently, or support for
Assistive Technology used by
people who are visually
impaired shall be provided.
1194.31(c) At least one mode of
user hearing shall be
provided, or support for
people who are deaf or hard
of hearing shall be provided
1194.31(d) Where audio information is
important for the use of a
product, at least one mode of
retrieval shall be provided in
an enhanced auditory fashion,
or support for assistive
hearing devices shall be
provided.
1194.31(e) At least one mode of
user speech shall be
provided, or support for
people with disabilities shall
be provided.
1194.31(f) At least one mode of
fine motor control or
simultaneous actions and that
is operable with limited reach

34
and strength shall be
provided.

35
B. Section 1194.41 Product Information,

Documentation and Support
Web application help is available online within the web application using direct links on all pages.
In addition to the online help, the following is available on request:
Table 5: Product Help and Support

Criteria Supporting Remarks and Explanations
Features
(a) Product support

documentation provided to
end-users shall be made
available in alternate formats
upon request, at no additional
charge
(b) End-users shall have
access to a description of the
accessibility and compatibility
features of products in
alternate formats or alternate
methods upon request, at no
additional charge.
(c) Support services for
products shall accommodate
the communication needs of
end users with disabilities.

36
C. Supporting Information for this VPAT

The following documents contain information used to create this VPAT and to understand 508
and the 508/255 Refresh:
 "Web Content Accessibility Guidelines (WCAG 2.0)" W3C Recommendation 11

December 2008, available at http://www.w3.org/TR/WCAG20/
 “How to Meet WCAG 2.0" reference document, which contain suggested techniques for
each Success Criteria, available at http://www.w3.org/WAI/WCAG20/quickref/
 "Understanding WCAG 2.0", available at http://www.w3.org/TR/UNDERSTANDING-
WCAG20/
 "Understanding Accessibility Support", available at
http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-
support-head
 “Official 508”, available at http://www.section508.gov/index.cfm?fuseAction=stdsdoc
 “Equally Effective Access: Mapping 508 to WACG 2.0”, from
http://www.csulb.edu/~wed/public/EqEffAcc/index.html
 “The 508-255 Refresh (ANPRM) Analysis and Comment”, http://508-255-
refresh.trace.wisc.edu/
 “Plain(er) Language Version of 508-255 ANPRM”, http://508-255-
refresh.trace.wisc.edu/content/plainer-language-version-508-255-anprm

37

Voluntary Product Accessibility Template® Section 508 Standards Compliancy (1194)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Voluntary Product Accessibility Template® Section 508 Standards Compliancy (1194)

Uploaded by

Copyright:

Available Formats

Voluntary Product Accessibility Template®

Section 508 Standards Compliancy (1194)

COMPANY NAME Section 508 Standards Compliancy PRODUCT

COMPANY NAME Section 508 Standards Compliancy PRODUCT

COMPANY NAME 508 VPAT PRODUCT December 9, 2021

VPAT Voluntary Product Accessibility Template (this document)

COMPANY NAME 508 VPAT PRODUCT December 9, 2021

The 508/255 Refresh

COMPANY NAME Section 508 Standards Compliancy PRODUCT

Initial Testing for this VPAT was completed on XXXXXXX:

This site relies on the following Accessibility Supported Technologies:

COMPANY NAME 508 VPAT PRODUCT December 9, 2021

Table 2: Summary Table: Voluntary Product Accessibility Template

COMPANY NAME 508 VPAT PRODUCT December 9, 2021

COMPANY NAME 508 VPAT PRODUCT December 9, 2021

Symantec Corporation 508 VPAT VIP December 9, 2021

Symantec Corporation 508 VPAT VIP December 9, 2021

Goal For Equally Techniques for Equally Doesn’t Support

Symantec Corporation 508 VPAT VIP December 9, 2021

Symantec Corporation 508 VPAT VIP December 9, 2021

luminance contrast between the

Symantec Corporation 508 VPAT VIP December 9, 2021

Text labels are associated with

Symantec Corporation 508 VPAT VIP December 9, 2021

( E) 1.2 Server-side image maps 2.1.1 All page functionality is

Need: Success Criteria: Supports with

Symantec Corporation 508 VPAT VIP December 9, 2021

should include redundant textual

Need: Success Criteria: Supports with

Symantec Corporation 508 VPAT VIP December 9, 2021

Need: Success Criteria: Supports with

Symantec Corporation 508 VPAT VIP December 9, 2021

that preserves the Section 508 1194.22 (g). The

Need: Success Criteria: Supports with

Symantec Corporation 508 VPAT VIP December 9, 2021

tables. To understand the

Symantec Corporation 508 VPAT VIP December 9, 2021

bypassing individual frames.

Symantec Corporation 508 VPAT VIP December 9, 2021

repeated items. Note: The

Need: Success Criteria: Supports with

Symantec Corporation 508 VPAT VIP December 9, 2021

Wording): WCAG 2 Principal Specific

Need: Success Criteria: Supports with

Symantec Corporation 508 VPAT VIP December 9, 2021

Symantec Corporation 508 VPAT VIP December 9, 2021

Symantec Corporation 508 VPAT VIP December 9, 2021

and took kits support them.

Symantec Corporation 508 VPAT VIP December 9, 2021

Symantec Corporation 508 VPAT VIP December 9, 2021

Symantec Corporation 508 VPAT VIP December 9, 2021

Symantec Corporation 508 VPAT VIP December 9, 2021

Need: Success Criteria: Supports with

Symantec Corporation 508 VPAT VIP December 9, 2021

longer than 20 hours.

Symantec Corporation 508 VPAT VIP December 9, 2021

Doesn’t Exist 1.4.2 A mechanism is provided

Need: Success Criteria: Supports with

Need: Success Criteria: Supports with

Symantec Corporation 508 VPAT VIP December 9, 2021

Effective Access: Effective Access:

Need: Success Criteria: Supports with

Need: Success Criteria: Not Applicable