Page 1

Google Accessibility Conformance Report
International edition, based on VPAT® Version 2.4Rev
1

Name of product/version: Google Sites
Report date: 21 December 2023
Product description: Google Sites is a web application which allows users to create
and customize websites through a series of tools and
templates.
Contact information: [email protected]
Evaluation methods used: The W3C Website Accessibility Conformance Evaluation
Methodology (WCAG-EM) was followed for conducting the
accessibility audit. The testing included manual accessibility
testing, automated accessibility tools, and testing with assistive
technology across multiple platforms and browsers.

The following applications were used as part of the audit to
identify potential accessibility issues:
● Desktop browsers: Chrome (NVDA)
● Assistive technologies: NVDA
● Accessibility testing tools: Deque DevTools Pro, Deque
Auditor, Color Contrast Analyser
Applicable
standards/guidelines:
This report covers the degree of conformance for the following
accessibility standards/guidelines:
● Web Content Accessibility Guidelines (WCAG) 2.0 Level
A and AA
● Web Content Accessibility Guidelines (WCAG) 2.1 Level
A and AA
● Revised Section 508 standards published January 18,
2017, and corrected January 22, 2018
● EN 301 549 Accessibility requirements for ICT products
and services - V3.1.1 (2019-11) and EN 301 549
Accessibility requirements for ICT products and services
- V3.2.1 (2021-03)

1
“Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information
Technology Industry Council (ITI)

Page 2

Table of contents
Google Accessibility Conformance Report 1
Table of contents 2
Tested Pages 3
Tested components that appear on multiple pages 3
Terms 3
WCAG 2.1 Report 4
Table 1: Success Criteria, Level A 4
Table 2: Success Criteria, Level AA 30
Table 3: Success Criteria, Level AAA 46
Revised Section 508 Report 46
Chapter 3: Functional Performance Criteria (FPC) 46
Chapter 4: Hardware 49
Chapter 5: Software 50
Chapter 6: Support Documentation and Services 53
EN 301 549 Report 54
Chapter 4: Functional Performance Statements (FPS) 54
Chapter 5: Generic Requirements 57
Chapter 6: ICT with Two-Way Voice Communication 62
Chapter 7: ICT with Video Capabilities 63
Chapter 8: Hardware 64
Chapter 9: Web 65
Chapter 10: Non-Web Documents 66
Chapter 11: Software 67
Chapter 12: Documentation and Support Services 71
Chapter 13: ICT Providing Relay or Emergency Service Access 72
Legal disclaimer 72

Page 3

Tested Pages
● Add Fonts modal
● Copy Site modal
● Main page
● Navigation Settings modal
● New Menu Section modal
● New Page modal
● Page Publish Info
● Publish Settings modal
● Review Changes and Publish page
● Select a File
● Select Image modal
● Unpublish Confirmation modal
● Untitled site page
● Version History page
Tested components that appear on multiple pages
● Edit File taskbar
● Edit Title taskbar
● Edit Image taskbar
● Edit Preview taskbar
● Edit Section taskbar
● Edit YouTube taskbar
● Google Drive sidebar
● Header
● Header Type taskbar
● Insert sidebar
● Pages sidebar
● Text Format taskbar
● Themes sidebar
● Title component
Terms
The terms used in the conformance level information are defined as follows:
Supports: The functionality of the product has at least one method that meets the criterion
without known defects or meets with equivalent facilitation.
Partially supports: Some functionality of the product does not meet the criterion.
Does not support: The majority of product functionality does not meet the criterion.
Not applicable: The criterion is not relevant to the product.

Page 4

