GitLab Accessibility Conformance Report International Edition

About your company

https://gitlab.com/users/sign_up/company/new?jobs_to_be_done_other=&registration_objective=ci&role=devops_engineer

Access Token

[url]/-/user_settings/personal_access_tokens

Account

[url]/-/profile/account

Activity - All Tab

[url]/demo-group/project-1/activity

Add new Access token

[url]/demo-group/project-1/-/settings/access_tokens

Admin Dashboard

[url]/admin

Background - Corn

[url]/admin/background_jobs

Background jobs - Dashboard

[url]/admin/background_jobs

Billing

https://gitlab.com/-/profile/billings

Branches

[url]/demo-group/project-1/-/branches

Bulk Edit

[url]/demo-group/project-1/-/issues

CI/CD Analytics

[url]/demo-group/project-1/-/pipelines/charts

Commits

[url]/demo-group/project-1/-/commits/master?ref_type=heads

Compare revisions

[url]/demo-group/project-1/-/compare/master..master

Configure feature flags dialog

[url]/demo-group/project-1/-/feature_flags

Container Registry

[url]/demo-group/project-3/container_registry?orderBy=UPDATED&sort=asc

Create a blank Project

[url]/projects/new#blank_project

Create a Cluster

[url]/demo-group/project-1/-/clusters/new_cluster_docs

Create or import your first project

https://gitlab.com/users/sign_up/groups/new

Dashboard

[url]/

Dependencies

[url]/demo-group/project-1/-/dependencies

DevOps Reports

[url]/admin/dev_ops_reports

Edit Profile

[url]/-/user_settings/profile

Email address

[url]/-/profile/emails

Environments

[url]/demo-group/project-1/-/environments

Explore Projects

[url]/explore/projects?archived=true

Explore snippets

[url]/explore/snippets

Explore Topics

[url]/explore/projects/topics

Feature Flags

[url]/demo-group/project-1/-/feature_flags

General

[url]/demo-group/project-1/edit

Get started with GitLab Pages

https://gitlab.com/demo/Test/pages/new

GitLab Duo Chat

[url]/demo-group/crtest/container_registry

GitLab is better with colleagues!' dialog

https://gitlab.com/test5482950/test/-/learn_gitlab

Give feedback

[url]/demo-group/crtest/container_registry

Google Cloud

https://gitlab.com/demo/Test/-/google_cloud/configuration

Groups

[url]/dashboard/groups

Help Flyout

[url]/demo-group/project-1/-/ci/editor?branch_name=master

Instance subscription

[url]/admin/subscription

Integrations

[url]/demo-group/project-1/-/settings/integrations

Issue Boards

[url]/demo-group/project-1/-/boards

Issue details

[url]/demo-group/project-1/-/issues/60

Issues list

[url]/demo-group/project-1/-/issues

Job Details

[url]/demo-group/project-1/-/jobs/84

Jobs - All

[url]/admin/jobs

Keyboard Shortcuts dialog

[url]/

Kubernetes Cluster

[url]/demo-group/project-1/-/clusters

Labels - All tab

[url]/demo-group/project-1/-/labels

Learn Git Lab

https://gitlab.com/tech3171450/test-1/-/learn_gitlab

Login

[url]/

Members

[url]/demo-group/project-1/-/project_members

Merge requests details - Changes tab

[url]/demo-group/project-1/-/merge_requests/12/diffs

Merge requests details - Overview tab

[url]/demo-group/project-1/-/merge_requests/12

Merge requests details - Pipelines tab

[url]/demo-group/project-1/-/merge_requests/12/pipelines

Merge requests details -Commits tab

[url]/demo-group/project-1/-/merge_requests/12/commits

Merge requests list - All tab

[url]/demo-group/project-1/-/merge_requests?scope=all&state=all

Merger Request

[url]/demo-group/project-1/-/settings/merge_requests

Milestones

[url]/demo-group/project-1/-/milestones

Monitor Settings

[url]/demo-group/project-1/-/settings/operations

New Feature Flag

[url]/demo-group/project-1/-/feature_flags/new

New issue

[url]/demo-group/project-1/-/issues/new

New Label

[url]/demo-group/project-1/-/labels/new

New Merge Request

[url]/demo-group/project-1/-/merge_requests/new

New project

[url]/projects/new

New Tag

[url]/demo-group/project-1/-/tags/new

New value stream dialog

[url]/demo-group/project-1/-/value_stream_analytics

Notifications

[url]/-/profile/notifications

Pipe Line Editor

[url]/demo-group/project-1/-/ci/editor?branch_name=master

Pipeline

[url]/demo-group/project-1/-/pipelines

Pipelines details

[url]/demo-group/project-3/-/pipelines/3

Policies

[url]/demo-group/project-1/-/security/policies

Preferences

[url]/-/profile/preferences

Profile

[url]/root

Project audit events

[url]/demo-group/project-1/-/audit_events

Project Overview

[url]/demo-group/test-wcag/-/tree/main

Projects Details

[url]/demo-group/project-1

Releases

[url]/demo-group/project-1/-/releases

Repository

[url]/demo-group/project-1/-/tree/master

Repository Analytics

[url]/demo-group/project-1/-/graphs/master/charts

Repository Graph

[url]/demo-group/project-1/-/network/master?ref_type=heads

Run Pipe Line

[url]/demo-group/project-1/-/pipelines/new

Schedule new pipeline

[url]/demo-group/project-1/-/pipeline_schedules/new

Security configuration

[url]/demo-group/project-3/-/security/configuration

Security dashboard

[url]/demo-group/project-1/-/security/dashboard

Start your Free Ultimate Trial

https://gitlab.com/-/trial_registrations/new

Terraform init command dialog

[url]/demo-group/project-1/-/terraform

Usage Quotas

[url]/-/profile/usage_quotas

Usage Quotas

[url]/demo-group/project-1/-/usage_quotas

Users

