Google Accessibility Conformance Report - VPAT Version 2.5 Rev1 - 4 October 2024 - Google Apps Script

Sep 11, 2026

Upload by Jacob

Accessibility Conformance Report prepared for Google Apps Script under VPAT® Version 2.5 Rev1 for the international edition, dated 4 October 2024. Evaluation follows the W3C WCAG-EM approach using manual testing, automated accessibility tools, and assistive technology across browser platforms, including Chrome and NVDA, with Axe tools and contrast analysis. The report documents conformance levels across WCAG 2.0/2.1 (Level A/AA), Revised Section 508, and EN 301 549, with detailed success criteria tables and referenced exceptions.

LanguageEnglish

CategoryForms

FormatPDF

Pages64

Reading Time22 min

AccessFree to download

Terms

Conformance level definitions

WCAG 2.1 Report

Table 1: Success Criteria, Level A

Table 2: Success Criteria, Level AA

Table 3: Success Criteria, Level AAA

Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Chapter 4: Hardware

Chapter 5: Software

Chapter 6: Support Documentation and Services

EN 301 549 Report

Chapter 4: Functional Performance Statements (FPS)

Chapter 5: Generic Requirements

Chapter 6: ICT with Two-Way Voice Communication

Chapter 7: ICT with Video Capabilities

Chapter 8: Hardware

Chapter 9: Web

Chapter 10: Non-Web Documents

Chapter 11: Software

Chapter 12: Documentation and Support Services

Chapter 13: ICT Providing Relay or Emergency Service Access

Tested Pages

File

Context & Set Up

Run A Function

Debug a function

Deploy Apps Script project

Tested Components that appear on multiple pages

Header

Left Navigation

Legal disclaimer

Google Accessibility Conformance Report International edition, based on VPAT® Version 2.5 Rev1 | Name of product/version: | Google Apps Script | | --- | --- | | Report date: | 4 October 2024 | | Product description: | Google Apps Script is a web-based scripting platform that allows users to create, customize, and automate Google Workspace applications. | | Contact information: | [vpat-questions@google.com](vpat-questions@google.com) | | 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 browser platforms.
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: Axe Auditor, Axe Dev tools Pro and Color Contrast Analyzer | | 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 | 1 “Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI) | | Accessibility requirements for ICT products and services-V3.2.1 (2021-03) | | --- | --- | Table of contents Google Accessibility Conformance Report 1 Table of contents 3 Terms 3 WCAG 2.1 Report 5 Table 1 : Success Criteria, Level A 5 Table 2: Success Criteria, Level AA 27 Table 3 : Success Criteria, Level AAA 42 Revised Section 508 Report 43 Chapter 3 : Functional Performance Criteria ( FPC) 43 Chapter 4: Hardware 45 Chapter 5 : Software 46 Chapter 6 : Support Documentation and Services 50 EN 301 549 Report 52 Chapter 4: Functional Performance Statements ( FPS) 52 Chapter 5 : Generic Requirements 55 Chapter 6 : ICT with Two-Way Voice Communication 60 Chapter 7: ICT with Video Capabilities 61 Chapter 8 : Hardware 62 Chapter 9 : Web 63 Chapter 10 : Non-Web Documents 64 Chapter 11: Software 64 Chapter 12: Documentation and Support Services 65 Chapter 13 : ICT Providing Relay or Emergency Service Access 66 Legal disclaimer 67 Tested Pages ● File ● Context & Set Up ● Run A Function ● Accept an autocomplete suggestion ● Accept hints from the Monaco editor ● Set up a breakpoint on a line of code ● Debug a function ● Step through a function ● Add a trigger to run my code ● Add a library to my project ● Add a Google Workspace service to my project ● View the error rate and executions of different deployments ● View execution logs within Apps Script ● Add a file to the project Page 3 ● Deploy Apps Script project Tested Components that appear on multiple pages ● Header ● Left Navigation 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. 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, Section

FAQs

What accessibility standards are covered in the report for Google Apps Script?

The report covers WCAG 2.0 and WCAG 2.1 (Level A and AA), Revised Section 508, and EN 301 549. It also aligns WCAG success criteria with specific EN 301 549 and Section 508 chapters where applicable.

How was the accessibility evaluation performed?

The audit followed the W3C Website Accessibility Conformance Evaluation Methodology (WCAG-EM). Testing included manual checks, automated accessibility tools, and assistive technology across browser platforms, including Chrome with NVDA and tools such as Axe Auditor and Axe DevTools Pro.

What do the conformance level terms mean in the report?

Supports means the product meets the criterion with no known defects or equivalent facilitation. Partially supports indicates some functionality does not meet the criterion, while Does not support means most functionality does not meet it. Not applicable means the criterion is not relevant, and Not evaluated applies only to certain WCAG Level AAA criteria.

Sep 11, 2026

Upload by Jacob