Not evaluated: The product has not been evaluated against the criterion. This can be used only
in WCAG Level AAA criteria.
WCAG 2.1 Report
Tables 1 and 2 also document conformance with:
● EN 301 549: Chapter 9 — Web, Sections 10.1–10.4 of Chapter 10 — Non-Web
Documents, Sections 11.1–11.4 and 11.8.2 of Chapter 11 — Software (open and closed
functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 — Documentation and
Support Services
● Revised Section 508: Chapter 5 — 501.1 Scope, 504.2 Content Creation or Editing, and
Chapter 6 — 602.3 Electronic Support Documentation
Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for
full pages, complete processes, and accessibility-supported ways of using technology as
documented in the WCAG 2.1 Conformance Requirements.
Table 1: Success Criteria, Level A
Criteria Conformance
level
Remarks and explanations
1.1.1 Non-text Content (Level
A)
Also applies to:
EN 301 549 Criteria
● 9.1.1.1 (Web)
● 10.1.1.1 (Non-web
document)
● 11.1.1.1.1 (Open
Functionality
Software)
● 11.1.1.1.2 (Closed
Functionality
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
Partially Supports Most non-text content has text
alternatives or a text alternate that
serves an equivalent purpose.

The following exceptions exist:
● An image does not have a
text alternative, so people
who are blind and/or use a
screen reader will not be able
to access the information
available in the image and if it
is an active image, will not
understand its function. This
occurs on the following
pages: Select a File; Add
Fonts modal.

Page 5

● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
1.2.1 Audio-only and Video-
only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
● 9.1.2.1 (Web)
● 10.1.2.1 (Non-web
document)
● 11.1.2.1.1 (Open
Functionality
Software)
● 11.1.2.1.2.1 and
11.1.2.1.2.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Not Applicable Prerecorded audio-only files are not
present.
1.2.2 Captions (Prerecorded)
(Level A)
Also applies to:
EN 301 549 Criteria
● 9.1.2.2 (Web)
Not Applicable Prerecorded videos are not present.

Page 6

● 10.1.2.2 (Non-web
document)
● 11.1.2.2 (Open
Functionality
Software)
● 11.1.2.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
1.2.3 Audio Description or
Media Alternative
(Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
● 9.1.2.3 (Web)
● 10.1.2.3 (Non-web
document)
● 11.1.2.3.1 (Open
Functionality
Software)
● 11.1.2.3.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
Not Applicable Prerecorded videos are not present,
so audio description is not required.

Page 7

● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
1.3.1 Info and Relationships
(Level A)
Also applies to:
EN 301 549 Criteria
● 9.1.3.1 (Web)
● 10.1.3.1 (Non-web
document)
● 11.1.3.1.1 (Open
Functionality
Software)
● 11.1.3.1.2 (Closed
Software) –
Informative only
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Partially Supports Most information, structure, and
relationships conveyed through
presentation can be
programmatically determined or are
available in text.

The following exceptions exist:
● Certain ARIA roles must
contain particular children, or
the relationships between
elements may not be
conveyed to people using
assistive technology, such as
a screen reader. This occurs
on the following pages:
Version History Page; Select
a File; Text Format taskbar;
Themes sidebar; Add Fonts
modal; Insert Sidebar.
● A set of radio buttons is not
programmatically grouped, so
the group label for the set of
radio buttons will not be
conveyed to people who are
blind and/or use a screen
reader and they will not
understand the purpose of
the individual radio buttons.
This occurs on the following
page: Copy Site Modal.
● Some text that visually
functions as a heading is not

Page 8

marked up as a heading, so
the structure of the content is
not properly conveyed to
assistive technologies and
people who are blind and/or
use a screen reader. This
occurs on the following
pages: Google Drive Sidebar;
Review Changes and Publish
page; Select Image Modal;
New Page Modal; New Menu
Section modal.
● Certain ARIA roles must be
contained by particular
parents, or the relationships
between elements may not
be conveyed to people using
assistive technology, such as
a screen reader. This occurs
on the following pages:
Version History Page; Select
a File; Untitled site page;
Google Drive Sidebar; Add
Fonts modal.
1.3.2 Meaningful Sequence
(Level A)
Also applies to:
EN 301 549 Criteria
● 9.1.3.2 (Web)
● 10.1.3.2 (Non-web
document)
● 11.1.3.2.1 (Open
Functionality
Software)
● 11.1.3.2.2 (Closed
Software) –
Informative only
● 11.8.2 (Authoring
Tool)
Partially Supports The reading and navigation order of
most content is logical and intuitive.

The following exceptions exist:
● Some visually hidden content
is announced by a screen
reader, so people who are
blind and/or use a screen
reader may be misled or
confused when hearing
content that is not intended to
be part of the reading order
on the page. This occurs on
the following page: Themes
sidebar.

Page 9

● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
● The screen reader skips and
does not announce
informative static content
(text or images), so the
intended meaning of the
content will be lost or
changed for people who are
blind and/or use a screen
reader. This occurs on the
following pages: Edit Preview
Taskbar; Google Drive
Sidebar; Select Image Modal.
1.3.3 Sensory Characteristics
(Level A)
Also applies to:
EN 301 549 Criteria
● 9.1.3.3 (Web)
● 10.1.3.3 (Non-web
document)
● 11.1.3.3 (Open
Functionality
Software)
● 11.1.3.3 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Supports Instructions to operate and/or
understand content do not rely on
sensory characteristics of
components such as shape, color,
size, visual location.
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria
Partially Supports For most content, color is not used
as the only method to convey
information, indicate an action,

Page 10

● 9.1.4.1 (Web)
● 10.1.4.1 (Non-web
document)
● 11.1.4.1 (Open
Functionality
Software)
● 11.1.4.1 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
prompt a response, or distinguish
visual elements.

The following exceptions exist:
● Color is used as the only
method to convey
information, so that
information will not be
available to people who are
colorblind and people who
are blind and/or use a screen
reader. This occurs on the
following pages: Version
History Page; Edit Section
Taskbar; Edit Preview
Taskbar; Themes sidebar;
Publish Settings Modal; Page
Publish Info.
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria
● 9.1.4.2 (Web)
● 10.1.4.2 (Non-web
document)
● 11.1.4.2 (Open
Functionality
Software)
● 11.1.4.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
Supports A mechanism is provided to stop,
pause, mute, or adjust volume for
audio that automatically plays for
more than 3 seconds.

Page 11

● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
● 9.2.1.1 (Web)
● 10.2.1.1 (Non-web
document)
● 11.2.1.1.1 (Open
Functionality
Software)
● 11.2.1.1.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Does Not Support On most pages, all functionality is
available using only the keyboard
(unless that functionality cannot be
accomplished in any known way
using a keyboard). If shortcut keys
and accesskeys are present, some
may conflict with existing browser
and screen reader shortcuts, and
some functionality based on custom
gestures may not be available when
a screen reader is turned on.

The following exceptions exist:
● Multiple functions cannot be
performed using only the
keyboard, so people who use
the keyboard alone to
navigate and operate content
cannot use these functions.
This occurs on the following
pages: Edit Preview Taskbar;
Page Publish Info; Header
Type Taskbar.
2.1.2 No Keyboard Trap (Level
A)
Also applies to:
EN 301 549 Criteria
● 9.2.1.2 (Web)
● 10.2.1.2 (Non-web
document)
● 11.2.1.2 (Open
Functionality
Software)
Supports Keyboard focus is never locked or
trapped in a particular area, and the
user is able to navigate to and from
all navigable elements using only a
keyboard.

Page 12

● 11.2.1.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
2.1.4 Character Key
Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.2.1.4 (Web)
● 10.2.1.4 (Non-web
document)
● 11.2.1.4.1 (Open
Functionality
Software)
● 11.2.1.4.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
Supports If a single character key shortcut
exists, then the single character key
shortcut can be turned off or
remapped, or it is only active when
the relevant user interface
component is in focus.
2.2.1 Timing Adjustable (Level
A)
Also applies to:
EN 301 549 Criteria
● 9.2.2.1 (Web)
Supports If a time limit exists, the user is given
options to turn off, adjust, or extend
that time limit.

Page 13

● 10.2.2.1 (Non-web
document)
● 11.2.2.1 (Open
Functionality
Software)
● 11.2.2.1 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
2.2.2 Pause, Stop, Hide (Level
A)
Also applies to:
EN 301 549 Criteria
● 9.2.2.2 (Web)
● 10.2.2.2 (Non-web
document)
● 11.2.2.2 (Open
Functionality
Software)
● 11.2.2.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
Supports Moving, blinking, scrolling, or auto-
updating information can be paused,
stopped, hidden, or otherwise
controlled by the user.

Page 14

● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
2.3.1 Three Flashes or Below
Threshold (Level A)
Also applies to:
EN 301 549 Criteria
● 9.2.3.1 (Web)
● 10.2.3.1 (Non-web
document)
● 11.2.3.1 (Open
Functionality
Software)
● 11.2.3.1 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Not Applicable The tested application does not
contain flashing content.
2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria
● 9.2.4.1 (Web)
● 10.2.4.1 (Non-web
document) – Does
not apply
● 11.2.4.1 (Open
Functionality
Software) – Does
not apply
Supports A method is provided to skip
navigation and other page elements
that are repeated across web pages.

Page 15

● 11.2.4.1 (Closed
Software) – Does
not apply
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software) –
Does not apply to
non-web software
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs) – Does not
apply to non-web
docs
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
● 9.2.4.2 (Web)
● 10.2.4.2 (Non-web
document)
● 11.2.4.2 (Open
Functionality
Software) - Does not
apply
● 11.2.4.2 (Closed
Software) – Does
not apply
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
Supports Pages have descriptive and
informative titles.

Page 16

● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria
● 9.2.4.3 (Web)
● 10.2.4.3 (Non-web
document)
● 11.2.4.3 (Open
Functionality
Software)
● 11.2.4.3 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Partially Supports The navigation order of most
interactive elements (such as links,
buttons, or form elements) is logical
and preserves meaning and
operability.

The following exceptions exist:
● Keyboard focus is lost or
misplaced as a result of user
interaction or content update
or refresh, so people who use
the keyboard to navigate
content (including screen
reader users) will become
disoriented. This occurs on
the following page: Select a
File.
2.4.4 Link Purpose (In
Context) (Level A)
Also applies to:
EN 301 549 Criteria
● 9.2.4.4 (Web)
● 10.2.4.4 (Non-web
document)
● 11.2.4.4 (Open
Functionality
Software)
Supports The purpose of the links can be
determined from the link text alone or
from the link text and its
programmatic context.

Page 17

● 11.2.4.4 (Closed
Software
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
2.5.1 Pointer Gestures (Level
A 2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.2.5.1 (Web)
● 10.2.5.1 (Non-web
document)
● 11.2.5.1 (Open
Functionality
Software)
● 11.2.5.1 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
Supports All functionality that can be operated
with a pointer can be operated with
single-point actions.
2.5.2 Pointer Cancellation
(Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.2.5.2 (Web)
Partially Supports For most functionality that can be
operated using a single pointer, at
least one of the following is true:
● The action is not triggered on
the down event.

Page 18

● 10.2.5.2 (Non-web
document)
● 11.2.5.2 (Open
Functionality
Software)
● 11.2.5.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
● The action triggers on the up
event, and a mechanism is
available to abort the function
before completion or to undo
the function after completion.
● The up-event reverses any
outcome of the preceding
down-event.
● Completing the function on
the down-event is essential.

The following exceptions exist:
● An irreversible action occurs
on the down event of multiple
controls, so people with
motor disabilities (such as
tremors) may trigger
unwanted actions. This
occurs on the following page:
Google Drive Sidebar; Select
Image Modal.
2.5.3 Label in Name (Level A
2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.2.5.3 (Web)
● 10.2.5.3 (Non-web
document)
● 11.2.5.3.1 (Open
Functionality
Software)
● 11.2.5.3.2 (Closed
Software) –
Informative only
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Partially Supports For most user interface components
that include visible text labels, the
accessible name matches (or
includes) the visible text in the label.

The following exceptions exist:
● The accessible name of an
interactive element (such as
a link, button, or form input)
does not contain the visible
label, so people who use
speech input to navigate and
operate content will not be
able to access the element.
This occurs on the following
page: Title component.
● An interactive element (such
as a link, button, or form
input) does not have an

Page 19

Revised Section 508 – Does
not apply
accessible name because its
visible label is not
programmatically associated
with the element, so people
who use speech input to
navigate and operate content
will not be able to access the
element. This occurs on the
following page: Text Format
taskbar.
2.5.4 Motion Actuation (Level
A 2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.2.5.4 (Web)
● 10.2.5.4 (Non-web
document)
● 11.2.5.4 (Open
Functionality
Software)
● 11.2.5.4 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
Supports Functionality that can be triggered by
device motion or user motion
detected by a device can be
disabled, and the functionality can be
operated without using motion.
3.1.1 Language of Page (Level
A)
Also applies to:
EN 301 549 Criteria
● 9.3.1.1 (Web)
● 10.3.1.1 (Non-web
document)
Supports The language of each page is correct
and can be determined
programmatically.

Page 20

● 11.3.1.1.1 (Open
Functionality
Software)
● 11.3.1.1.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
● 9.3.2.1 (Web)
● 10.3.2.1 (Non-web
document)
● 11.3.2.1 (Open
Functionality
Software)
● 11.3.2.1 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
Partially Supports In most cases, when an element
receives focus, a change in context
(such as a substantial change to the
page, the spawning of a pop-up
window, or a change in focus) that
may disorient the user does not
occur.

The following exceptions exist:
● When an element receives
keyboard focus, it results in a
substantial, unanticipated
context change (such as a
change in the page content
that changes the meaning of
the page), so people who use
a keyboard to navigate
content (including screen
reader users) may become
confused or disoriented. This

Page 21

● 602.3 (Support
Docs)
occurs on the following page:
Edit Preview Taskbar.
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria
● 9.3.2.2 (Web)
● 10.3.2.2 (Non-web
document)
● 11.3.2.2 (Open
Functionality
Software)
● 11.3.2.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Supports When a user inputs information or
interacts with a control, it does not
result in a substantial change to the
page that could disorient the user
unless the user is informed about the
change ahead of time.
3.3.1 Error Identification
(Level A)
Also applies to:
EN 301 549 Criteria
● 9.3.3.1 (Web)
● 10.3.3.1 (Non-web
document)
● 11.3.3.1.1 (Open
Functionality
Software)
● 11.3.3.1.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
Supports For form controls where an input
error is automatically detected, a text
message or alert is provided that
identifies the field/control where the
error was detected and describes the
error.

Page 22

● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
3.3.2 Labels or Instructions
(Level A)
Also applies to:
EN 301 549 Criteria
● 9.3.3.2 (Web)
● 10.3.3.2 (Non-web
document)
● 11.3.3.2 (Open
Functionality
Software)
● 11.3.3.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Partially Supports For most form controls/input fields
requiring user input, labels,
instructions, and/or error messages
are provided to identify the
controls/input fields in the form so
that users know what input data is
expected.

The following exceptions exist:
● Some labels of elements are
not persistent (always visible
on the page), so each
element's purpose may be
difficult to discover. This
occurs on the following
pages: Version History Page;
Title component.
● The labels for some form
fields are missing, so each
field's purpose is not clear.
This occurs on the following
pages: Themes sidebar; Title
component.
● A group of elements is
missing a visible group label,
so the purpose of the
elements in the group cannot
be understood. This occurs

Page 23

on the following page:
Themes sidebar.
4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria
● 9.4.1.1 (Web)
● 10.4.1.1 (Non-web
document)
● 11.4.1.1.1 (Open
Functionality
Software)
● 11.4.1.1.2 (Closed
Software) – Does
not apply
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Supports For WCAG 2.0, 2.1, EN 301 549,
and Revised 508 Standards, the
September 2023 errata update
indicates this criterion is always
supported. See the WCAG 2.0
Editorial Errata and the WCAG 2.1
Editorial Errata.
4.1.2 Name, Role, Value (Level
A)
Also applies to:
EN 301 549 Criteria
● 9.4.1.2 (Web)
● 10.4.1.2 (Non-web
document)
● 11.4.1.2.1 (Open
Functionality
Software)
● 11.4.1.2.2 (Closed
Software) – Does
not apply
Partially Supports The name, role, and/or value of user
interface components can be
programmatically determined.
However, there are exceptions;

The following exceptions exist:
● An ARIA input field is missing
an accessible name, so
people who are blind and/or
use a screen reader or other
assistive technology will not
know the purpose of the form

Page 24

● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
field. This occurs on the
following pages: Version
History Page; Untitled site
page; Text Format taskbar;
Select Image Modal; Add
Fonts modal.
● A breadcrumb region is
missing one or more required
attributes in its HTML code
that provides its
programmatic role, name,
state, or another property to
assistive technology, so
people who are blind and/or
use a screen reader or other
assistive technology may not
be able to understand the
name, purpose, or current
state of the region and its
contents or how to interact
with the region and contents.
This occurs on the following
page: Google Drive Sidebar.
● Multiple buttons do not have
a programmatic role, so each
button's role (usually button,
but sometimes link or
something else) is not
conveyed to screen readers
and other assistive
technologies and will not be
available to people who use
those technologies. This
occurs on the following
pages: Untitled site page;
Themes sidebar; Page
Publish Info.
● A form is missing an
accessible name, so people

Page 25

who are blind and/or use a
screen reader or other
assistive technology will not
know the purpose of the form
field. This occurs on the
following page: Title
component.
● A frame is missing an
accessible name, so people
who are blind and/or use a
screen reader or other
assistive technology will not
know the purpose of the
frame. This occurs on the
following pages: Version
History Page; Select a File;
Untitled site page; Edit
Preview Taskbar; Google
Drive Sidebar; Review
Changes and Publish page;
Select Image Modal; Add
Fonts modal.
● An element is missing or has
an incorrect programmatic
name, so people who are
blind and/or use a screen
reader or other assistive
technology may not be able
to determine the name of the
element and may not
understand its purpose or
content or how to interact
with it. This occurs on the
following page: Navigation
Settings modal.
● Required ARIA attributes are
missing for an element, so
the element’s name, role, and
values may not be conveyed

Page 26

to people using assistive
technology, like a screen
reader. This occurs on the
following pages: Version
History Page; Google Drive
Sidebar; Select Image Modal.
● An element that appears and
functions like a slider control
does not have the required
attributes in its HTML code
needed to provide its
programmatic role, name,
state, and other properties to
assistive technology, so
people who are blind and/or
use a screen reader or other
assistive technology may not
be able to understand the
element's name, purpose, or
current value or how to
interact with it. This occurs on
the following page: Themes
sidebar.
● The expand/collapse state of
a control is missing or
incorrect, so people using
assistive technology, like a
screen reader, will not know
that the control expands to
reveal additional content.
This occurs on the following
pages: Text Format taskbar;
New Page Modal.
● For some elements that allow
a user either to select or not
select a single option (like a
checkbox or radio buttons) or
to select from among 2 or
more options (like a select

Page 27

dropdown), the state (such as
checked/unchecked or
selected/not selected) is not
conveyed to assistive
technology, so people who
are blind and/or use a screen
reader or other assistive
technology may not be able
to understand the purpose of
each element, the options
available, and whether the
element or an option is
currently checked. This
occurs on the following page:
Edit Section Taskbar;
Themes sidebar; Review
Changes and Publish page;
Header Type Taskbar.
● An element does not have an
attribute in its HTML code
that will provide its
programmatic state (such as
"checked"/"not checked") to
assistive technology or the
state assigned is not correct,
so people who are blind
and/or use a screen reader or
other assistive technology
may not be able to
understand the current state
of the element or how to
interact with it. This occurs on
the following page: New Page
Modal.
● Elements must only use
supported ARIA attributes.
This occurs on the following
pages: Version History Page;
Untitled site page; Edit

Page 28




Preview Taskbar; Themes
sidebar; Add Fonts modal;
Insert Sidebar.

Page 29

Table 2: Success Criteria, Level AA
Criteria Conformance
level
Remarks and explanations
1.2.4 Captions (Live) (Level
AA)
Also applies to:
EN 301 549 Criteria
● 9.1.2.4 (Web)
● 10.1.2.4 (Non-web
document)
● 11.1.2.4 (Open
Functionality
Software)
● 11.1.2.4 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Not Applicable Live multimedia files with audio are
not present, so synchronized
captions are not required.
1.2.5 Audio Description
(Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
● 9.1.2.5 (Web)
● 10.1.2.5 (Non-web
document)
● 11.1.2.5 (Open
Functionality
Software)
● 11.1.2.5 (Closed
Software)
Not Applicable Prerecorded multimedia files are not
present, so audio descriptions are
not required.

Page 30

Criteria Conformance
level
Remarks and explanations
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
1.3.4 Orientation (Level AA 2.1
only)
Also applies to:
EN 301 549 Criteria
● 9.1.3.4 (Web)
● 10.1.3.4 (Non-web
document)
● 11.1.3.4 (Open
Functionality
Software)
● 11.1.3.4 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
Supports Orientation of the content is not
locked to either landscape or portrait
unless a specific orientation is
essential for the functionality.
1.3.5 Identify Input Purpose
(Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Partially Supports The purpose of most input fields that
collect an individual's personal data
are programmatically defined based

Page 31

Criteria Conformance
level
Remarks and explanations
● 9.1.3.5 (Web)
● 10.1.3.5 (Non-web
document)
● 11.1.3.5.1 (Open
Functionality
Software)
● 11.1.3.5.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
on the WCAG list of Input Purposes
for User Interface Components.

The following exceptions exist:
● The autocomplete attribute is
not used correctly for a form
field, so people with motor
impairments or cognitive
impairments that attempt to
autofill the form will not be
able to. This occurs on the
following page: Text Format
taskbar.
1.4.3 Contrast (Minimum)
(Level AA)
Also applies to:
EN 301 549 Criteria
● 9.1.4.3 (Web)
● 10.1.4.3 (Non-web
document)
● 11.1.4.3 (Open
Functionality
Software)
● 11.1.4.3 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
Partially Supports Most text and images of regular text
have the required color contrast ratio
with their backgrounds.

The following exceptions exist:
● The color contrast ratios on
hover or focus between the
text labels of some controls
and their background are less
than 4.5:1, so people who are
colorblind or have low vision
may have difficulty reading
the text label of each control.
This occurs on the following
pages: Version History Page;
Publish Settings Modal; New
Page Modal; Header Type
Taskbar.
● The color contrast ratio
between placeholder text in
an input and the input's

Page 32

Criteria Conformance
level
Remarks and explanations
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
background is less than
4.5:1, so people who are
colorblind or have low vision
may have difficulty reading
the placeholder text. This
occurs on the following page:
Title component.
● The color contrast ratio
between text and its
background is less than
4.5:1, so people who are
colorblind or have low vision
may have difficulty reading
the text. This occurs on the
following pages: Edit Section
Taskbar; Untitled site page;
Add Fonts modal.
● Elements must meet
minimum color contrast ratio
thresholds. This occurs on
the following pages: Version
History Page; Select a File;
Publish Settings Modal; New
Page Modal; New Menu
Section modal; Add Fonts
modal.
1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria
● 9.1.4.4 (Web)
● 10.1.4.4 (Non-web
document)
● 11.1.4.4.1 (Open
Functionality
Software)
Partially Supports Most content is readable and
functional when browser zoom is set
to 200% of its initial size.

The following exceptions exist:
● Content is lost, clipped, or
obscured when the page is
zoomed to 200%, so people
who have low vision and

Page 33

Criteria Conformance
level
Remarks and explanations
● 11.1.4.4.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
need to enlarge text to read it
may not have access to that
content. This occurs on the
following page: Untitled site
page.
● Functionality is lost when the
page is zoomed to 200%, so
people who have low vision
and need to enlarge text to
read it may not have access
to this functionality. This
occurs on the following page:
Header.
● Zooming and scaling must
not be disabled. This occurs
on the following page:
Untitled site page.
1.4.5 Images of Text (Level
AA)
Also applies to:
EN 301 549 Criteria
● 9.1.4.5 (Web)
● 10.1.4.5 (Non-web
document)
● 11.1.4.5.1 (Open
Functionality
Software)
● 11.1.4.5.2 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
Supports When content can be presented
visually using only text, an image of
text is not used to present that text.

Page 34

Criteria Conformance
level
Remarks and explanations
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
1.4.10 Reflow (Level AA 2.1
only)
Also applies to:
EN 301 549 Criteria
● 9.1.4.10 (Web)
● 10.1.4.10 (Non-web
document)
● 11.1.4.10 (Open
Functionality
Software)
● 11.1.4.10 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
Does Not Support Most content on pages is viewable
without scrolling horizontally when
the viewport is set to 320 CSS pixels
wide. However, key functionality is
lost when the pages are resized.

The following exceptions exist:
● Info or functionality is lost due
to overlapping content at
320px equivalent. This occurs
on the following page:
Version History Page.
● Info or functionality is
unavailable at 320px width
equivalent. This occurs on
the following pages: Header;
Untitled site page.
1.4.11 Non-text Contrast
(Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.1.4.11 (Web)
● 10.1.4.11 (Non-web
document)
● 11.1.4.11 (Open
Functionality
Software)
Partially Supports Most of the boundaries and
indicators of the visual state(s) of
each active user component and any
graphics required to understand
content have a 3:1 color contrast
ratio with adjacent color(s) or their
background.

The following exceptions exist:
● The visual boundaries of
some interactive elements

Page 35

Criteria Conformance
level
Remarks and explanations
● 11.1.4.11 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
(like a radio button or input
fields) do not have a 3:1 color
contrast ratio with the
background, so people who
are colorblind or have low
vision may have difficulty
perceiving the boundaries of
the interactive element. This
occurs on the following
pages: Version History Page;
New Page Modal; New Menu
Section modal.
● Some icons (or parts of an
icon required to understand
its content) do not have a 3:1
color contrast ratio with the
background or adjacent
colors, so people who are
colorblind or have low vision
may not be able understand
the information presented by
each icon. This occurs on the
following pages: Untitled site
page; Themes sidebar; Add
Fonts modal.
● The indicators for the state of
some interactive elements
(like checkboxes or radio
buttons) do not have a 3:1
color contrast ratio with the
background, so people who
are colorblind or have low
vision may have difficulty
perceiving the state of the
interactive elements. This
occurs on the following page:
Edit Section Taskbar; Text
Format taskbar; Navigation
Settings modal.

Page 36

Criteria Conformance
level
Remarks and explanations
● The focus indicators of some
interactive elements (like
buttons or input fields) do not
have a 3:1 color contrast ratio
with the background, so
people who are colorblind or
have low vision may have
difficulty perceiving when
each interactive element is
receiving focus. This occurs
on the following pages:
Header; Version History
Page; Edit Section Taskbar;
Untitled site page; Unpublish
Confirmation modal; Google
Drive Sidebar; Text Format
taskbar; Themes sidebar;
Review Changes and Publish
page; Publish Settings Modal;
Select Image Modal; New
Page Modal; Navigation
Settings modal; New Menu
Section modal; Add Fonts
modal; Header Type Taskbar;
Pages Sidebar; Insert
Sidebar; Copy Site Modal;
Edit Image Taskbar.
1.4.12 Text Spacing (Level AA
2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.1.4.12 (Web)
● 10.1.4.12 (Non-web
document)
● 11.1.4.12 (Open
Functionality
Software)
Partially Supports For most content, the spacing
between letters, words, lines of text
and paragraphs can be adjusted with
no loss of content or functionality.

The following exceptions exist:
● When text spacing is
adjusted to help people with
vision, reading and cognitive
disabilities, some content
cannot be seen because it is

Page 37

Criteria Conformance
level
Remarks and explanations
● 11.1.4.12 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
cut off. This occurs on the
following page: Header.
1.4.13 Content on Hover or
Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.1.4.13 (Web)
● 10.1.4.13 (Non-web
document)
● 11.1.4.13 (Open
Functionality
Software)
● 11.1.4.13 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
Partially Supports In most cases when additional
content is triggered by pointer hover
or keyboard focus, that additional
content can be dismissed and
hovered over, and the content
persists until the user dismisses it.

The following exceptions exist:
● Content that appears on
mouse hover or keyboard
focus (such as tooltips, drop-
down menus, or popups) is
not dismissible, so it
obscures all or part of the
original content on the page.
This occurs on the following
pages: Version History Page;
Themes sidebar.
● Content that appears on
mouse hover (such as
tooltips, drop-down menus, or
popups) disappears when the
mouse pointer is moved over
that content, meaning people
with disabilities, especially
people with low vision who
need to magnify text, may not
be able to read the additional

Page 38

Criteria Conformance
level
Remarks and explanations
content. This occurs on the
following pages: Version
History Page; Edit Preview
Taskbar; Google Drive
Sidebar; Review Changes
and Publish page; Select
Image Modal; Page Publish
Info.
2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria
● 9.2.4.5 (Web)
● 10.2.4.5 (Non-web
document) – Does
not apply
● 11.2.4.5 (Open
Functionality
Software) – Does
not apply
● 11.2.4.5 (Closed
Software) – Does
not apply
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software) –
Does not apply to
non-web software
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs) – Does not
Supports Multiple ways are available to find
other pages on the site.

Page 39

Criteria Conformance
level
Remarks and explanations
apply to non-web
docs
2.4.6 Headings and Labels
(Level AA)
Also applies to:
EN 301 549 Criteria
● 9.2.4.6 (Web)
● 10.2.4.6 (Non-web
document)
● 11.2.4.6 (Open
Functionality
Software)
● 11.2.4.6 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Partially Supports Most headings and labels for form
and interactive controls are
informative.

The following exceptions exist:
● Multiple buttons have
identical programmatic labels
but different functionality, and
there is no programmatic
context, so people who are
blind and/or use a screen
reader will not know or may
be confused or misled about
what each button does. This
occurs on the following
pages: Review Changes and
Publish page; Add Fonts
modal.
● Multiple programmatic labels
for controls or form input
fields do not convey the
purpose of the control or
input, so people who are
blind and/or use a screen
reader may not understand
what a control does or what
data to enter. This occurs on
the following pages: Google
Drive Sidebar; Select Image
Modal; Copy Site Modal.

Page 40

Criteria Conformance
level
Remarks and explanations
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
● 9.2.4.7 (Web)
● 10.2.4.7 (Non-web
document)
● 11.2.4.7 (Open
Functionality
Software)
● 11.2.4.7 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Partially Supports In most cases, it is visually apparent
which page element is currently
receiving keyboard focus.

The following issues exist:
● Multiple interactive elements
(such as links, buttons, or
form inputs) do not have a
visual focus indicator, so
sighted people who use a
keyboard to navigate content
will not know when those
elements are receiving focus.
This occurs on the following
pages: Version History Page;
Select a File; Text Format
taskbar; Navigation Settings
modal.
3.1.2 Language of Parts
(Level AA)
Also applies to:
EN 301 549 Criteria
● 9.3.1.2 (Web)
● 10.3.1.2 (Non-web
document)
● 11.3.1.2 (Open
Functionality
Software) – Does
not apply
● 11.3.1.2 (Closed
Software) – Does
not apply
Supports The language of each section of
content that is different from the
default language of the page is
correctly identified and can be
determined programmatically.

Page 41

Criteria Conformance
level
Remarks and explanations
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
3.2.3 Consistent Navigation
(Level AA)
Also applies to:
EN 301 549 Criteria
● 9.3.2.3 (Web)
● 10.3.2.3 (Non-web
document) – Does
not apply
● 11.3.2.3 (Open
Functionality
Software) – Does
not apply
● 11.3.2.3 (Closed
Software) – Does
not apply
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software) –
Supports Navigation patterns that are repeated
on web pages are presented in the
same relative order each time they
appear and do not change order
when navigating through the site.

Page 42

Criteria Conformance
level
Remarks and explanations
Does not apply to
non-web software
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs) – Does not
apply to non-web
docs
3.2.4 Consistent Identification
(Level AA)
Also applies to:
EN 301 549 Criteria
● 9.3.2.4 (Web)
● 10.3.2.4 (Non-web
document) – Does
not apply
● 11.3.2.4 (Open
Functionality
Software) – Does
not apply
● 11.3.2.4 (Closed
Software) – Does
not apply
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software) –
Does not apply to
non-web software
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs) – Does not
Supports Labels, names, and text alternatives
for content that have the same
functionality across multiple web
pages are consistently identified.

Page 43

Criteria Conformance
level
Remarks and explanations
apply to non-web
docs
3.3.3 Error Suggestion (Level
AA)
Also applies to:
EN 301 549 Criteria
● 9.3.3.3 (Web)
● 10.3.3.3 (Non-web
document)
● 11.3.3.3 (Open
Functionality
Software)
● 11.3.3.3 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
Supports If input errors are automatically
detected, suggestions are provided
in text for correcting the input in a
timely and accessible manner before
the data is submitted to the server.
3.3.4 Error Prevention (Legal,
Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria
● 9.3.3.4 (Web)
● 10.3.3.4 (Non-web
document)
● 11.3.3.4 (Open
Functionality
Software)
Supports If the user can change or delete legal
transactions, financial transactions,
student exam responses, or data
transactions that are unrecoverable
or unintentionally modify or delete
data, the changes and/or deletions
are reversible, verified, or confirmed.

Page 44

Criteria Conformance
level
Remarks and explanations
● 11.3.3.4 (Closed
Software)
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508
● 501
(Web)(Software)
● 504.2 (Authoring
Tool)
● 602.3 (Support
Docs)
4.1.3 Status Messages (Level
AA 2.1 only)
Also applies to:
EN 301 549 Criteria
● 9.4.1.3 (Web)
● 10.4.1.3 (Non-web
document)
● 11.4.1.3 (Open
Functionality
Software)
● 11.4.1.3 (Closed
Software) – Does
not apply
● 11.8.2 (Authoring
Tool)
● 12.1.2 (Product
Docs)
● 12.2.4 (Support
Docs)
Revised Section 508 – Does
not apply
Partially Supports In most cases, status messages can
be programmatically determined and
presented by assistive technologies
without receiving focus.

The following exceptions exist:
● Some status messages are
not automatically announced
by the screen reader, so
people who are blind and/or
use a screen reader or other
assistive technology may
completely miss the status
messages or they may not
hear them in a timely fashion.
This occurs on the following
page: Title component; Add
Fonts modal; Edit Title
taskbar.

Page 45

Table 3: Success Criteria, Level AAA
Notes: Not evaluated
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
Criteria Conformance
level
Remarks and explanations
302.1 Without Vision Web: Partially
Supports
Web: Most functionality is usable without
vision.

Exceptions are noted in:
● 1.1.1 Non-Text Content
● 1.3.1 Info and Relationships
● 1.3.2 Meaningful Sequence
● 1.4.1 Use of Color
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels
● 3.2.1 On Focus
● 4.1.2 Name, Role, Value
302.2 With Limited Vision Web: Partially
Supports
Web: Most functionality is usable with
limited vision.

Exceptions are noted in:
● 1.1.1 Non-Text Content
● 1.3.1 Info and Relationships
● 1.3.2 Meaningful Sequence
● 1.4.1 Use of Color
● 1.4.3 Contrast (minimum)
● 1.4.4 Resize Text
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels
● 2.4.7 Focus Visible
● 3.2.1 On Focus
● 3.3.2 Labels or Instructions

Page 46

Criteria Conformance
level
Remarks and explanations
● 4.1.2 Name, Role, Value
302.3 Without Perception
of Color
Web: Partially
Supports
Web: Most functionality is usable without
perception of color.

Exceptions are noted in:
● 1.4.1 Use of Color
● 1.4.3 Contrast (minimum)
302.4 Without Hearing Web: Partially
Supports
Web: The product does not require the use
of hearing.
302.5 With Limited
Hearing
Web: Supports Web: The product does not require the use
of hearing.
302.6 Without Speech Web: Not
Applicable
Web: The product does not require the use
of speech.
302.7 With Limited
Manipulation
Web: Partially
Supports
Web: Most functionality is usable with
limited manipulation and does not require
fine motor control or simultaneous manual
operations.

Exceptions are noted in:
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels
● 2.4.7 Focus Visible
● 3.2.1 On Focus
● 4.1.2 Name, Role, Value
302.8 With Limited Reach
and Strength
Web: Supports Web: All functionality is usable with limited
reach and strength.
302.9 With Limited
Language, Cognitive, and
Learning Abilities
Web: Partially
Supports
Web: Most functionality is usable by
people with limited language, cognitive,
and learning abilities. People with cognitive
disabilities have varying needs for features

Page 47

Criteria Conformance
level
Remarks and explanations
that allow them to adapt content and work
with assistive technology.

Exceptions are noted in:
● 1.1.1 Non-Text Content
● 1.3.1 Info and Relationships
● 1.3.2 Meaningful Sequence
● 1.4.1 Use of Color
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels
● 2.4.7 Focus Visible
● 3.2.1 On Focus
● 3.3.2 Labels or Instructions
● 4.1.2 Name, Role, Value

Page 48

Chapter 4: Hardware
Notes: Not applicable. The product is not a hardware product.

Page 49

Chapter 5: Software
Notes: Google Sites is a web application, so its compliance with some of this chapter’s criteria is
dependent on the accessibility features available in the browser and operating system used to
access this application.
Criteria Conformance level Remarks and
explanations
501.1 Scope – Incorporation of
WCAG 2.0 AA
See WCAG 2.1
section
See information in
WCAG 2.1 section
502 Interoperability with Assistive
Technology
Heading cell – no
response required
Heading cell – no
response required
502.2.1 User Control of Accessibility
Features
Supports
502.2.2 No Disruption of Accessibility
Features
Supports
502.3 Accessibility Services
Heading cell – no
response required
Heading cell – no
response required
502.3.1 Object Information
Does Not Support The name, role,
and/or value of user
interface components
cannot be
programmatically
determined for many
of the elements.
502.3.2 Modification of Object
Information
Supports Most states and
properties that can
be set by the user
are capable of being
set programmatically,
including through
assistive technology.
502.3.3 Row, Column, and Headers
Partially Supports For most objects in
data tables, the
occupied rows and
columns, and any
headers associated
with those rows or
columns, are

Page 50

Criteria Conformance level Remarks and
explanations
programmatically
determinable.
502.3.4 Values
Partially Supports Most current values,
and any set or range
of allowable values
associated with an
object, are
programmatically
determinable.
502.3.5 Modification of Values
Supports Values that can be
set by the user are
capable of being set
programmatically,
including through
assistive technology.
502.3.6 Label Relationships
Partially Supports Most relationships
where a component
that has as a label for
another component,
or of being labeled by
another component,
are programmatically
determinable.
502.3.7 Hierarchical Relationships
Partially Supports Most hierarchical
(parent-child)
relationships that a
component has as a
container for, or
being contained by,
another component
are programmatically
determinable.
502.3.8 Text
Supports The content of text
objects, text
attributes, and the
boundary of text
rendered to the
screen, are

Page 51

Criteria Conformance level Remarks and
explanations
programmatically
determinable.
502.3.9 Modification of Text
Supports All text that can be
set by the user is
capable of being set
programmatically,
including through
assistive technology.
502.3.10 List of Actions
Supports For objects, a list of
all actions that can
be executed on that
object are
programmatically
determinable.
502.3.11 Actions on Objects
Supports The application
allows assistive
technology to
programmatically
execute all available
actions on objects.
502.3.12 Focus Cursor
Partially Supports The application
exposes information
and mechanisms
necessary to track
focus, text insertion
point, and selection
attributes of most
user interface
components.
502.3.13 Modification of Focus Cursor
Supports All focus, text
insertion point, and
selection attributes
that can be set by the
user can be set
programmatically,
including using
assistive technology.

Page 52

Criteria Conformance level Remarks and
explanations
502.3.14 Event Notification
Partially Supports Most automatic
updates and status
messages are
automatically
announced by
assistive
technologies.

502.4 Platform Accessibility Features
Supports The application does
not have
independent
accessibility features.
It utilizes the
accessibility features
of the browser and
operating system
used to access it.
503 Applications
Heading cell – no
response required
Heading cell – no
response required
503.2 User Preferences
Supports The application
permits user
preferences from
platform settings for
color, contrast, font
type, font size, and
focus cursor.
503.3 Alternative User Interfaces Not Applicable
503.4 User Controls for Captions
and Audio Description
Heading cell – no
response required
Heading cell – no
response required
503.4.1 Caption Controls Not Applicable
503.4.2 Audio Description Controls Not Applicable
504 Authoring Tools
Heading cell – no
response required
Heading cell – no
response required
504.2 Content Creation or Editing (if
not authoring tool, enter “not
applicable”)
Not Applicable

Page 53

Criteria Conformance level Remarks and
explanations
504.2.1 Preservation of Information
Provided for Accessibility in Format
Conversion
Not Applicable
504.2.2 PDF Export Not Applicable
504.3 Prompts Not Applicable
504.4 Templates Not Applicable


Chapter 6: Support Documentation and Services
Notes: Not evaluated. Pending evaluation of the shared documentation website and shared
support services for Google products.
Criteria Conformance
level
Remarks and explanations
601.1 Scope
602 Support
Documentation

602.2 Accessibility and
Compatibility Features
Not Applicable

Support documentation for this product
exists but is verified in another Accessibility
Conformance Report.
602.3 Electronic Support
Documentation
Not applicable

Support documentation for this product
exists but is verified in another Accessibility
Conformance Report.
602.4 Alternate Formats
for Non-Electronic Support
Documentation
Not applicable

Page 54

Criteria Conformance
level
Remarks and explanations
603 Support Services
603.2 Information on
Accessibility and
Compatibility Features
Not applicable
603.3 Accommodation of
Communication Needs
Not applicable
EN 301 549 Report
Chapter 4: Functional Performance Statements (FPS)
Criteria Conformance
Level
Remarks and Explanations
4.2.1 Usage without
vision
Web: Partially
Supports
Web: Most functionality is usable without
vision.

Exceptions are noted in:
● 1.1.1 Non-Text Content
● 1.3.1 Info and Relationships
● 1.3.2 Meaningful Sequence
● 1.4.1 Use of Color
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels
● 3.2.1 On Focus
● 4.1.2 Name, Role, Value
● 4.1.3 Status Messages
4.2.2 Usage with limited
vision
Web: Partially
Supports
Web: Most functionality is usable with
limited vision.

Exceptions are noted in:
● 1.1.1 Non-Text Content
● 1.3.1 Info and Relationships

Page 55

Criteria Conformance
Level
Remarks and Explanations
● 1.3.2 Meaningful Sequence
● 1.4.1 Use of Color
● 1.4.3 Contrast (minimum)
● 1.4.4 Resize Text
● 1.4.10 Non-Text Contrast
● 1.4.11 Non-Text Contrast
● 1.4.12 Text Spacing
● 1.4.13 Content on Hover or Focus
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels
● 2.4.7 Focus Visible
● 3.2.1 On Focus
● 3.3.2 Labels or Instructions
● 4.1.2 Name, Role, Value
4.2.3 Usage without
perception of colour
Web: Partially
Supports
Web: Most functionality is usable without
perception of color.

Exceptions are noted in:
● 1.4.1 Use of Color
● 1.4.3 Contrast (minimum)
● 1.4.11 Non-Text Contrast
4.2.4 Usage without
hearing
Web: Supports Web: The product does not require the use
of hearing.
4.2.5 Usage with limited
hearing
Web: Supports Web: The product does not require the use
of hearing.
4.2.6 Usage without vocal
capability
Web: Not
Applicable
Web: The product does not require the use
of speech or other vocal output.
4.2.7 Usage with limited
manipulation or strength
Web: Partially
Supports
Web: Most functionality is usable by
people with limited manipulation and does
not require manipulation, simultaneous
action, or hand strength.

Exceptions are noted in:
● 1.3.5 Identify Input Purpose
● 1.4.13 Content on Hover or Focus
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels

Page 56

Criteria Conformance
Level
Remarks and Explanations
● 2.4.7 Focus Visible
● 2.5.2 Pointer Cancellation
● 2.5.3 Label in Name
● 3.2.1 On Focus
● 4.1.2 Name, Role, Value
4.2.8 Usage with limited
reach
Web: Supports Web: All functionality is usable by people
with limited reach.
4.2.9 Minimize
photosensitive seizure
triggers
Web: Supports Web: All functionality may be operated in a
mode that minimizes the potential for
triggering photosensitive seizures.
4.2.10 Usage with limited
cognition
Web: Partially
Supports
Web: Most functionality is usable by
people with limited language, cognitive,
and learning abilities. People with cognitive
disabilities have varying needs for features
that allow them to adapt content and work
with assistive technology.

Exceptions are noted in:
● 1.1.1 Non-Text Content
● 1.3.1 Info and Relationships
● 1.3.2 Meaningful Sequence
● 1.3.5 Identify Input Purpose
● 1.4.1 Use of Color
● 1.4.10 Non-Text Contrast
● 1.4.12 Text Spacing
● 1.4.13 Content on Hover or Focus
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels
● 2.4.7 Focus Visible
● 2.5.2 Pointer Cancellation
● 2.5.3 Label in Name
● 3.2.1 On Focus
● 3.3.2 Labels or Instructions
● 4.1.2 Name, Role, Value
● 4.1.3 Status Messages
4.2.11 Privacy Web: Partially
Supports
Web: Most functionality is usable without
vision.

Exceptions are noted in:

Page 57

Criteria Conformance
Level
Remarks and Explanations
● 1.1.1 Non-Text Content
● 1.3.1 Info and Relationships
● 1.3.2 Meaningful Sequence
● 1.4.1 Use of Color
● 2.1.1 Keyboard
● 2.4.3 Focus Order
● 2.4.6 Headings and Labels
● 3.2.1 On Focus
● 4.1.2 Name, Role, Value
● 4.1.3 Status Messages

Page 58

Chapter 5: Generic Requirements
Criteria Conformance
Level
Remarks and Explanations
5.1 Closed functionality Heading cell – no
response
required
Heading cell – no response required
5.1.2 General Heading cell – no
response
required
Heading cell – no response required
5.1.2.1 Closed
functionality
See 5.2 through
13
See information in 5.2 through 13
5.1.2.2 Assistive
technology
See 5.1.3 through
5.1.6
See information in 5.1.3 through 5.1.6
5.1.3 Non-visual access Heading cell – no
response
required
Heading cell – no response required
5.1.3.1 General Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.2 Auditory output
delivery including speech
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.3 Auditory output
correlation
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.4 Speech output
user control
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.

Page 59

Criteria Conformance
Level
Remarks and Explanations
5.1.3.5 Speech output
automatic interruption
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.6 Speech output for
non-text content
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.7 Speech output for
video information
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.8 Masked entry Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.9 Private access to
personal data
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.10 Non-interfering
audio output
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.11 Private listening Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.12 Speaker volume Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.

Page 60

Criteria Conformance
Level
Remarks and Explanations
5.1.3.13 Volume reset Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.14 Spoken
languages
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.15 Non-visual error
identification
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.3.16 Receipts, tickets,
and transactional outputs
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from attaching, installing, or using
assistive technology.
5.1.4 Functionality closed
to text enlargement
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from enlarging text.
5.1.5 Visual output for
auditory information
Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.1.5 Visual output for auditory
information.
5.1.6 Operation without
keyboard interface
Heading cell – no
response
required
Heading cell – no response required
5.1.6.1 Closed
functionality
Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from operating a keyboard interface.

Page 61

Criteria Conformance
Level
Remarks and Explanations
5.1.6.2 Input focus Not applicable The product does not contain functionality
limited by characteristics that prevent a
user from operating a keyboard interface.
5.2 Activation of
accessibility features
Not applicable The product does not have specific
documented accessibility features.
5.3 Biometrics Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.3 Biometrics.
5.4 Preservation of
accessibility information
during conversion
Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.4 Preservation of accessibility
information during conversion.
5.5 Operable parts Heading cell – no
response
required
Heading cell – no response required
5.5.1 Means of operation Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.5 Operable parts – 5.5.1
Means of operation.
5.5.2 Operable parts
discernibility
Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.5 Operable parts – 5.5.1
Means of operation.
5.6 Locking or toggle
controls
Heading cell – no
response
required
Heading cell – no response required
5.6.1 Tactile or auditory
status
Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.6 Locking or toggle controls –
5.6.1 Tactile or auditory status.

Page 62

Criteria Conformance
Level
Remarks and Explanations
5.6.2 Visual status Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.6 Locking or toggle controls –
5.6.2 Visual status.
5.7 Key repeat Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.7 Key repeat.
5.8 Double-strike key
acceptance
Not applicable The criterion is not relevant to the product.
The product does not have a feature
relevant to 5.8 Double-strike key
acceptance.
5.9 Simultaneous user
actions
Supports The product does not require simultaneous
user actions. The product is compatible
with system settings for sequential key
presses, such as Sticky Keys.

Page 63

Chapter 6: ICT with Two-Way Voice Communication
Notes: Not applicable. The product does not contain functionality relating to, nor does it
require/rely on, two-way voice communication.

Page 64

Chapter 7: ICT with Video Capabilities
Notes: Not Applicable. This product does not contain any multimedia.

Page 65

Chapter 8: Hardware
Notes: Not applicable. The product is not a hardware product.

Page 66

Chapter 9: Web
See the WCAG 2.1 Report section.

Page 67

Chapter 10: Non-Web Documents
Notes: Not applicable. The product does not include non-web documents.

Page 68

Chapter 11: Software
Notes:
Criteria Conformance
Level
Remarks and Explanations
11.0 General
(informative)
Heading cell –
no response
required
Heading cell – no response required
11.1.1.1 through
11.4.1.3
See WCAG 2.1
section
See information in WCAG 2.1 section
11.5 Interoperability
with assistive
technology
Heading cell –
no response
required
Heading cell – no response required
11.5.1 Closed
functionality
Heading cell –
no response
required
Heading cell – no response required
11.5.2 Accessibility
services
Heading cell –
no response
required
Heading cell – no response required
11.5.2.1 Platform
accessibility service
support for software
that provides a user
interface
See 11.5.2.5
through
11.5.2.17
See information in 11.5.2.5 through
11.5.2.17

Page 69

Criteria Conformance
Level
Remarks and Explanations
11.5.2.2 Platform
accessibility service
support for assistive
technologies
See 11.5.2.5
through
11.5.2.17
See information in 11.5.2.5 through
11.5.2.17
11.5.2.3 Use of
accessibility services
Supports The browser accessibility services are
used.
11.5.2.4 Assistive
technology
Not Applicable
11.5.2.5 Object
information
Does Not
Support
The name, role, and/or value of many
user interface components cannot be
programmatically determined.
11.5.2.6 Row, column,
and headers
Partially
Supports
For most objects in data tables, the
occupied rows and columns, and any
headers associated with those rows or
columns, are programmatically
determinable.
11.5.2.7 Values Partially
Supports
The value of most interface
components can be programmatically
determined.
11.5.2.8 Label
relationships
Does Not
Support
The name of many interface
components cannot be
programmatically determined or are
incorrect.

Page 70

Criteria Conformance
Level
Remarks and Explanations
11.5.2.9 Parent-child
relationships
Partially
Supports
Most hierarchical (parent-child)
relationships that a component has as a
container for, or being contained by,
another component are
programmatically determinable.
11.5.2.10 Text Supports All text that can be set by the user is
capable of being set programmatically,
including through assistive technology.
11.5.2.11 List of
available actions
Supports For objects, a list of all actions that can
be executed on that object are
programmatically determinable.
11.5.2.12 Execution of
available actions
Supports The application allows assistive
technology to programmatically execute
all available actions on objects.
11.5.2.13 Tracking of
focus and selection
attributes
Partially
Supports
The application exposes information
and mechanisms necessary to track
focus, text insertion point, and selection
attributes of most user interface
components.
11.5.2.14 Modification
of focus and selection
attributes
Supports All focus, text insertion point, and
selection attributes that can be set by
the user can be set programmatically,
including using assistive technology.

Page 71

Criteria Conformance
Level
Remarks and Explanations
11.5.2.15 Change
notification
Partially
Supports
Most change notifications are
automatically announced by assistive
technologies.

11.5.2.16 Modifications
of states and properties
Supports The states and properties of user
interface elements can be
programmatically modified by assistive
technologies.
11.5.2.17 Modifications
of values and text
Supports The values and text of user interface
elements can be programmatically
modified by assistive technologies
using the input methods of the platform
(the browser).
11.6 Documented
accessibility usage
Heading cell –
no response
required
Heading cell – no response required
11.6.1 User control of
accessibility features
Not Applicable
11.6.2 No disruption of
accessibility features
Not Applicable
11.7 User preferences Does Not
Support
User preferences are not followed from
the platform (the browser).

Page 72

Criteria Conformance
Level
Remarks and Explanations
11.8 Authoring tools Heading cell –
no response
required
Heading cell – no response required
11.8.1 Content
technology
Heading cell –
no response
required
Heading cell – no response required
11.8.2 Accessible
content creation
See WCAG 2.1
section
See information in WCAG 2.1 section
11.8.3 Preservation of
accessibility information
in transformations
Supports Accessibility information is preserved in
the content after restructuring
transformations or re-coding
transformations.
11.8.4 Repair
assistance
Not Applicable
11.8.5 Templates Does Not
Support
The requirement of at least one
template identified as conforming to the
requirements of clause 9 (Web) is not
met.

Page 73

Chapter 12: Documentation and Support Services
Notes: Not evaluated. Pending evaluation of the shared documentation website and shared
support services for Google Sites products.
Criteria Conformance
Level
Remarks and Explanations
12.1 Product
documentation
Heading cell – no
response required
Heading cell – no response required
12.1.1 Accessibility and
compatibility features
Not Applicable Support documentation for this product
exists but is verified in another Accessibility
Conformance Report.
12.1.2 Accessible
documentation
Not applicable Support documentation for this product
exists but is verified in another Accessibility
Conformance Report.
12.2 Support Services Heading cell – no
response required
Heading cell – no response required
12.2.2 Information on
accessibility and
compatibility features
Not applicable
12.2.3 Effective
communication
Not applicable
12.2.4 Accessible
documentation
Not applicable

Page 74

Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not applicable. The product does not provide relay or emergency service access.
Legal disclaimer
© 2024 Google LLC. As of the date of its publication indicated in the information table at the
beginning of this Conformance Report, this Conformance Report represents the current view of
Google regarding information about the subject Google product as outlined in the ITI’s “VPAT®
International Edition Version 2.4Rev.” Google cannot guarantee that any information in this
Conformance Report will remain accurate after such date of publication, but Google works
continuously to monitor the accessibility of its products and provide updates from time to time.
Any modification or customization to the subject product may render some or all of this
Conformance Report to become inapplicable. This Conformance Report is provided “as is” and
for informational purposes only.