[url]/admin/users

Value Stream Analytics

[url]/demo-group/project-1/-/value_stream_analytics

Verify Screen

https://gitlab.com/users/identity_verification

Vulnerability report

[url]/demo-group/project-1/-/security/vulnerability_report

Web Hooks

[url]/demo-group/project-1/-/hooks

Welcome page

NA

What's new flyout

[url]/demo-group/project-1/-/ci/editor?branch_name=master

Security Capabilities

[url]/demo-user/project-1/-/security/discover

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)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Partially Supports

Web: Most non-text content has text alternatives or a text alternate that serves an equivalent purpose. The following exceptions exist:

• A complex image does not have a long description to convey the information presented by the image, so people who are blind and/or use a screen reader will not be able to understand the information presented by the image. This occurs on the following page(s): Repository Graph; Background jobs - Dashboard; Repository Analytics.
• A decorative image is not hidden from screen readers, so people who are blind and/or use a screen reader will have to navigate through unnecessary and duplicative text. This occurs on the following page(s): Vulnerability report; Dependencies.
• An image has a text alternative that is different than what the image represents, so people who are blind and/or use a screen reader will be given different information than sighted users. This occurs on the following page(s): Dashboard.
• A complex image has a short text alternative that is not meaningful, so people who are blind and/or use a screen reader may not be able to understand the information available in the image. This occurs on the following page(s): Background jobs - Dashboard; Repository Analytics.
• A complex image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to understand the information available in the image. This occurs on the following page(s): Security dashboard; CI/CD Analytics.
• Text alternative for the informative image is missing. This occurs on the following page(s): Background jobs - Dashboard; Instance subscription.
• Known instances are tracked in the &564 epic and will continue to be addressed.

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)

Web: Not Applicable

Web: 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)
• 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)

Web: Not Applicable

Web: Prerecorded videos are not present.

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

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Not Applicable

Web: Prerecorded videos are not present, so audio description is not required.

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)
• 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)

Web: Does Not Support

Web: Most, if not all, information, structure, and relationships conveyed through presentation cannot be programmatically determined or are not available in text. The following issues exist:

• A group of form controls is not programmatically associated with their group label, so the purpose of individual controls in the group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following page(s): Notifications; Preferences; Compare revisions; Integrations; General; Pipelines details; Create a Cluster.
• A heading level is out of order, 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 page(s): Users; Profile; Notifications; GitLab Duo Chat; Issue Boards; Repository; Learn Git Lab; Add new Access token; Environments; Email address; CI/CD Analytics; Merger Request; Value Stream Analytics; Instance subscription; Monitor Settings; Access Token; Project audit events; Feature Flags.
• Content that is visually presented as a list is not properly marked up as a list, so the structure of the list is not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page(s): Search and Filter; Merge requests details - Overview tab; Sidebar; Merge requests details -Commits tab; Milestones.
• A block of text is marked up as a heading but is not a heading, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page(s): Issue Boards; Compare revisions; Add new Access token; Background jobs - Dashboard; CI/CD Analytics; Merger Request; General; Date Picker; Repository Analytics; Container Registry; Admin Dashboard; Explore Topics; Groups; Policies; Usage Quotas; Dependencies; Account.
• Text that visually functions as a heading is not 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 page(s): Preferences; GitLab Duo Chat; Issues list; Edit Profile; Search and Filter; Project Overview; Merge requests details - Overview tab; Repository Analytics; Pipelines details.
• Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page(s): Search and Filter; DevOps Reports; Projects Details; Keyboard Shortcuts dialog.
• Data is arranged visually like a data table, but the programmatic table header markup is missing or incomplete. People who are blind and/or use a screen reader will not be aware of the association between the table headers and their related data. This occurs on the following page(s): Google Cloud.
• Content that does not visually function as a list is marked up as a list, so the structure of the page is misrepresented to and people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page(s): Repository; Merge requests details - Overview tab.
• A block of content has incorrect semantic markup, so its meaning, structure, or relationships is not conveyed to people who are blind and/or use a screen reader. This occurs on the following page(s): Background - Corn.
• One or more data cells is incorrectly marked up as a header cell in a table, so the table structure and the header/data relationship between the cell(s) and other cells in the table will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following page(s): Vulnerability report.
• An element's programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content. This occurs on the following page(s): Environments; Kubernetes Cluster.
• An HTML list element contains content that is visually presented as a part of the list, but the content's HTML coding does not include it programmatically in that list, so the structure of the list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page(s): Issue Boards; Issues list; Milestones.
• Content that is visually presented as a list is not properly marked up as a list, so the structure of the list is not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page(s): Issue Boards; Labels - All tab; Merge requests details - Overview tab.
• Group of radio buttons not associated with group label. This occurs on the following page(s): Preferences; Issue Boards; Issue details; Merger Request; Create or import your first project; Schedule new pipeline; Welcome page; Create a blank Project.
• Group of checkboxes not associated with group label. This occurs on the following page(s): Add new Access token; Merger Request; Create a blank Project.
• Known instances are tracked in the &567 epic and will continue to be addressed.

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)
• 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)

Web: Partially Supports

Web: The reading and navigation order of most content is logical and intuitive. The following exceptions exist:

• Screen readers can read content outside the modal dialog, so people who are blind and/or use a screen reader may become disoriented or confused. This occurs on the following page(s): What's new flyout.
• 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(s): Merge requests details - Changes tab; Issue details; General; Monitor Settings; Start your Free Ultimate Trial; Get started with GitLab Pages.
• The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, 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 page(s): Releases; Rich text editor; Merge requests details - Changes tab; Container Registry.
• The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following page(s): Issue Boards; Merge requests details - Overview tab.
• The correct reading order of dynamically changing content is not programmatically determinable by screen readers, so people who are blind and/or use a screen reader may not be made aware of new or changed content that is dynamically added to a page. This occurs on the following page(s): Billing.
• Screen reader focus is lost or misplaced due to user interaction or content update, making navigation difficult or impossible for people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page(s): New value stream dialog.

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)

Web: Supports

Web: Instructions to operate and/or understand content do not rely on sensory characteristics of components such as shape, color, size, and visual location.

1.4.1 Use of Color (Level A)

Also applies to:

EN 301 549 Criteria

• 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)

Web: Does Not Support

Web: For most if not all content, color is the only method used to convey information, indicate an action, prompt a response, or distinguish visual elements. The following issues 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 page(s): Profile; Security dashboard; CI/CD Analytics; Value Stream Analytics.
• Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify the link. This occurs on the following page(s): Pipe Line Editor; Issue details; Environments; Kubernetes Cluster; Project Overview; Merge requests details - Overview tab; General; Create or import your first project; Projects Details; Monitor Settings; Activity - All Tab; Policies; Configure feature flags dialog; Account; Verify Screen; Help Flyout; Terraform init command dialog.
• Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of a control, 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 page(s): Users; Issue Boards; Vulnerability report; Branches; Search and Filter; Create or import your first project; Create a Cluster; Project audit events; Members.
• Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify the link. This occurs on the following page(s): Login; GitLab Duo Chat; Pipe Line Editor; Jobs - All; Vulnerability report; Compare revisions; Run Pipe Line; Releases; Repository; Security configuration; Background - Corn; Edit Profile; Security dashboard; Learn Git Lab; Add new Access token; Issue details; Environments; GitLab is better with colleagues!' dialog; Integrations; DevOps Reports; New issue; Project Overview; Background jobs - Dashboard; Merge requests details - Overview tab; Email address; Merger Request; General; Container Registry; Admin Dashboard; Instance subscription; Monitor Settings; Web Hooks; Start your Free Ultimate Trial; Access Token; New Tag; Keyboard Shortcuts dialog; Billing; Usage Quotas; Create a Cluster; New Label; Dependencies; Create a blank Project; New project; Feature Flags; Security Capabilities; Help Flyout.
• Known instances are tracked in the #2694 issue.

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)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Not Applicable

Web: The tested application does not contain audio content that plays automatically for more than 3 seconds.

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)

Web: Partially Supports

Web: 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 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:

• An action cannot be performed when using a screen reader, so people who are blind and others who use a screen reader cannot perform this action. This occurs on the following page(s): Date Picker.
• A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. This occurs on the following page(s): Users; Profile; Issue Boards; Pipe Line Editor; Issues list; Repository Graph; Rich text editor; Merge requests details - Changes tab; Security dashboard; Issue details; Labels - All tab; Background jobs - Dashboard; Merge requests details - Overview tab; CI/CD Analytics; Value Stream Analytics; Date Picker; Repository Analytics; Container Registry; Groups; Merge requests list - All tab; Sidebar; Dependencies.
• The content in a scrollable region cannot be accessed using a keyboard, so people who use a keyboard to navigate will not be able to view this content. This occurs on the following page(s): Repository Graph.
• Know instances are tracked in the &565 epic.

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)
• 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)

Web: Supports

Web: 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.

• Known instances where a user cannot navigate away from focused file editors are tracked in the &627 epic.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

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

Web: Partially Supports

Web: In most cases when 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. The following exceptions exist:

• Single character key shortcuts exist and cannot be modified or turned off, so people who use the keyboard or speech input to navigate and operate content may accidentally trigger a command. This occurs on the following page(s): Project wide.

2.2.1 Timing Adjustable (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.2.1 (Web)
• 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)

Web: Partially Supports

Web: In most cases when a time limit exists, the user is given an option to turn off, adjust, or extend the time limit. The following exceptions exist:

• Some content visually appears and disappears with no ability to adjust how long the content is visible, potentially preventing people who are blind, have low vision, or have mobility or cognitive disabilities from locating or reading the content. This occurs on the following page(s): Preferences; Job Details; Issue details; About your company.

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)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Partially Supports

Web: On most pages where moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user. The following exceptions exist:

• The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following page(s): What's new flyout; Background jobs - Dashboard.

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)

Web: Not Applicable

Web: 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
• 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

Web: Supports

Web: A method is provided to skip navigation and other page elements that are repeated across web pages.

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

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Partially Supports

Web: Most pages have descriptive and informative titles. The following exceptions exist:

• Page TITLE element does not identify purpose of page. This occurs on the following page(s): Environments; Create or import your first project; About your company; Welcome page; Create a blank Project.

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)

Web: Partially Supports

Web: 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 or touch screen swiping goes to an element that is hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following page(s): Merge requests details - Changes tab; Issue details; New issue; General; Monitor Settings; Get started with GitLab Pages.
• Keyboard focus does not follow the visual focus order, or it does not move to the intended target, so people who use the keyboard to navigate content (including screen reader users) may become disoriented on the page. This occurs on the following page(s): Get started with GitLab Pages; Help Flyout.
• Keyboard focus is not confined within a modal, so people who use the keyboard to navigate content (including screen reader users) will be able to navigate outside of the modal, which may cause them to become disoriented. This occurs on the following page(s): What's new flyout.
• The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs on the following page(s): Pipe Line Editor; Container Registry; Get started with GitLab Pages.
• When a modal closes, keyboard focus is not returned to the control that opened the modal or to another logical location, so people who use the keyboard to navigate content (including screen reader users) may become disoriented on the page. This occurs on the following page(s): New value stream dialog; What's new flyout; Help Flyout.

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)
• 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)

Web: Partially Supports

Web: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. The following exceptions exist:

• The purpose of the link is not made clear by its text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where the link goes. This occurs on the following page(s): Dashboard; Preferences; Job Details; Vulnerability report; Environments; New issue; Merge requests details - Overview tab; CI/CD Analytics; Admin Dashboard; Explore Topics; Projects Details.
• Known instances of unclear product links are tracked in the &620 epic.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

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

Web: Supports

Web: 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 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.2.5.2 (Web)
• 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

Web: Supports

Web: For 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.
• 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.

2.5.3 Label in Name (Level A 2.1 and 2.2)

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)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Web: 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(s): Notifications; Dashboard; Vulnerability report; New Feature Flag; New value stream dialog; Edit Profile; Issue details; New issue; General; Value Stream Analytics; Create or import your first project; Schedule new pipeline; New Tag; Policies; Usage Quotas; Get started with GitLab Pages; Project audit events; Members.
• An interactive element (such as a link, button, or form input) does not have an 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(s): Preferences; Background - Corn; Issue details; GitLab is better with colleagues!' dialog; New issue; Bulk Edit; Background jobs - Dashboard; Merger Request; General; Create or import your first project; Get started with GitLab Pages.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

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

Web: Supports

Web: 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)
• 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)

Web: Partially Supports

Web: On most pages, the language of the page is correct and can be determined programmatically. The following exceptions exist:

• The page does not have a valid language assigned, so screen readers may mispronounce content. This occurs on the following page(s): Project Overview.

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)
• 602.3 (Support Docs)

Web: Supports

Web: 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.

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)

Web: Partially Supports

Web: In most cases, 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, or the user is informed about the change ahead of time. The following exceptions exist:

• When a user changes the setting of a user interface control (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disoriented. This occurs on the following page(s): Notifications; Preferences; Background - Corn; Repository Graph; Background jobs - Dashboard.

3.2.6 Consistent Help (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Supports

Web: On web pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order.

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)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Partially Supports

Web: For most 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. The following exceptions exist:

• A form field with an error is not identified in the text error message or a text alternative for an image, and the error message with the field name is not programmatically associated with the form field (so it is announced when a screen reader user navigates to the field), so people who are blind and/or use a screen reader will not be able to identify in which form field the error occurred. This occurs on the following page(s): Issue Boards; Create or import your first project.
• Known instances where the identification and description of an error is not always combined programmatically to help assistive technologies to identify an error are tracked in the &7341 epic.

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)

Web: Partially Supports

Web: 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:

• The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following page(s): Run Pipe Line; Repository Graph; Issue details; New issue; Bulk Edit; Merge requests details - Overview tab; Schedule new pipeline; Explore Topics; Get started with GitLab Pages; Commits; Milestones.
• The label for a form field is missing, so the field's purpose is not clear. This occurs on the following page(s): Notifications; Vulnerability report; Compare revisions; Run Pipe Line; Background - Corn; Labels - All tab; Kubernetes Cluster; Merger Request; General; Value Stream Analytics; Schedule new pipeline; Get started with GitLab Pages; Pipeline; Milestones; Project audit events; Configure feature flags dialog; Members.
• Some visible Instructions for a form input field are not available for people who use assistive technology. This occurs on the following page(s): Get started with GitLab Pages.
• Select or dropdown control missing a visible label. This occurs on the following page(s): Releases; Background - Corn; Search and Filter; Rich text editor; Background jobs - Dashboard; Date Picker.
• Known instances where a label is not present are tracked in the &621 epic.

3.3.7 Redundant Entry (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Supports

Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security.

4.1.1 Parsing (Level A)

Also applies to:

WCAG 2.0 and 2.1 – Always answer "Supports"

WCAG 2.2 (obsolete and removed) - Does not apply

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)

Web: Supports

Web: 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. This criterion was removed from WCAG 2.2.

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
• 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)

Web: Does Not Support

Web: The name, role, state, and/or value of most, if not all, user interface components cannot be programmatically determined. The following issues exist:

• A button does not have a programmatic role, so its 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 page(s): Users; Profile; Issue Boards; Jobs - All; Issues list; Branches; Issue details; Merge requests details - Overview tab; Value Stream Analytics; Container Registry; Admin Dashboard; Instance subscription; Merge requests list - All tab; Explore Projects; Commits.
• A button does not have a programmatic role and name, so its role (usually button, but sometimes link or something else) and its name (such as "Submit" or "Cancel") are 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 page(s): Pipe Line Editor; Security dashboard; Background jobs - Dashboard; Sidebar.
• When a button is pressed, its pressed state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the button is pressed. This occurs on the following page(s): Rich text editor; Security dashboard; CI/CD Analytics; Value Stream Analytics; Project audit events.
• An element that appears and functions like a combobox 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 name, purpose, or content of the element or how to interact with it. This occurs on the following page(s): GitLab Duo Chat; Issue Boards; Pipe Line Editor; Vulnerability report; Compare revisions; Repository Graph; Edit Profile; Search and Filter; Rich text editor; GitLab is better with colleagues!' dialog; Bulk Edit; General; Repository Analytics; New Merge Request; Commits; Create a blank Project; Members.
• An element that appears and functions like a modal dialog 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 name, purpose, or content of the element or how to interact with it. This occurs on the following page(s): What's new flyout.
• An element does not have an attribute in its HTML code that will provide its programmatic role to assistive technology or the role assigned is not correct (like assigning a button the role of "checkbox"), 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 content of the element or how to interact with it. This occurs on the following page(s): Rich text editor.
• The programmatic state of an element that reveals or hides content ("expanded" or"collapsed") is missing or is used incorrectly, so people who are blind and/or use a screen reader or other assistive technology will not be informed of the current state of the element or the state will be misrepresented. This occurs on the following page(s): Job Details; Issue Boards; Pipe Line Editor; Releases; Background - Corn; Search and Filter; Rich text editor; Merge requests details - Changes tab; Merge requests details - Pipelines tab; Merge requests details - Overview tab; Merge requests list - All tab; Sidebar; Pipeline; Dependencies.
• For an element that allows 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 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 the element, the options available, and whether the element or an option is currently checked. This occurs on the following page(s): Users; Pagination; Dashboard; Preferences; Run Pipe Line; Background - Corn; Branches; Edit Profile; Merge requests details - Changes tab; Issue details; Labels - All tab; DevOps Reports; New issue; Background jobs - Dashboard; Merge requests details - Overview tab; Date Picker; Create or import your first project; Projects Details; Google Cloud; Activity - All Tab; Pipelines details; Explore Projects; Milestones.
• The content of a tooltip cannot be accessed using a screen reader, so people who are blind and others who use a screen reader will not be able to read this content. This occurs on the following page(s): Profile; Issue Boards; Pipe Line Editor; Issues list; Repository Graph; Background jobs - Dashboard; Merge requests details - Overview tab; CI/CD Analytics; Value Stream Analytics; Repository Analytics.
• A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following page(s): Repository Graph; Value Stream Analytics.
• The HTML code for a link or button is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of the element. This occurs on the following page(s): Pipe Line Editor; Issue details; Merge requests details - Pipelines tab; Merge requests details - Overview tab; Pipeline.
• A form field does not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the form field or what input it requires. This occurs on the following page(s): Search and Filter; New issue.
• A link does not have discernible link text, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the destination or function of the link. This occurs on the following page(s): Repository Graph.
• An element with a "link," "button," or "menuitem" role 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(s): Merge requests details - Changes tab.
• A form input element does not have a 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 how to interact with it. This occurs on the following page(s): Project Overview.
• An element that is focusable or contains one or more focusable elements is programmatically hidden, so people who use the keyboard to navigate as well as people who are blind and/or use a screen reader or other assistive technology will not be able to perceive or interact with the element. This occurs on the following page(s): Releases; Repository; DevOps Reports; Project Overview; Instance subscription; Get started with GitLab Pages.
• A link does not have discernible text, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the destination or function of the link. This occurs on the following page(s): Job Details; New Feature Flag; Security configuration; Edit Profile; Merge requests details - Changes tab; Labels - All tab; General; Admin Dashboard; Pipeline.
• A progressbar element does not have a 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 the information it conveys. This occurs on the following page(s): Releases; Usage Quotas.
• An iframe does not have a programmatic title that is 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 or content of the iframe without browsing its content. This occurs on the following page(s): Background - Corn; Background jobs - Dashboard.
• The HTML code for a link or button is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of the element. This occurs on the following page(s): Job Details; Issue Boards; Issue details; Usage Quotas.
• A form input element does not have a 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 how to interact with it. This occurs on the following page(s): GitLab is better with colleagues!' dialog.
• A tooltip element does not have a 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 the information it conveys. This occurs on the following page(s): Repository Analytics.
• Authored Content (Rich text editor): The product does not allow authors to provide accessible name of the checkboxes. This occurs on the following page(s): Rich text editor.
• Know instances are tracked in the &567 epic.

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)

Web: Not Applicable

Web: 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)
• 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)

Web: Not Applicable

Web: Prerecorded multimedia files are not present, so audio descriptions are not required.

1.3.4 Orientation (Level AA 2.1 and 2.2)

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

Web: Supports

Web: 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 and 2.2)

Also applies to:

EN 301 549 Criteria

• 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

Web: Partially Supports

Web: The purpose of most input fields that collect an individual's personal data are programmatically defined based on the WCAG list of Input Purposes for User Interface Components. The following exceptions exist:

• No programmatic purpose is provided for an input element (like a text input field), so browsers or assistive technology are not able to automatically suggest information to fill in the input. This occurs on the following page(s): Edit Profile; Email address; Start your Free Ultimate Trial; About your company.
• The programmatic purpose provided for an input element (like a text input field) is not accurate, so information automatically suggested by the browser or assistive technology to fill in the input will be incorrect. This occurs on the following page(s): Create or import your first project.

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)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Partially Supports

Web: Most text and images of regular text have the required color contrast ratio with their backgrounds. The following exceptions exist:

• The color contrast ratio between placeholder text in an input and the input's 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(s): Users; GitLab Duo Chat; Pipe Line Editor; Vulnerability report; Run Pipe Line; Edit Profile; Search and Filter; Merge requests details - Changes tab; Issue details; GitLab is better with colleagues!' dialog; DevOps Reports; New issue; Bulk Edit; Merger Request; Schedule new pipeline; Explore Topics; Monitor Settings; Get started with GitLab Pages.
• 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 page(s): Project wide; GitLab Duo Chat; Pipe Line Editor; Issues list; Issue details; GitLab is better with colleagues!' dialog; DevOps Reports; General; Get started with GitLab Pages.
• The color contrast ratio on hover or focus between a control's text label and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of the control. This occurs on the following page(s): GitLab Duo Chat; Background - Corn; Rich text editor; Labels - All tab; New issue; Project Overview; Background jobs - Dashboard.
• The color contrast ratio between text and its background is less than 4.5:1 (or less than 3:1 for large text), so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following page(s): Preferences; Issue Boards; Issues list; Background - Corn; Merge requests details - Changes tab; Issue details; Labels - All tab; Background jobs - Dashboard; Merge requests details - Overview tab; Repository Analytics; Schedule new pipeline; New Merge Request; Get started with GitLab Pages.
• Known instances are tracked in the &562 epic.

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)
• 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)

Web: Partially Supports

Web: 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 need to enlarge text to read it may not have access to that content. This occurs on the following page(s): Pipe Line Editor; Learn Git Lab; DevOps Reports.
• Known instances where text is clipped or inaccessible when zoomed are tracked in the &563 epic.

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) – 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)

Web: Supports

Web: When content can be presented visually using only text, an image of text is not used to present that text.

• Known instances are tracked in the &10943 epic.

1.4.10 Reflow (Level AA 2.1 and 2.2)

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

Web: Partially Supports

Web: The content of most pages is viewable without scrolling horizontally when the viewport is set to 320 CSS pixels wide. The following exceptions exist:

• When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following page(s): Notifications; Preferences; Instance subscription; Projects Details.
• When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs on the following page(s): Pipe Line Editor; Vulnerability report; Releases; Repository; Learn Git Lab; Add new Access token; Kubernetes Cluster; DevOps Reports; Project Overview; Merge requests details - Overview tab; Groups; Monitor Settings; Activity - All Tab; Keyboard Shortcuts dialog.
• When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following page(s): Value Stream Analytics; Feature Flags.

1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

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)
• 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

Web: Partially Supports

Web: 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 boundary of an interactive element (like a radio button or input field) does 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 page(s): New Label.
• An icon (or part of the icon required to understand its content) does 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 the icon. This occurs on the following page(s): New value stream dialog; Add new Access token; Issue details; New issue; Bulk Edit.
• The indicator for the state of an interactive element (like a checkbox or radio button) does 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 element. This occurs on the following page(s): Rich text editor; Merge requests details - Changes tab; New issue; Pipelines details.
• An image or graphic (like a chart) or part of the image/graphic required to understand its content does 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 the image/graphic. This occurs on the following page(s): Profile.
• The focus indicator of an interactive element (like a button or input field) does 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 the interactive element is receiving focus. This occurs on the following page(s): GitLab Duo Chat.
• Known instances are being tracked in the &8763 epic.

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

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)
• 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

Web: Supports

Web: The spacing between letters, words, lines of text and paragraphs can be adjusted with no loss of content or functionality.

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

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

Web: Partially Supports

Web: 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 page(s): Repository Graph; Security dashboard; Background jobs - Dashboard; 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 content. This occurs on the following page(s): Repository Graph; Security dashboard; Background jobs - Dashboard; CI/CD Analytics; Repository Analytics; Sidebar; Pipelines details.

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

• R501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Web: Multiple ways are available to find other pages on the site.

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)

Web: Partially Supports

Web: Most headings and labels for form and interactive controls are informative. The following exceptions exist:

• A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following page(s): Users; Notifications; GitLab Duo Chat; Issue Boards; New Feature Flag; Repository; Branches; Search and Filter; Merge requests details - Changes tab; DevOps Reports; Project Overview; Value Stream Analytics; Date Picker; New Tag; Policies; Get started with GitLab Pages; Dependencies; Members.
• 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 page(s): Users; Issue Boards; Pipe Line Editor; Jobs - All; Vulnerability report; Run Pipe Line; Releases; New Feature Flag; Repository; New value stream dialog; Security configuration; Background - Corn; Search and Filter; Merge requests details - Changes tab; Issue details; Labels - All tab; Environments; Kubernetes Cluster; DevOps Reports; New issue; Project Overview; Merge requests details - Pipelines tab; Merge requests details - Overview tab; General; Schedule new pipeline; Monitor Settings; Web Hooks; Pipelines details; New Merge Request; Get started with GitLab Pages; Commits; Pipeline; Merge requests details -Commits tab; Milestones; Project audit events; Feature Flags; Members.

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)

Web: Partially Supports

Web: In most cases, it is visually apparent which page element is currently receiving keyboard focus. The following exceptions exist:

• An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following page(s): Create or import your first project.

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Partially Supports

Web: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. The following exceptions exist:

• A focused element is completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following page(s): Users; GitLab Duo Chat; Jobs - All; Vulnerability report; Repository; Background - Corn; Issue details; Environments; New issue; Bulk Edit; Merge requests details - Overview tab; Admin Dashboard; Instance subscription; Pipelines details.
• Known instances are being tracked in the &14070 epic.

2.5.7 Dragging Movements (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Partially Supports

Web: Most functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. The following exceptions exist:

• Some functionality relies on a dragging movement with no single-pointer, single touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture on the following page(s): Labels - All tab.
• Known instances are being tracked in the &14073 epic.

2.5.8 Target Size (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Partially Supports

Web: The size of the target for most clickable controls is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is inline with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. The following exceptions exist:

• A target's hit area does not meet minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs on the following page(s): Issues list; Merge requests details - Overview tab; Merge requests list - All tab.
• A target's hit area does not meet minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately on the following page(s): Users; Job Details; Issue Boards; Issues list; Vulnerability report; Background - Corn; Branches; Merge requests details - Changes tab; Issue details; Integrations; Project Overview; Merge requests details - Overview tab; Usage Quotas; Pipeline.
• Known instances are being tracked in the &14071 epic.

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
• 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)

Web: Partially Supports

Web: On most pages, 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. The following exceptions exist:

• A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following page(s): Preferences; Language drop-down.

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) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Web: 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.

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 apply to non-web docs

Web: Supports

Web: Labels, names, and text alternatives for content that have the same functionality across multiple web pages are consistently identified.

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)

Web: Supports

Web: 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.

• Known instances where error remedies are not provided or are not programmatically associated to help assistive technologies are tracked in the &7341 epic.

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)
• 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)

Web: Supports

Web: 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.

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Supports

Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the Web site.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

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

Web: Does Not Support

Web: Most, if not all, status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist:

• A status message is 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 message or they may not hear it in a timely fashion. This occurs on the following page(s): Users; Project wide; Preferences; GitLab Duo Chat; Issue Boards; Pipe Line Editor; Issues list; Vulnerability report; Compare revisions; New Feature Flag; Repository; New value stream dialog; Repository Graph; Edit Profile; Search and Filter; Rich text editor; Merge requests details - Changes tab; Add new Access token; Kubernetes Cluster; GitLab is better with colleagues!' dialog; Integrations; New issue; Project Overview; Merge requests details - Pipelines tab; Merger Request; General; Repository Analytics; Create or import your first project; Schedule new pipeline; Explore Topics; Groups; Merge requests list - All tab; Monitor Settings; Give feedback; New Tag; Keyboard Shortcuts dialog; New Merge Request; Policies; Get started with GitLab Pages; Pipeline; Dependencies; Create a blank Project; Project audit events; Members; Verify Screen.
• Known instances of visual responses to user actions that use a status message, but are not perceptive to assistive technologies are tracked in the &8764 epic.

302.1 Without Vision

Web: Does Not Support

Web: Most, if not all, functionality is not usable without vision. Examples 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.2.1 Timing Adjustable
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (in context)
• 2.4.6 Headings and Labels
• 3.1.1 Language of Page
• 3.1.2 Language of Parts
• 3.2.2 On Input
• 4.1.2 Name, Role, Value

302.2 With Limited Vision

Web: Does Not Support

Web: Most, if not all, functionality is not usable with limited vision. Examples 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.2.1 Timing Adjustable
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (in context)
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 3.1.1 Language of Page
• 3.1.2 Language of Parts
• 3.2.2 On Input
• 3.3.1 Error Identification
• 3.3.2 Labels or Instructions
• 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)
• 3.3.1 Error Identification

302.4 Without Hearing

Supports

All functionality in the website is usable without hearing.

302.5 With Limited Hearing

Supports

All functionality in the website is usable with limited hearing.

302.7 With Limited Manipulation

Web: Does Not Support

Web: Most, if not all, functionality is not usable with limited manipulation and/or requires fine motor control or simultaneous manual operations. Examples are noted in:

• 2.1.1 Keyboard
• 2.2.1 Timing Adjustable
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (in context)
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 4.1.2 Name, Role, Value

302.8 With Limited Reach and Strength

Supports

All functionality is usable with limited reach and strength.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Does Not Support

Web: Most, if not all, functionality is not 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. Examples 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.2.1 Timing Adjustable
• 2.2.2 Pause, Stop, Hide
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (in context)
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 3.1.1 Language of Page
• 3.1.2 Language of Parts
• 3.2.2 On Input
• 3.3.1 Error Identification
• 3.3.2 Labels or Instructions
• 4.1.2 Name, Role, Value

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.2 section

See information in WCAG 2.2 section

502 Interoperability with Assistive Technology

Heading cell – no response required

Heading cell – no response required

502.2.1 User Control of Accessibility Features

Not Applicable

This Web site is not platform software, so this requirement does not apply.

502.2.2 No Disruption of Accessibility Features

Not Applicable

This website does not have accessibility features.

Heading cell – no response required

Heading cell – no response required

502.3.1 Object Information

Web: Does Not Support

Web: The role, state(s), properties, boundary, name, and description of most, if not all, objects cannot be programmatically determined, so those attributes cannot be perceived and conveyed by assistive technology. Examples are noted in:

• 4.1.2. Name, Role, Value

502.3.2 Modification of Object Information

Web: Partially Supports

Web: For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions are noted in:

• 4.1.2. Name, Role, Value

502.3.3 Row, Column, and Headers

Web: Partially Supports

In most instances when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions are noted in:

• 1.3.1 Info and Relationships

502.3.4 Values

Web: Partially Supports

Web: For most objects that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology. Exceptions include:

• 4.1.2. Name, Role, Value

502.3.5 Modification of Values

Web: Partially Supports

Web: For most objects that allow the user to set or modify its value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:

• 4.1.2. Name, Role, Value

502.3.6 Label Relationships

Web: Partially Supports

Web: For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions are noted in:

• 1.3.1 Info and Relationships
• 4.1.2. Name, Role, Value

502.3.7 Hierarchical Relationships

Web: Partially Supports

For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions are noted in:

• 1.3.1 Info and Relationships

502.3.8 Text

Web: Supports

All text, text attributes (such as whether text is static or editable), and text boundaries (such as when text receives visual focus) are programmatically determinable, so they can be perceived and conveyed by assistive technology.

502.3.9 Modification of Text

Web: Supports

When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology.

502.3.10 List of Actions

Web: Partially Supports

For most of the elements on which one or more actions may be performed, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology. Exceptions are noted in:

• 4.1.2. Name, Role, Value

502.3.11 Actions on Objects

Web: Partially Supports

For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include:

• 2.1.1 Keyboard

502.3.12 Focus Cursor

Web: Supports

The position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology.

502.3.13 Modification of Focus Cursor

Web: Not Applicable

This web site does not allow modification of the focus indicator, text insertion point, or text selector indicator.

502.3.14 Event Notification

Web: Does Not Support

Most, if not all, status messages relevant to user interactions are not available to, and are not presented by, assistive technology. Examples are noted in:

• 4.1.3 Status Messages

502.4 Platform Accessibility Features

Web: The website is not platform software, so this requirement does not apply.

Heading cell – no response required

Heading cell – no response required

503.2 User Preferences

Not Applicable

503.3 Alternative User Interfaces

Web: Not Applicable

Web: The website or application does not offer an alternative user interface.

503.4 User Controls for Captions and Audio Description

Heading cell – no response required

Heading cell – no response required

503.4.1 Caption Controls

Web: Not Applicable

Web: This web site does not contain media with an audio component that has closed captions.

503.4.2 Audio Description Controls

Web: Not Applicable

Web: This website does not contain media with a video component that offers audio descriptions.

504 Authoring Tools

Heading cell – no response required

Heading cell – no response required

504.2 Content Creation or Editing

See WCAG 2.2 section

See information in WCAG 2.2 section

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Web: Not Applicable

Web: This web site is not an authoring tool.

504.2.2 PDF Export

Web: Not Applicable

Web: This web site is not an authoring tool.

504.3 Prompts

Web: Not Applicable

Web: This web site is not an authoring tool.

601.1 Scope

Heading cell – no response required

Heading cell – no response required

602 Support Documentation

Heading cell – no response required

Heading cell – no response required

602.2 Accessibility and Compatibility Features

Not Applicable

602.3 Electronic Support Documentation

See WCAG 2.2 section

See information in WCAG 2.2 section

602.4 Alternate Formats for Non-Electronic Support Documentation

Not Applicable

603 Support Services

Heading cell – no response required

Heading cell – no response required

603.2 Information on Accessibility and Compatibility Features

Not Applicable

603.3 Accommodation of Communication Needs

Not Applicable

4.2.1 Usage without vision

Web: Does Not Support

Web: Most, if not all, functionality is not usable without vision. Examples 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.1.4 Character Key Shortcuts
• 2.2.1 Timing Adjustable
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (in context)
• 2.4.6 Headings and Labels
• 3.1.1 Language of Page
• 3.1.2 Language of Parts
• 3.2.2 On Input
• 3.3.1 Error Identification
• 4.1.2 Name, Role, Value
• 4.1.3 Status Messages

4.2.2 Usage with limited vision

Web: Does Not Support

Web: Most, if not all, functionality is not usable with limited vision. Examples 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
• 1.4.10 Non-Text Contrast
• 1.4.11 Non-Text Contrast
• 1.4.13 Content on Hover or Focus
• 2.1.1 Keyboard
• 2.2.1 Timing Adjustable
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (in context)
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 3.1.1 Language of Page
• 3.1.2 Language of Parts
• 3.2.2 On Input
• 3.3.1 Error Identification
• 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
• 3.3.1 Error Identification

4.2.4 Usage without hearing

Web: Supports

Web: All functionality in the website is usable without hearing.

4.2.5 Usage with limited hearing

Web: Supports

Web: All functionality in the website is usable with limited hearing.

4.2.6 Usage with no or limited 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: Does Not Support

Web: Most, if not all, functionality is not usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength. Examples are noted in:

• 1.3.5 Identify Input Purpose
• 1.4.13 Content on Hover or Focus
• 2.1.1 Keyboard
• 2.1.4 Character Key Shortcuts
• 2.2.1 Timing Adjustable
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (in context)
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 2.5.3 Label in Name
• 4.1.2 Name, Role, Value

4.2.8 Usage with limited reach

Web: Partially Supports

Web: All functionality is usable by people with limited reach.

• 1.3.5 Identify Input Purpose
• 1.4.13 Content on Hover or Focus
• 2.1.4 Character Key Shortcuts
• 2.5.3 Label in Name

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, language or learning

Web: Does Not Support

Web: Most, if not all, functionality is not 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. Examples 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.13 Content on Hover or Focus
• 2.1.1 Keyboard
• 2.1.4 Character Key Shortcuts
• 2.2.1 Timing Adjustable
• 2.2.2 Pause, Stop, Hide
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (in context)
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 2.5.3 Label in Name
• 3.1.1 Language of Page
• 3.1.2 Language of Parts
• 3.2.2 On Input
• 3.3.1 Error Identification
• 3.3.2 Labels or Instructions
• 4.1.2 Name, Role, Value
• 4.1.3 Status Messages

4.2.11 Privacy

Web: Not Applicable

Web: The web pages do not contain any privacy features.

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 Audio output of visual information

Not Applicable

The product does not have closed functionality.

5.1.3.2 Auditory output delivery including speech

Not Applicable

The product does not have closed functionality.

5.1.3.3 Auditory output correlation

Not Applicable

The product does not have closed functionality.

5.1.3.4 Speech output user control

Not Applicable

The product does not have closed functionality.

5.1.3.5 Speech output automatic interruption

Not Applicable

The product does not have closed functionality.

5.1.3.6 Speech output for non-text content

Not Applicable

The product does not have closed functionality.

5.1.3.7 Speech output for video information

Not Applicable

The product does not have closed functionality.

5.1.3.8 Masked entry

Not Applicable

The product does not have closed functionality.

5.1.3.9 Private access to personal data

Not Applicable

The product does not have closed functionality.

5.1.3.10 Non-interfering audio output

Not Applicable

The product does not have closed functionality.

5.1.3.11 Private listening volume

Not Applicable

The product does not have closed functionality.

5.1.3.12 Speaker volume

Not Applicable

The product does not have closed functionality.

5.1.3.13 Volume reset

Not Applicable

The product does not have closed functionality.

5.1.3.14 Spoken languages

Not Applicable

The product does not have closed functionality.

5.1.3.15 Non-visual error identification

Not Applicable

The product does not have closed functionality.

5.1.3.16 Receipts, tickets, and transactional outputs

Not Applicable

The product does not have closed functionality.

5.1.4 Functionality closed to text enlargement

Not Applicable

The product does not have closed functionality.

5.1.5 Visual output for auditory information

Not Applicable

The product does not have closed functionality.

5.1.6 Operation without keyboard interface

Heading cell – no response required

Heading cell – no response required

5.1.6.1 Closed functionality

See 5.1.3.1 through 5.1.3.16

See information in 5.1.3.1 through 5.1.3.16

5.1.6.2 Input focus

Not Applicable

The product does not have closed functionality.

5.1.7 Access without speech

Not Applicable

The product does not have closed functionality.

5.2 Activation of accessibility features

Not Applicable

The product does not have specific documented accessibility features.

5.3 Biometrics

Not Applicable

Biometrics are not used to access or use the website.

5.4 Preservation of accessibility information during conversion

Not Applicable

The product does not convert content.

5.5 Operable parts

Heading cell – no response required

Heading cell – no response required

5.5.1 Means of operation

Not Applicable

The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate

5.5.2 Operable parts discernibility

Does Not Support

The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions are noted in 1.3.1 Info and Relationships, 2.4.6 Headings and Labels and 4.1.2 Name, Role, Value.

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

Tactile or auditory status is not included in the product.

5.6.2 Visual status

Supports

Visual status of controls is discernable in the product.

5.7 Key repeat

Not Applicable

Key repeat functionality is not found in the product.

5.8 Double-strike key acceptance

Not Applicable

Double-strike key acceptance is not found in the product.

5.9 Simultaneous user actions

Not Applicable

The product does not require simultaneous user actions to achieve any functionality.