Paradraw
GitLab/
notice

GitLab Accessibility Conformance Report International Edition

22,689 words, 364 clausesno date on the pageread 12/10/2026source

·GitLab Accessibility Conformance Report International Edition

·Based on VPAT® Version 2.5, International Edition (template) April 2025

  • ·Name of Product/Version: Self Managed GitLab Ultimate 19 with GitLab Duo Agentic Platform Report Date: August 4, 2026
  • ·Product Description: GitLab is The DevSecOps Platform that empowers organizations to maximize the overall return on software development by delivering software faster and efficiently, while strengthening security and compliance. With GitLab, every team in your organization can collaboratively plan, build, secure, and deploy software to drive business outcomes faster with complete transparency, consistency, and traceability across the DevSecOps lifecycle.
  • ·Contact information: accessibility@gitlab.com
  • ·General notes:
  • ·This report was created by Deque Systems Inc. upon completion of an accessibility evaluation performed between June 1, 2026 and July 31, 2026.
  • ·This evaluation only refers to GitLab the product and does not include the about.gitlab.com or docs.gitlab.com websites.
  • ·The latest report provides a new evaluation of GitLab Ultimate version 19. New success criteria from the VPAT 2.5 template have also been added. This revision supersedes earlier versions of this report.
  • ·GitLab supports the current and previous major version along with current minor version of the following browsers: Mozilla Firefox, Google Chrome, Chromium, Apple Safari, Microsoft Edge.
  • ·GitLab does not support running with JavaScript disabled in the browser because several features require JavaScript extensively.
  • ·View GitLab installation minimum requirements for both the supported operating systems and the minimum requirements needed to install and use GitLab.
  • ·Known accessibility issues are linked in the tables below and may also be found by searching GitLab.com (account required).
  • ·WCAG 2.2 notes:
  • ·When reporting on conformance with the WCAG 2.2 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.
  • ·Table 3: Success Criteria, Level AAA has been removed because the GitLab product has not been evaluated for WCAG 2.2 Level AAA conformance.
  • ·Section 508 notes:
  • ·The ICT covered by this report is not hardware. As such, the requirements of this chapter do not apply.

·Evaluation Methods Used

·A combination of automated and manual testing techniques was employed for the accessibility audit.

  • ·Manual audit was performed using Chrome on Windows and included exclusive use of the keyboard.
  • ·Automated tools used included Axe Auditor and the Axe Dev Tools browser extension. Assistive technologies employed included latest version of NVDA.

·Scope of Evaluation

·The pages in the following table were evaluated as part of the audit on which this report is based. Page Title | URL

Access tokens | [url]/demo-group/project-1/-/settings/access_tokens Account | [url]/-/profile/account
Activity - All Tab[url]/demo-group/project-1/activity
Add new comment template[url]/-/profile/comment_templates
Agent detail[url]/demo-group/project-1/-/automate/agents/2
Agents[url]/demo-group/project-1/-/automate/agents
Analytics dashboard detail[url]/demo-group/project-1/-/analytics/dashboards/value_streams_dashboard
Analytics dashboards[url]/demo-group/project-1/-/analytics/dashboards
Artifacts[url]/demo-group/project-1/-/artifacts
Audit events[url]/demo-group/project-1/-/audit_events
Branches[url]/demo-group/project-1/-/branches
CI/CD[url]/demo-group/project-1/-/settings/ci_cd
CI/CD analytics[url]/demo-group/project-1/-/pipelines/charts
Code review analytics[url]/demo-group/project-1/-/analytics/code_reviews
Comment templates[url]/-/profile/comment_templates
Commit detail[url]/demo-group/project-1/-/commit/commit-hash
Commits[url]/gitlab-org/gitlab/-/commits/master?ref_type=heads
Compare revisions[url]/demo-group/project-1/-/compare?from=main&to=main
Configure feature flags modal[url]/demo-group/project-1/-/feature_flags
Connect a cluster (agent)[url]/demo-group/project-1/-/clusters
Container detail[url]/demo-group/project-1/container_registry/13
Container registry[url]/demo-group/project-1/container_registry
Contributor analytics[url]/demo-group/project-1/-/graphs/main?ref_type=heads
Create a Kubernetes cluster[url]/demo-group/project-1/-/clusters/new_cluster_docs
Create a new release[url]/demo-group/project-1/-/releases/new
Create an environment[url]/demo-group/project-1/-/environments/new
Create merge request[url]/demo-group/project-1/-/merge_requests/new
Create new model[url]/demo-group/project-1/-/ml/models/new
Create using MLFlow modal[url]/demo-group/project-1/-/ml/models?first=30&orderBy=created_at&sort=desc
Create wiki page[url]/demo-group/project-1/-/wikis/home?view=create
Customer information[url]/subscriptions/purchase/new?deployment_type=self_managed&product_rate_plan_id=UNIQUE_PLAN_ID&subscription_name=UNIQUE_SUBSCRIPTION_ID
Customers Portal_Billing account settings[url]/billing_accounts
Customers Portal_GitLab credits dashboard[url]/subscriptions/A-S00162972/usage
Customers Portal_Sign in[url]/customers/sign_in
Customers Portal_Subscriptions & purchases[url]/subscriptions
Edit Profile | [url]/-/user_settings/profile Email address | [url]/-/profile/emails
Environments[url]/demo-group/project-1/-/environments
Feature flags[url]/demo-group/project-1/-/feature_flags
Flow detail[url]/demo-group/project-1/-/automate/flows/3/
Flows[url]/demo-group/project-1/-/automate/flows
General | [url]/demo-group/project-1/edit GitLab Duo Chat Section | [url]/ Help | [url]/help Homepage | [url]/
Insights[url]/demo-group/project-1/insights#/issues
Integrations[url]/demo-group/project-1/-/settings/integrations
Issue analytics[url]/demo-group/project-1/-/analytics/issues_analytics
Issue Boards[url]/demo-group/project-1/-/boards
Issues - Open tab[url]/demo-group/project-1/-/work_items?first_page_size=20&sort=created_date&state=opened
Issues list[url]/demo-group/project-1/-/work_items?sort=created_date&state=opened&first_page_size=20
Iterations[url]/demo-group/project-1/-/cadences
Jobs[url]/demo-group/project-1/-/jobs?kind=BUILD
Keyboard Shortcuts dialog[url]/demo-group/project-1/edit#js-gitlab-duo-settings
Kubernetes Cluster[url]/demo-group/project-1/-/clusters
Labels - All tab[url]/demo-group/project-1/-/labels
Members[url]/demo-group/project-1/-/project_members
Merge requests[url]/dashboard/merge_requests
Merge Requests Settings[url]/demo-group/project-1/-/settings/merge_requests
Milestones[url]/demo-group/project-1/-/milestones
Model registry[url]/demo-group/project-1/-/ml/models?first=30&orderBy=created_at&sort=desc
New agent[url]/demo-group/project-1/-/automate/agents/new
New feature flag[url]/demo-group/project-1/-/feature_flags/new
New flow[url]/demo-group/project-1/-/automate/flows/new
New issue[url]/demo-group/project-1/-/work_items?first_page_size=20&sort=created_date&state=opened
New Label[url]/demo-group/project-1/-/labels/new
New milestone[url]/demo-group/project-1/-/milestones/new
New on demand scan[url]/demo-group/project-1/-/on_demand_scans/new
New snippet[url]/demo-group/project-1/-/snippets/new
New Tag[url]/demo-group/project-1/-/tags/new
New test case[url]/demo-group/project-1/-/quality/test_cases/new
New trigger[url]/demo-group/project-1/-/automate/triggers/new
New user list[url]/demo-group/project-1/-/feature_flags_user_lists/new
New value stream[url]/demo-group/project-1/-/analytics/value_stream_analytics/value_streams/new
Notifications[url]/-/profile/notifications
On Demand Scans[url]/demo-group/project-1/-/on_demand_scans
Package registry[url]/demo-group/project-1/-/packages
Packages and registries[url]/demo-group/project-1/-/settings/packages_and_registries
Password[url]/-/user_settings/password/edit
Payment method[url]/subscriptions/purchase/new?deployment_type=self_managed&product_rate_plan_id=UNIQUE_PLAN_ID&subscription_name=UNIQUE_SUBSCRIPTION_ID
Pipeline detail[url]/demo-group/project-1/-/pipelines/7094
Pipeline editor[url]/demo-group/project-1/-/ci/editor
Pipelines[url]/demo-group/project-1/-/pipelines
Policies[url]/deque-accessibility-audit/seeded-content/swag-shop/-/security/policies
Preferences | [url]/-/profile/preferences Profile | [url]/USERNAME
Releases[url]/demo-group/project-1/-/releases
Repository[url]/demo-group/project-1/-/tree/main
Repository analytics[url]/demo-group/project-1/-/graphs/main/charts
Repository graph[url]/demo-group/project-1/-/network/main?ref_type=heads
Repository Settings[url]/demo-group/project-1/-/settings/repository#cleanup
Requirements[url]/demo-group/project-1/-/requirements_management/requirements
Run new pipeline[url]/demo-group/project-1/-/pipelines/new
Schedule new pipeline[url]/demo-group/project-1/-/pipeline_schedules/new
Security configuration - Security testing tab[url]/demo-group/project-1/-/security/configuration
Security dashboard[url]/demo-group/project-1/-/security/dashboard
Snippet detail[url]/demo-group/project-1/-/snippets/4
Snippets[url]/demo-group/project-1/-/snippets
SSH keys[url]/-/user_settings/ssh_keys
Submit vulnerability[url]/demo-group/project-1/-/security/vulnerabilities/new
Subscription Details[url]/subscriptions/purchase/new?deployment_type=self_managed&product_rate_plan_id=UNIQUE_PLAN_ID&subscription_name=UNIQUE_SUBSCRIPTION_ID
Tags[url]/demo-group/project-1/-/tags/1.0.0
Terraform init command dialog[url]/demo-group/project-1/-/ml/models/new
Terraform modules[url]/deque-accessibility-audit/seeded-content/swag-shop/-/terraform_module_registry/3
Terraform states[url]/deque-accessibility-audit/seeded-content/swag-shop/-/terraform
Test cases[url]/demo-group/project-1/-/quality/test_cases
Triggers[url]/demo-group/project-1/-/automate/triggers
Usage quotas[url]/-/profile/usage_quotas#pipelines-quota-tab
Usage quotas - Storage tab[url]/-/profile/usage_quotas#storage-quota-tab
Value Stream Analytics[url]/demo-group/project-1/-/value_stream_analytics
Vulnerability report[url]/demo-group/project-1/-/security/vulnerability_report
Web Hooks[url]/demo-group/project-1/-/hooks

·Applicable Standards/Guidelines

·This report covers the degree of conformance for the following accessibility standard/guidelines: Standard/Guideline | Included In Report

Web Content Accessibility Guidelines 2.0Level A (Yes) Level AA (Yes) Level AAA (No)
Web Content Accessibility Guidelines 2.1Level A (Yes) Level AA (Yes) Level AAA (No)
Web Content Accessibility Guidelines 2.2Level A (Yes) Level AA (Yes) Level AAA (No)
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018(Yes)
EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11) and EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03)(Yes)

·Terms

·The terms used in the Conformance Level information are defined as follows:

  • ·Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • ·Partially Supports: Some functionality of the product does not meet the criterion.
  • ·Does Not Support: The majority of product functionality does not meet the criterion.
  • ·Not Applicable: The criterion is not relevant to the product.
  • ·Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG Level AAA criteria.

·WCAG 2.2 Report

·Tables 1 and 2 also document conformance with:

  • ·Revised Section 508:
  • ·Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing
  • ·Chapter 6 - 602.3 Electronic Support Documentation
  • ·EN 301 549:
  • 9Clause 9 - Web
  • ·Clauses 10.1-10.4 of Clause 10 - Non-web documents
  • ·Clauses 11.1-11.4 and 11.8.2 of Clause 11 - Software
  • ·Clauses 12.1.2 and 12.2.4 of Clause 12 - Documentation and support services

·Note: When reporting on conformance with the WCAG 2.2 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.

·Table 1: Success Criteria, Level A

CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria 9.1.1.1 (Web) 10.1.1.1 (Non-web document) 11.1.1.1.1 (Open Functionality Software) 11.1.1.1.2 (Closed Functionality Software) 11.8.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs) Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)Web: Partially SupportsWeb: Most non-text content has text alternatives or a text alternative that serves an equivalent purpose. The following exceptions exist: An image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following page: Customers Portal_GitLab credits dashboard. Some images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following pages: New feature flag; Edit Profile; New feature flag; New user list; Create new model; Access tokens; Repository settings; Configure feature flags modal; Pipelines; New snippet; Pipeline detail; Connect a cluster (agent); Run New pipeline; Subscription Details; Customer information; Payment Method; Web Hooks; Tags; Value Stream Analytics; Environments; Preferences; Customers Portal_Subscriptions & purchases; Analytics dashboard detail; Policies; Security configuration - Security testing tab. Some complex images do 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 each image. This occurs on the following pages: Repository Analytics; Issue Analytics; Insights; Security dashboard; Customers Portal_GitLab credits dashboard. Some complex images do not have a long description to convey the information presented by each image, so people who are blind and/or use a screen reader will not be able to understand the information presented by each image. This occurs on the following pages: Contributor analytics; CI/CD analytics. Some decorative images are not hidden from assistive technologies, so a screen reader will announce them unnecessarily. This occurs on the following pages: Model registry; Commits. 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: Contributor analytics. A dynamically changing image does not have a text alternative that changes with it, so people who are blind and/or use a screen reader will not understand the information or function represented by the image. This occurs on the following page: Analytics dashboard detail.
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 ApplicableWeb: Prerecorded audio-only and video-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 ApplicableWeb: 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 ApplicableWeb: Prerecorded videos are not present, so the 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 SupportWeb: 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: Some HTML lists contain elements in the code that are not allowed in a programmatic list, so the structure and/or content of each list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Repository; Model registry. Some description lists are not marked up properly, so the structures of the lists are not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Agent detail; Flow detail. Some content that is visually presented as a list is not properly marked up as a list, so the structures of those lists are not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs in the following pages: Customers Portal_Subscriptions & purchases; Customers Portal_GitLab credits dashboard; Subscription Details; Customer information; Payment method; Customers Portal_Billing account settings; Model registry; Issues list; Profile; Snippet detail; Repository. Some content that is visually presented as multiple lists is not marked up as a list, so the presence and structure of each list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Flow detail. Some 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 in the following pages: Customers Portal_Subscriptions & purchases; Customers Portal_Billing account settings; Customers Portal_Subscriptions & purchases; Customers Portal_GitLab credits dashboard; Subscription Details; Customer information; Payment method; Customers Portal_Billing account settings; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; New flow; Merge requests; Connect a cluster (agent); Access tokens; Help; Create using MLFlow modal; Customers Portal_Billing account settings; Flow detail; Vulnerability report; Analytics dashboard detail; Merge Requests Settings; Run new pipeline; Repository; Snippet detail; Usage quotas - Storage tab; Edit Profile; Issue Boards; Schedule new pipeline; New value stream; Code review analytics. Some heading levels are 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 in the following pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Usage quotas - Storage tab; Create a new release; Kubernetes Cluster; SSH keys; Comment templates; Edit Profile; Merge Requests Settings; GitLab Duo Chat Section; General; Help; Merge requests; Notifications; Flow detail; Analytics dashboard detail; Web Hooks; Email address; Requirements; Repository Settings. Content is arranged visually like a data table, but it is not programmatically marked up as a table, so the table's structure and relationships are not conveyed to people who are blind and/or use a screen reader. This occurs on the following page: Environments. An element's programmatic role requires that the element have a parent element, but the parent element is 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 without the context provided by the parent. This occurs on the following page: Terraform states. One or more data cells is incorrectly marked up as a header cell in some tables, so the table structure and the header/data relationship between the cell(s) and other cells in those tables will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Vulnerability report; Artifacts. Multiple elements' 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 in the following pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Customers Portal_Subscriptions & purchases; Customers Portal_GitLab credits dashboard; Subscription Details; Customer information; Payment method; Customers Portal_Billing account settings; Usage quotas; Artifacts; Terraform states; Kubernetes Cluster; Preferences. A block of text visually styled as deleted or inserted does not have semantic markup or text to indicate programmatically that the text is deleted or inserted, so people who are blind and/or use a screen reader may not be aware that the text is deleted or inserted. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template. Some blocks of text are marked up as headings but are not headings, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs in the following pages: Members; Value Stream Analytics; Agents; Flows; Test cases; Jobs; Requirements; Notifications; Container registry; Container detail; New agent; New flow; Flow detail; Merge Requests Settings; Issues list; Test cases; Issues - Open tab; Requirements; Create wiki page; Customers Portal_Subscriptions & purchases; Issue analytics; On Demand Scans; Connect a cluster (agent); Policies; Usage quotas - Storage tab; Commit detail. Some groups of form controls are not programmatically associated with their group label, so the purpose of individual controls in each group cannot be understood by people who are blind and/or use a screen reader. This occurs in the following pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Configure feature flags modal; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Keyboard Shortcuts dialog; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New issue; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform init command dialog; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; General; Create merge request; Customers Portal_Billing account settings; Usage quotas; Compare revisions; Preferences. Some elements use role="presentation" incorrectly, so each element's semantic meaning will not be conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Value Stream Analytics; Usage quotas; Kubernetes Cluster; Analytics dashboard detail; CI/CD analytics. Data is arranged visually like a data table, but the programmatic table header markup for some tables is missing or incomplete. People who are blind and/or use a screen reader will not be aware of the association between the headers for these tables and their related data. This occurs on the following pages: Issue analytics; Security configuration - Security testing tab; Help; Feature flags; Model registry; Artifacts; Terraform states; Kubernetes Cluster; Vulnerability report; Repository Settings; Commit detail; SSH keys; New on demand scan; Analytics dashboard detail; Terraform modules; Members; Triggers; On Demand Scans; Audit events; Merge Requests Settings; Merge requests; Pipelines; Code review analytics. Some information, structure, and/or relationships are only presented visually but not conveyed programmatically, so context provided to sighted users is not available to people who are blind. This occurs on the following pages: Commit detail; Branches. Some sets of radio buttons are not programmatically grouped, so the group label for each set of radio buttons will not be conveyed to people who are blind and/or use a screen reader, and they will not understand the purpose of the individual radio buttons. This occurs on the following pages: Issue Boards; New snippet; Merge Requests Settings; Profile; New agent; New flow; New value stream; Preferences; Schedule new pipeline; Web Hooks. Content that does not visually function as a list is marked up as a list, so the structure of the page is misrepresented to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Repository. Some sets of checkboxes are not programmatically grouped, so the group label for each set of checkboxes will not be conveyed to people who are blind and/or use a screen reader, and they will not understand the purpose of the individual checkboxes. This occurs on the following pages: Repository Settings; General; Merge Requests Settings; Access tokens; Web Hooks.
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: Does Not SupportWeb: The reading and navigation order of most, if not all, content is not logical or intuitive. The following issues exist: The screen reader skips and does not announce informative static content (text or images), so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: New feature flag; Members; New Flow; Flow detail; Pipeline editor; Value Stream Analytics; Issue analytics; Subscription Details; Policies. 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 pages: Create wiki page; Pipeline editor; Value Stream Analytics. 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 pages: Issues - Open tab; Issues list; GitLab Duo Chat Section. 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 in the following pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Payment method; General; Edit Profile; Analytics dashboard detail; Issues list; Terraform modules; Pipeline detail; Issues - Open tab; Web Hooks; CI/CD. 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: Subscription Details; Customer Information; Payment Method.
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: SupportsWeb: 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 SupportWeb: 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 the state (such as "checked," "pressed," or "selected") of some controls, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following pages: Repository Analytics; Insights; Security dashboard; Customers Portal_Billing account settings; New test case. 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 in the following pages: Issues list; Issues - Open tab; Issue Boards; Requirements; Branches; Pipelines; Jobs; Test cases; Audit events; Package registry; Container detail; Model registry; Code review analytics; Issue analytics; Integrations; Web Hooks; Access tokens; Repository; Merge Requests; CI/CD; Packages and registries; Account; Email address; Notifications; SSH keys; Preferences; Issue analytics; Snippet detail; CI/CD 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 in the following pages: Subscription Details; Customer information; Payment method; New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Help; General; Connect a cluster (agent); Repository Settings; Model registry; Analytics dashboard detail; Flow detail; Web Hooks; Integrations; Merge Requests Settings; Access tokens; Security configuration - Security testing tab; Customers Portal_Subscriptions & purchases; Create merge request; Customers Portal_Sign in; Customers Portal_GitLab credits dashboard; Commits; Security dashboard; SSH keys; Usage quotas - Storage tab; Pipeline editor; Run new pipeline; Usage quotas; On Demand Scans; Create wiki page; Account; Keyboard Shortcuts dialog; New user list; New on demand scan; Create a new release; New Tag; Packages and registries; Edit Profile; Agent detail; Repository; Commit detail; Compare revisions; Insights; Terraform modules; Create an environment; Container registry; Analytics dashboards; Email address; New Label; Vulnerability report; Terraform states; Schedule new pipeline; New flow; Flow detail; Merge requests; Commit detail; Tags; CI/CD Analytics; Profile; Kubernetes Cluster; Members; Activity - All Tab; Snippets; New agent; CI/CD analytics; Configure feature flags modal; Environments; Jobs; Requirements; Terraform init command dialog; CI/CD; Payment method; Policies.
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 ApplicableWeb: 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 SupportsWeb: 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 access keys are present, some may conflict with existing browser and screen reader shortcuts, and some functionality based on custom gestures may not be available when a screen reader is turned on. The following exceptions exist: Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Members; Value Stream Analytics; Issues list; Activity - All Tab; Agents; Agent detail; Flows; New flow; Flow detail; Issues - Open tab; Pipeline detail; Test cases; Merge Requests Settings; Agents; Flows; New flow; Flow detail; Pipeline editor; Merge requests; Run new pipeline; Repository Graph; Pipeline editor; Contributor analytics; New Tag; Repository (Main branch menu button); Repository settings; Repository Analytics; Insights; Security dashboard; Issue Analytics; Contributor analytics; Usage quotas - Storage tab; Profile; GitLab Duo Chat Section; Releases; Audit events; Customers Portal_Billing account settings; Issue Boards; General; Artifacts; Value Stream Analytics; Snippet detail; New agent; Requirements; Issue analytics; Analytics dashboard detail; New on demand scan; Customers Portal_Subscriptions & purchases; Customers Portal_GitLab credits dashboard; Repository Settings; Commit detail; Schedule new pipeline; CI/CD analytics; Kubernetes Cluster; Issues list; Pipeline editor; Pipelines; Security dashboard; Create wiki page; Repository graph. 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 pages: Terraform init command dialog; Profile.
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: Partially SupportsWeb: In most cases, keyboard focus is not locked or trapped in a particular area, and the user can navigate to and from all navigable elements using only a keyboard. The following exception exists: There is a keyboard trap, so people who use a keyboard to navigate content will get stuck in one place on the page. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template.
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 applyWeb: SupportsWeb: If a single-character key shortcut exists, then the single-character key shortcut can be turned off or remapped, or it is only active when the relevant user interface component is in focus.
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria 9.2.2.1 (Web) 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 SupportsWeb: 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 exception exists: 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: Customers Portal_Subscriptions & purchases.
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: Not ApplicableWeb: The tested application does not contain Moving, blinking, scrolling, or auto-updating content.
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 ApplicableWeb: 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 docsWeb: SupportsWeb: 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 SupportsWeb: Most pages have descriptive and informative titles. The following exception exists: The page's programmatic title does not identify the purpose of the page, so people who use a screen reader will not know the purpose of the page without reading its content. This occurs on the following pages: New trigger; Releases; Usage quotas; Customers Portal_Sign in; Issue Boards; Analytics dashboard detail; Repository.
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: Does Not SupportWeb: The navigation order of most, if not all, interactive elements (such as links, buttons, or form elements) is not logical and/or does not preserve meaning and operability. The following issues exist: Keyboard focus is lost or misplaced as a result of user interaction or content update, or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs on the following page: Labels - All tab. 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 in the following pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Configure feature flags modal; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Keyboard Shortcuts dialog; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New issue; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform init command dialog; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks;Pipeline editor; Create wiki page; GitLab Duo Chat Section; Issues list; Payment method. Keyboard focus or touch screen swiping goes to multiple elements that are 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 pages: Payment method; General; CI/CD; Snippet detail; Issues list; Create a new release; Terraform modules; Test cases; New milestone; Issues - Open tab; Web Hooks. 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 in the following pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Configure feature flags modal; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Keyboard Shortcuts dialog; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New issue; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform init command dialog; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Branches; Create using MLFlow modal; Pipelines; New issue. 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 in the following pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks.
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 SupportsWeb: 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 multiple links is not made clear by each link's 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 each link goes. This occurs in the following pages: Subscription Details; Customer information; Payment method; Kubernetes Cluster; Analytics dashboard detail; Usage quotas - Storage tab. Multiple links have identical link text but different destinations, and the context provided by the content that immediately surrounds each link does not provide any clarification, so people who are blind and/or use a screen reader will not know or may be confused about where each link goes. This occurs on the following pages: Jobs; Labels - All tab; On Demand Scans; Commits; Flow detail; General; Repository; Customers Portal_Billing account settings; Repository Settings; Email address; Preferences; Triggers; New on demand scan; Artifacts; Usage quotas - Storage tab; Merge Requests Settings; Customers Portal_Subscriptions & purchases; Account.
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 applyWeb: SupportsWeb: 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 applyWeb: SupportsWeb: 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 (Open Functionality Software) 11.2.5.3 (Closed Software) 11.8.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs) Revised Section 508 - Does not applyWeb: Partially SupportsWeb: 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: Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: Merge Requests Settings; Branches; New Tag; Artifacts; Package registry; Customers Portal_Billing account settings; Terraform modules; New on demand scan; Subscription Details; Web Hooks. The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; New Label; Value Stream Analytics; Edit Profile; Repository Settings; Merge Requests Settings; Customers Portal_GitLab credits dashboard; Container detail; Container registry; Customers Portal_Billing account settings; Requirements; Submit vulnerability; Homepage; Notifications; Members; Payment method; Terraform modules; GitLab Duo Chat Section; New trigger; Issues list; Test cases; Issues - Open tab; Requirements; New on demand scan; Jobs; Vulnerability report; Pipelines; Usage quotas - Storage tab.
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 applyWeb: SupportsWeb: 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 SupportsWeb: On most pages, the language of the page is correct and can be determined programmatically. The following exception exists: The page does not have a valid language assigned, so screen readers may mispronounce content. This occurs on the following page: Snippet detail.
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: SupportsWeb: 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 SupportsWeb: 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 exception exists: When a user changes the setting of some user interface controls (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 pages: Merge Requests Settings; Preferences.
3.2.6 Consistent Help (Level A 2.2 only) EN 301 549 Criteria - Does not apply Revised Section 508 - Does not applyWeb: SupportsWeb: 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 SupportsWeb: 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: An error message for a form input (such as a text input field, radio button, select dropdown, or checkbox) cannot be read by screen readers, so people who use a screen reader may not be made aware when an error has occurred. This occurs on the following page: Pipeline editor; Flow detail. Some form fields with an error are 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 an error occurred. This occurs on the following pages: New feature flag; Web Hooks; New snippet; Merge Requests Settings; Create new model; New on demand scan; Preferences. An error for a form input (such as a text input field, radio button, select dropdown, or checkbox) is not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs on the following page: Pipeline editor; Flow detail.
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 SupportsWeb: 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 labels for some form fields are missing, so each field's purpose is not clear. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Security configuration - Security testing tab; Artifacts; Vulnerability report; New feature flag; Releases. Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following pages: Vulnerability report; Snippet detail; New on demand scan; Repository; Connect a cluster (agent); New snippet; Repository graph; Milestones; GitLab Duo Chat Section. Some select or dropdown controls are missing visible labels, so the information or selection expected before interacting with each control cannot be understood. This occurs on the following pages: Notifications; Payment method; Pipelines; Members; Issues list; Test cases; Package registry; Model registry; Issues Open tab; Package registry; Requirements; Container Registry; Container Detail; Terraform modules; Requirements; Issue Analytics; Vulnerability report; Repository graph; GitLab Duo Chat Section. Some required fields are not identified as required by each field's labels, in its form's general instructions, or by an error message that indicates that the field is not completed, so people cannot determine that each field is required. This occurs on the following pages: Create new model; New test case.
3.3.7 Redundant Entry (Level A 2.2 only) EN 301 549 Criteria - Does not apply Revised Section 508 - Does not applyWeb: SupportsWeb: 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.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 SupportWeb: The name, role, state, and/or value of most, if not all, user interface components cannot be programmatically determined. The following issues exist: Multiple form input elements do 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 each element and may not understand its purpose or how to interact with it. This occurs on the following pages: Artifacts; Package registry; New on demand scan; Subscription Details; Create a new release; Customers Portal_Subscriptions & purchases. Multiple links do 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 each link. This occurs on the following pages: Snippet detail; Pipelines; Commit detail; Terraform modules; Repository Settings. Multiple buttons do not have a programmatic name, so each button's name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs in the following pages: Customers Portal_Subscriptions & purchases; Customers Portal_GitLab credits dashboard; Subscription Details; Customer information; Payment method; Customers Portal_Billing account settings; Model registry; Terraform modules; Pipelines; Terraform states; General; Security configuration - Security testing tab; Customers Portal_Billing account settings. 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 in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template. The content of multiple tooltips 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 pages: Value Stream Analytics; Analytics dashboard detail; Security configuration - Security testing tab; New on demand scan; Repository Analytics; Issue Analytics; Insights; Contributor analytics; Security dashboard; Repository Analytics; Insights; Security dashboard; Repository Settings; Requirements; New agent; Issue analytics; Releases; Commit detail; Issues - Open tab; Customers Portal_Subscriptions & purchases; Kubernetes Cluster; CI/CD analytics; Pipeline editor; Security dashboard; Pipelines; Issues list; Repository graph. Multiple elements that appear and function like a combo box do 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 each element or how to interact with it. This occurs on the following pages: New trigger; Jobs; Requirements; Vulnerability report; Issue Analytics; Code Review Analytics; Test cases; Issues list; Package registry; Model registry; Issue Boards; Commits; Value Stream Analytics. Multiple elements have an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Commits; Requirements; New snippet; Model registry; Create wiki page; Create a new release; Create new model; New test case. Elements that are focusable or contain one or more focusable elements are 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 elements. This occurs in the following pages: Customers Portal_Subscriptions & purchases; Customers Portal_Billing account settings; Issue Boards. Multiple elements do not have an attribute in their 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 pages: Snippets; Commits; Snippet detail; Merge requests. 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: Profile. 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: Value Stream Analytics. The HTML code for some links or buttons is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of these elements. This occurs on the following pages: Issues list; New on demand scan; Model registry; Usage quotas; Snippet detail. An element that appears and functions like a progress bar that dynamically indicates the progress status for a process 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 progress bar's name or purpose or the current state of the process. This occurs on the following page: Subscription Details; Customer Information; Payment Method. Multiple form fields are missing 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 each form field or what input it requires. This occurs on the following pages: Merge Requests Settings; Branches; Create a new release; Customers Portal_Subscriptions & purchases; New on demand scan; Web Hooks. Multiple buttons do not have a programmatic role, so each button's role (usually button, but sometimes link or something else) is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: New agent; Profile; Vulnerability report; Artifacts; Jobs; Requirements; Vulnerability report; Issue Analytics; Code Review Analytics; Test cases; Issues list; Package registry; Model registry; Issue Boards; Jobs; Requirements; New on demand scan; Requirements; Policies; Issues list; Audit events. When some buttons are pressed, their 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 buttons are pressed. This occurs on the following pages: Repository Analytics; Insights; Security dashboard; Issue Boards. A set of form controls (such as a set of radio buttons or related checkboxes) are grouped programmatically but have no programmatic group label, 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 controls in the group or what input they require. This occurs on the following page: Repository. Multiple buttons do not have a programmatic role and name, so each button's 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 pages: Repository Analytics; Insights; Security dashboard; Contributor analytics; Run new pipeline; Repository Graph; Compare Revisions; Run New pipeline; Pipeline editor; Contributor analytics; New Tag; Repository settings; New flow; Flow detail; Pipeline Editor; Analytics dashboard detail; Value Stream Analytics; Security dashboard; Repository Settings; Schedule new pipeline; Issue analytics; New Label. A custom select does not have a role and/or a state (such as which options are available and/or which option is currently selected) that are 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 available options, and which option is selected. This occurs on the following page: Insights. An element is missing or has an incorrect programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of the element and may not understand its purpose or content or how to interact with it. This occurs on the following page: Releases. For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Customers Portal_Subscriptions & purchases; Customers Portal_Billing account settings; Members; Value Stream Analytics; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Configure feature flags modal; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Keyboard Shortcuts dialog; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New issue; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform init command dialog; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Commit detail; Issue Boards; GitLab Duo Chat Section; Issues list; Labels - All tab; Repository; Homepage; Activity - All Tab; CI/CD analytics; Create a new release; Snippet detail; Branches; Edit Profile; Audit events; Snippets. The programmatic state of some elements that reveal or hide 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 each element or the state will be misrepresented. This occurs in the following pages: Members; Value Stream Analytics; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Configure feature flags modal; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Keyboard Shortcuts dialog; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New issue; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform init command dialog; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Pipeline editor; GitLab Duo Chat Section; New flow; Flow detail; Pipeline Editor; Issue Analytics; Code Review Analytics; Test cases; Issues list; Package registry; Model registry; Jobs; Requirements; Pipelines; Commits; Create a new release; Value Stream Analytics; New on demand scan; Vulnerability report; Artifacts; Releases; Commit detail; Submit vulnerability; Create wiki page; New Label; Snippet detail.

·Table 2: Success Criteria, Level AA

CriteriaConformance LevelRemarks and Explanations
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria 9.1.2.4 (Web) 10.1.2.4 (Non-web document) 11.1.2.4 (Open Functionality Software) 11.1.2.4 (Closed Software) 11.8.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs) Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)Web: Not ApplicableWeb: 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 ApplicableWeb: 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 applyWeb: SupportsWeb: 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 (Open Functionality Software) 11.1.3.5 (Closed Software) 11.8.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs) Revised Section 508 - Does not applyWeb: Partially SupportsWeb: The purpose of most input fields that collect an individual's personal data is programmatically defined based on the WCAG list of Input Purposes for User Interface Components. The following exception exists: No programmatic purpose is provided for some input elements (like text input fields), so browsers or assistive technology are not able to automatically suggest information to fill in the inputs. This occurs on the following pages: Customers Portal_Billing account settings; Payment method; Edit Profile; Email address.
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 SupportsWeb: 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 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 in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Issues - Open tab; General; Repository graph; Preferences; Customers Portal_Billing account settings; Members; New agent; New on demand scan; Snippet detail; Subscription Details; GitLab Duo Chat Section; Issue Analytics; Code Review Analytics; Test cases; Issues list; Package registry; Model registry; Customers Portal_Subscriptions & purchases; Customers Portal_GitLab credits dashboard; Subscription Details; Customer information; Payment method; Customers Portal_Billing account settings; Subscription Details; Customer information; Payment method; Flow detail; Issue Boards; New flow; Preferences; Issues - Open tab; Pipeline editor; Issues list; Security configuration - Security testing tab; Labels - All tab; Test cases. The color contrast ratios on hover or focus between the text labels of some controls and their background are less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of each control. This occurs on the following pages: New flow; Flow detail; Pipeline editor; Homepage; Snippet detail. 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 in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template.
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 SupportsWeb: 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 pages: General; Code review analytics; Repository graph; New flow; Repository; Branches; Issue analytics; Vulnerability report. Functionality is lost when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to this functionality. This occurs on the following pages: Branches; Usage quotas - Storage tab; Audit events; New flow; Commit detail; Create a new release; GitLab Duo Chat Section; Issue analytics; Vulnerability report; Snippet detail.
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: SupportsWeb: When content can be presented visually using only text, an image of text is not used to present that text.
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.1 (Open Functionality Software) 11.1.4.10.2 (Closed Software) 11.8.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs) Revised Section 508 - Does not applyWeb: Partially SupportsWeb: 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 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 pages: Connect a cluster (agent); General; Code review analytics; Snippet detail; Create a new release; Branches; Commits; Repository; Integrations. 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 pages: New on demand scan; Branches; Analytics dashboard detail; New feature flag; Pipelines; Value Stream Analytics; Audit events; Test cases; Issues list; Snippets; Commit detail; Milestones; Repository graph; Container detail; Vulnerability report; Usage quotas - Storage tab; On Demand Scans; New user list; Repository Settings; Compare revisions; New agent; Issue Boards; New flow; Terraform modules; Security dashboard; Issues - Open tab; GitLab Duo Chat Section; Pipeline detail; Releases; Flow detail.
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 applyWeb: Does Not SupportWeb: Most, if not all, boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content do not have a 3:1 color contrast ratio with adjacent color(s) or their background. The following issues exist: The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs in the following Pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Configure feature flags modal; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Keyboard Shortcuts dialog; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New issue; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform init command dialog; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Repository Analytics; Insights; Security dashboard; Contributor analytics; New Label; Preferences; Edit Profile. The focus indicators of some interactive elements (like buttons or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when each interactive element is receiving focus. This occurs on the following pages: Submit vulnerability; Commit detail; Terraform states; Issue analytics. The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements. This occurs in the following Pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Customers Portal_Subscriptions & purchases; Customers Portal_Billing account settings; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Members; Value Stream Analytics; Commit detail; Snippet detail; Policies; Audit events; CI/CD analytics; New test case. Some images or graphics (like a chart) or parts of the image/graphic required to understand its content do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by the image/graphic. This occurs in the following Pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Members; New flow; Flow detail; Pipeline editor; Issue Analytics; Code Review Analytics; Test cases; Issues list; Package registry; Model registry; Issue Boards; Value stream analytics; Issue Boards; Jobs; Merge requests; Issues list; Agents; Flows; Analytics dashboard detail; Kubernetes Cluster; Repository analytics; Issues - Open tab; CI/CD analytics; Repository graph; Snippet detail; Usage quotas - Storage tab; Create wiki page. Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon. This occurs on the following pages: Issues - Open tab; Profile; Jobs; Edit Profile; New test case.
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 applyWeb: Partially SupportsWeb: For most content, the spacing between letters, words, lines of text, and paragraphs can be adjusted with no loss of content or functionality. The following exceptions exist: When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: Jobs; Repository graph; Repository; Labels - All tab; Security dashboard. When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, the spacing for some or all text on the page does not adjust. This occurs on the following page: Payment method.
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 applyWeb: Does Not SupportWeb: In most, if not all, cases when additional content is triggered by pointer hover or keyboard focus, that additional content cannot be dismissed and hovered over, and the content does not persist until the user dismisses it. The following issues 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 in the following Pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Configure feature flags modal; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Keyboard Shortcuts dialog; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New issue; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform init command dialog; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Subscription Details; Customer information; Payment method; Issues list; Customers Portal_Billing account settings; Customers Portal_Subscriptions & purchases; Container registry; Repository; Run new pipeline; Repository Graph; Pipeline editor; Contributor analytics; Repository settings; Requirements; GitLab Duo Chat Section; Repository graph; New on demand scan. 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 in the following Pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Repository graph; Pipeline detail; SSH keys; Customers Portal_GitLab credits dashboard; Repository Analytics; Insights; Contributor analytics; Security dashboard; Container registry; Issue analytics; Analytics dashboard detail; CI/CD analytics.
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria 9.2.4.5 (Web) 10.2.4.5 (Non-web document) - Does not apply 11.2.4.5 (Open Functionality Software) - Does not apply 11.2.4.5 (Closed Software) - Does not apply 11.8.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs) Revised Section 508 501 (Web)(Software) - Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) - Does not apply to non-web docsWeb: SupportsWeb: 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: Does Not SupportWeb: Headings and/or labels for form and interactive controls are not informative. The following issues exist: Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs on the following pages: Repository; Merge requests; General; Members; Container detail; Container registry; New on demand scan; Audit events; Comment templates; Kubernetes Cluster; Customers Portal_Billing account settings; New agent; Jobs; Requirements; Vulnerability report; Code Review Analytics; Test cases; Issues list; Package registry; Model registry; Issue Boards; Terraform modules; Commits; Value Stream Analytics; Members; Subscription Details; Payment Method; Repository Settings; Create a new release; Package registry; On Demand Scans; Jobs; Commit detail; Issue Boards; Notifications; Submit vulnerability; Compare revisions; Schedule new pipeline; New snippet; Artifacts; New feature flag; Iterations; Issues - Open tab; Access tokens; Run new pipeline; Terraform init command dialog; Milestones; Branches; Web Hooks; Issues list; Merge Requests Settings; Requirements; Customers Portal_Subscriptions & purchases; Labels - All tab; Snippet detail. A label for a control or form input field does not convey the purpose of the control or input, so users may not understand what the control does or what data to enter, especially people with cognitive or learning disabilities and people who are blind and/or use a screen reader. This occurs on the following page: Security configuration - Security testing tab. Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what a control does or what data to enter. This occurs in the following Pages: Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Policies; Vulnerability report; New on demand scan; Payment method; New Tag; SSH keys; Container detail; Edit Profile; Create merge request; Repository Settings; Profile; Configure feature flags modal; Customers Portal_GitLab credits dashboard; Merge Requests Settings; Integrations; Create a new release; Issue Boards; Submit vulnerability; Notifications; Audit events; New value stream; Homepage; Value Stream Analytics; GitLab Duo Chat Section; New trigger; Commit detail; Customers Portal_Billing account settings; Snippets; Issues list; Test cases; Issues - Open Tab; Code Review Analytics; Jobs; Requirements; Vulnerability report; Issue Analytics; Code Review Analytics; Test cases; Issues list; Package registry; Model registry; Issue Boards; Commits; Value Stream Analytics.
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 SupportsWeb: In most cases, it is visually apparent which page element is currently receiving keyboard focus. The following exceptions exist: Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs on the following pages: Repository; Snippet detail; Tags; Create wiki page; Help; Audit events; New on demand scan; SSH keys; Commits. The visual focus indicator for an interactive element (such as a link, button, or form input) is not visible, 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: Repository.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) EN 301 549 Criteria - Does not apply Revised Section 508 - Does not applyWeb: Partially SupportsWeb: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. The following exception exists: Multiple focused elements are 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 pages: Account; Repository; Edit Profile; Merge Requests Settings; Email address; Preferences.
2.5.7 Dragging Movements (Level AA 2.2 only) EN 301 549 Criteria - Does not apply Revised Section 508 - Does not applyWeb: Partially SupportsWeb: 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 exception exists: 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. This occurs on the following pages: Issue Boards; Repository Analytics; Insights; Security dashboard; Contributor analytics.
2.5.8 Target Size (Minimum) (Level AA 2.2 only) EN 301 549 Criteria - Does not apply Revised Section 508 - Does not applyWeb: Partially SupportsWeb: 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 in line 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: Multiple target hit areas do not meet a 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 in the following Pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Issues - Open tab; New milestone; Pipelines; Usage quotas; Issues list; Jobs; Artifacts; Issue Boards; Commit detail; Repository; Branches; Web Hooks; Usage quotas - Storage tab; Tags; New on demand scan; Agents; Flows.
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: SupportsWeb: 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.
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 docsWeb: SupportsWeb: 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 docsWeb: SupportsWeb: Labels, names, and/or 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: SupportsWeb: If input errors are automatically detected, suggestions are provided in text for correcting the input in a timely and accessible manner before the data is submitted to the server.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria 9.3.3.4 (Web) 10.3.3.4 (Non-web document) 11.3.3.4 (Open Functionality Software) 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: SupportsWeb: 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 applyWeb: SupportsWeb: 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 website.
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) - Does not apply 11.4.1.3 (Open Functionality Software) - Does not apply 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 applyWeb: Does Not SupportWeb: Most, if not all, status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist: Some status messages are not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status messages, or they may not hear them in a timely fashion. This occurs in the following pages: New milestone; Create wiki page; Requirements; Commit detail; New snippet; Snippet detail; New test case; Submit vulnerability; Create a new release; Create new model; Create an environment; Add new comment template; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Configure feature flags modal; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Keyboard Shortcuts dialog; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New issue; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform init command dialog; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Access tokens; Account; Activity - All Tab; Add new comment template; Agent detail; Agents; Analytics dashboard detail; Analytics dashboards; Artifacts; Audit events; Branches; CI/CD; CI/CD analytics; Code review analytics; Comment templates; Commit detail; Commits; Compare revisions; Connect a cluster (agent); Container detail; Container registry; Contributor analytics; Create a Kubernetes cluster; Create a new release; Create an environment; Create merge request; Create new model; Create using MLFlow modal; Create wiki page; Customer information; Customers Portal_Billing account settings; Customers Portal_GitLab credits dashboard; Customers Portal_Sign in; Customers Portal_Subscriptions & purchases; Edit Profile; Email address; Environments; Feature flags; Flow detail; Flows; General; GitLab Duo Chat Section; Help; Homepage; Insights; Integrations; Issue analytics; Issue Boards; Issues - Open tab; Issues list; Iterations; Jobs; Kubernetes Cluster; Labels - All tab; Members; Merge requests; Merge Requests Settings; Milestones; Model registry; New agent; New feature flag; New flow; New Label; New milestone; New on demand scan; New snippet; New Tag; New test case; New trigger; New user list; New value stream; Notifications; On Demand Scans; Package registry; Packages and registries; Password; Payment method; Pipeline detail; Pipeline editor; Pipelines; Policies; Preferences; Profile; Releases; Repository; Repository analytics; Repository graph; Repository Settings; Requirements; Run new pipeline; Schedule new pipeline; Security configuration - Security testing tab; Security dashboard; Snippet detail; Snippets; SSH keys; Submit vulnerability; Subscription Details; Tags; Terraform modules; Terraform states; Test cases; Triggers; Usage quotas; Usage quotas - Storage tab; Value Stream Analytics; Vulnerability report; Web Hooks; Issues list; Issues - Open tab; Issue Boards; Requirements; Branches; Pipelines; Jobs; Test cases; Audit events; Package registry; Container detail; Model registry; Code review analytics; Issue analytics; Integrations; Web Hooks; Access tokens; Repository; Merge Requests; CI/CD; Packages and registries; Account; Email address; Notifications; SSH keys; Preferences; Subscription Details; Customer information; Payment method; SSH keys; Customers Portal_Subscriptions & purchases; Agents; Flows; Analytics dashboard detail; Package registry; Create merge request; General; Kubernetes Cluster; Test cases; Jobs; Access tokens; Terraform Modules; Preferences; Container Registry; Issue Analytics; commit Detail; Envionrments; New Issue; New agent; New flow; New value stream; Issue Boards; Merge Requests; Pipeline editor; Flow detail; New Flow; Pipeline Editor; Vulnerability report; New on demand scan; Requirements; Issues list; Notifications; Container registry; Container detail; Code Review Analytics; Model registry; Pipeline detail; Pipelines; Compare revisions; Commit; Policies; Create a new release; Create an environment; Repository settings; Run new pipeline; Repository Graph; Compare Revisions; Contributor analytics; New Tag; New Feature Flag; Members; Schedule new pipeline; Repository; Merge requests; Milestones; Repository (Activate Code menu-> Activate Copy button and copy button from the Actions menu); Terraform init command dialog; Terraform modules; Configure feature flags modal; Snippet detail; Connect a cluster (agent); Company Information; Payment Method; Account; Create wiki page; Profile; Security configuration - Security testing tab; New snippet; Requirements; Edit Profile; Repository Settings; Model registry; New test case; Value Stream Analytics; Connect a cluster (agent); Customers Portal_Billing account settings; Vulnerability report; Merge Requests Settings; Package registry; New trigger; Web Hooks; Container detail; GitLab Duo Chat Section; Snippet detail; Issues list; New user list; New on demand scan; Members; Labels - All tab; Policies; Submit vulnerability; General; New Label; Keyboard Shortcuts dialog; Code review analytics; Commit detail; Issue Boards; Preferences; Pipelines; Subscription Details; Artifacts; Activity - All Tab.

·Table 3: Success Criteria, Level AAA

·Notes: Not Applicable. Website was not audited for WCAG 2.2 AAA conformance.

·Revised Section 508 Report

·Chapter 3: Functional Performance Criteria (FPC)

CriteriaConformance LevelRemarks and Explanations
302.1 Without VisionWeb: Partially SupportsWeb: Most functionality is usable without vision. Exceptions are noted in: 1.1.1 Non-text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 2.1.1 Keyboard 2.1.2 No Keyboard Trap 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.2.2 On Input 3.3.1 Error Identification 4.1.2 Name, Role, Value
302.2 With Limited VisionWeb: Partially SupportsWeb: Most functionality is usable with limited vision. Exceptions are noted in: 1.1.1 Non-text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 1.4.3 Contrast (Minimum) 1.4.4 Resize text 2.1.1 Keyboard 2.1.2 No Keyboard Trap 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.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 ColorWeb: Partially SupportsWeb: 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 HearingWeb: Partially SupportsWeb: Most functionality is usable without hearing. Exceptions are noted in: 3.1.1 Language of Page
302.5 With Limited HearingWeb: Partially SupportsWeb: Most functionality is usable with limited hearing. Exceptions are noted in: 3.1.1 Language of Page
302.6 Without SpeechWeb: SupportsWeb: All functionality is usable without speech.
302.7 With Limited ManipulationWeb: Partially SupportsWeb: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions are noted in: 2.1.1 Keyboard 2.1.2 No Keyboard Trap 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 StrengthWeb: SupportsWeb: All functionality is usable with limited reach and strength.
302.9 With Limited Language, Cognitive, and Learning AbilitiesWeb: Partially SupportsWeb: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions are noted in: 1.1.1 Non-text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.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 2.4.7 Focus Visible 3.1.1 Language of Page 3.2.2 On Input 3.3.1 Error Identification 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value

·Chapter 4: Hardware

·Notes: The ICT covered by this report is not hardware. As such, the requirements of this chapter do not apply.

·Chapter 5: Software

CriteriaConformance LevelRemarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASee WCAG 2.2 sectionSee information in WCAG 2.2 section
502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesWeb: Not ApplicableWeb: The website or application is not platform software, so this requirement does not apply.
502.2.2 No Disruption of Accessibility FeaturesWeb: Not ApplicableWeb: The website or application is not platform software, so this requirement does not apply
502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationWeb: Partially SupportsWeb: The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions are noted in: 4.1.2 Name, Role, Value
502.3.2 Modification of Object InformationWeb: Partially SupportsWeb: 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 Rows, Column, and HeadersWeb: Partially SupportsWeb: 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 ValuesWeb: Partially SupportsWeb: For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions are noted in: 4.1.2 Name, Role, Value
502.3.5 Modification of ValuesWeb: Partially SupportsWeb: For most objects that allow the user to set or modify their value, the act of setting a value 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.6 Label RelationshipsWeb: Partially SupportsWeb: 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 RelationshipsWeb: Partially SupportsWeb: 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 TextWeb: Partially SupportsWeb: Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions are noted in: 1.3.1 Info and Relationships
502.3.9 Modification of TextWeb: SupportsWeb: 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 ActionsWeb: SupportsWeb: When one or more actions may be performed on an element, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology.
502.3.11 Actions on ObjectsWeb: Partially SupportsWeb: 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 are noted in: 2.1.1 Keyboard
502.3.12 Focus CursorWeb: Partially SupportsWeb: On most pages, 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. Exceptions are noted in: 2.4.7 Focus Visible
502.3.13 Modification of Focus CursorWeb: SupportsWeb: When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology.
502.3.14 Event NotificationWeb: Partially SupportsWeb: In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions are noted in: 4.1.3 Status Messages
502.4 Platform Accessibility FeaturesWeb: Not ApplicableWeb: The website or application is not platform software, so this requirement does not apply.
503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesWeb: Not ApplicableWeb: The website or application is not platform software, so this requirement does not apply
503.3 Alternative User InterfacesWeb: Not ApplicableWeb: The website or application does not offer an alternative user interface.
503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsWeb: Not ApplicableWeb: The website or application does not contain media with an audio component that has closed captions.
503.4.2 Audio Description ControlsWeb: Not ApplicableWeb: The website or application does not contain media with a video component that offers audio descriptions.
504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingSee WCAG 2.2 sectionSee information in WCAG 2.2 section
504.2.1 Preservation of Information Provided for AccessibilityWeb: Not ApplicableWeb: The website or application is not an authoring tool.
504.2.2 PDF ExportWeb: Not ApplicableWeb: The website or application is not an authoring tool.
504.3 PromptsWeb: Not ApplicableWeb: The website or application is not an authoring tool.
504.4 TemplatesWeb: Not ApplicableWeb: The website or application is not an authoring tool.

·Chapter 6: Support Documentation and Services

CriteriaConformance LevelRemarks and Explanations
601 ScopeHeading cell - no response requiredHeading cell - no response required
602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesWeb: Not ApplicableWeb: Documentation is not provided for the website or application.
602.3 Electronic Support DocumentationSee WCAG 2.2 sectionSee information in WCAG 2.2 section
602.4 Alternate Formats for Non-Electronic Support DocumentationWeb: Not ApplicableWeb: Documentation is not provided for the website or application.
603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesWeb: Not ApplicableWeb: Support services are not provided for the website or application.
603.3 Accommodation of Communication NeedsWeb: Not ApplicableWeb: Support services are not provided for the website or application.

·EN 301 549 Report

4Clause 4: Functional Performance Statements (FPS)

CriteriaConformance LevelRemarks and Explanations
4.2.1 Usage without visionWeb: Partially SupportsWeb: Most functionality is usable without vision. Exceptions are noted in: 1.1.1 Non-text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 2.1.1 Keyboard 2.1.2 No Keyboard Trap 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.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 visionWeb: Partially SupportsWeb: Most functionality is usable with limited vision. Exceptions are noted in: 1.1.1 Non-text Content 1.3.5 Identify Input Purpose 1.4.1 Use of Color 1.4.3 Contrast (Minimum) 1.4.4 Resize text 1.4.10 Reflow 1.4.11 Non-text Contrast 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.1.2 No Keyboard Trap 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.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 colourWeb: Partially SupportsWeb: 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 hearingWeb: Partially SupportsWeb: Most functionality is usable without hearing. Exceptions are noted in: 2.2.1 Timing Adjustable
4.2.5 Usage with limited hearingWeb: Partially SupportsWeb: Most functionality is usable with limited hearing. Exceptions are noted in: 2.2.1 Timing Adjustable
4.2.6 Usage with no or limited vocal capabilityWeb: SupportsWeb: All functionality is usable without speech or other vocal output.
4.2.7 Usage with limited manipulation or strengthWeb: Partially SupportsWeb: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions are noted in: 2.1.1 Keyboard 2.1.2 No Keyboard Trap 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 3.2.2 On Input 4.1.2 Name, Role, Value
4.2.8 Usage with limited reachWeb: Partially SupportsWeb: Most functionality is usable by people with limited reach. Exceptions are noted in: 2.5.3 Label in Name
4.2.9 Minimize photosensitive seizure triggersWeb: SupportsWeb: 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 learningWeb: Partially SupportsWeb: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions are noted in: 1.3.5 Identify Input Purpose 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 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.2.2 On Input 3.3.1 Error Identification 3.3.2 Labels or Instructions 4.1.3 Status Messages
4.2.11 PrivacyWeb: SupportsWeb: Where the product provides features for accessibility, it maintains the privacy of people who use these features at the same level as other users.

5Clause 5: Generic Requirements

CriteriaConformance LevelRemarks and Explanations
5.1 Closed functionalityHeading cell - no response requiredHeading cell - no response required
5.1.2 GeneralHeading cell - no response requiredHeading cell - no response required
5.1.2.1 Closed functionalitySee 5.2 through 13See information in 5.2 through 13
5.1.2.2 Assistive technologySee 5.1.3 through 5.1.6See information in 5.1.3 through 5.1.6
5.1.3 Non-visual accessHeading cell - no response requiredHeading cell - no response required
5.1.3.1 Audio output of visual informationWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.2 Auditory output delivery including speechWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.3 Auditory output correlationWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.4 Speech output user controlWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.5 Speech output automatic interruptionWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.6 Speech output for non-text contentWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.7 Speech output for video informationWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.8 Masked entryWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.9 Private access to personal dataWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.10 Non-interfering audio outputWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.11 Private listening volumeWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.12 Speaker volumeWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.13 Volume resetWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.14 Spoken languagesWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.15 Non-visual error identificationWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.3.16 Receipts, tickets, and transactional outputsWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.4 Functionality closed to text enlargementWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.5 Visual output for auditory informationWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.6 Operation without keyboard interfaceHeading cell - no response requiredHeading cell - no response required
5.1.6.1 Closed functionalitySee 5.1.3.1 through 5.1.3.16See information in 5.1.3.1 through 5.1.3.16
5.1.6.2 Input focusWeb: Not ApplicableWeb: The product does not have closed functionality.
5.1.7 Access without speechWeb: Not ApplicableWeb: The product does not have closed functionality.
5.2 Activation of accessibility featuresWeb: Not ApplicableWeb: The application does not provide any accessibility features which are part of the web pages.
5.3 BiometricsWeb: Not ApplicableWeb: The website does not use biometric forms of user identification or control. All functionality is accessible through standard input methods (keyboard, mouse, UI).
5.4 Preservation of accessibility information during conversionWeb: Not ApplicableWeb: The product does not convert content.
5.5 Operable partsHeading cell - no response requiredHeading cell - no response required
5.5.1 Means of operationWeb: Not ApplicableWeb: 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 discernibilityWeb: Not ApplicableWeb: 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.6 Locking or toggle controlsHeading cell - no response requiredHeading cell - no response required
5.6.1 Tactile or auditory statusWeb: Not ApplicableWeb: Tactile or auditory status is not included in the product.
5.6.2 Visual statusWeb: Not ApplicableWeb: Visual status of controls isn't discernible in the product
5.7 Key repeatWeb: Not ApplicableWeb: Key repeat functionality is not found in the product.
5.8 Double-strike key acceptanceWeb: Not ApplicableWeb: Double-strike key acceptance is not found in the product.
5.9 Simultaneous user actionsWeb: Not ApplicableWeb: The product does not require simultaneous user actions for core functionality. All actions triggered by key combinations are also available via the graphical user interface using mouse or sequential keyboard navigation.

6Clause 6: ICT with Two-Way Voice Communication

·Notes: The ICT covered by this report does not have any functionality that supports two-way communication. As such, the requirements of this chapter do not apply.

7Clause 7: ICT with Video Capabilities

CriteriaConformance LevelRemarks and Explanations
7.1 Caption processing technologyHeading cell - no response requiredHeading cell - no response required
7.1.1 Captioning playbackWeb: Not ApplicableWeb: The website or application does not contain video that has synchronized audio.
7.1.2 Captioning synchronizationWeb: Not ApplicableWeb: The website or application does not contain video that has synchronized audio.
7.1.3 Preservation of captioningWeb: Not ApplicableWeb: The website or application does not transmit, convert, or record video that has synchronized audio.
7.1.4 Captions characteristicsWeb: Not ApplicableWeb: The website or application does not contain video that has synchronized audio.
7.1.5 Spoken subtitlesWeb: Not ApplicableWeb: The website or application does not contain video that has synchronized audio.
7.2.1 Audio description playbackWeb: Not ApplicableWeb: The website or application does not contain video that has synchronized audio.
7.2.2 Audio description synchronizationWeb: Not ApplicableWeb: The website or application does not contain video that has synchronized audio.
7.2.3 Preservation of audio descriptionWeb: Not ApplicableWeb: The website or application does not transmit, convert, or record video that has synchronized audio.
7.3 User controls for captions and audio descriptionWeb: Not ApplicableWeb: The website or application does not contain media with an audio component that has closed captions or media with a video component that has audio description.

8Clause 8: Hardware

·Notes: The ICT covered by this report is not hardware. As such, the requirements of this clause do not apply.

9Clause 9: Web (see WCAG 2.2 section)

10Clause 10: Non-web Documents

·Notes: The ICT covered by this report does not include non-web documents. As such, the requirements of this chapter do not apply.

11Clause 11: Software

·Notes: The ICT covered by this report is a web application, its accessibility requirements are covered in Chapter 9 and by reference the WCAG 2.2 section. As such, the requirements of this chapter do not apply

12Clause 12: Documentation and Support Services

CriteriaConformance LevelRemarks and Explanations
12.1 Product documentationHeading cell - no response requiredHeading cell - no response required
12.1.1 Accessibility and compatibility featuresWeb: Not ApplicableWeb: Documentation is not provided for the website or application.
12.1.2 Accessible documentationSee WCAG 2.2 sectionSee information in WCAG 2.2 section
12.2 Support ServicesHeading cell - no response requiredHeading cell - no response required
12.2.2 Information on accessibility and compatibility featuresWeb: Not ApplicableWeb: Support services are not provided for the website or application.
12.2.3 Effective communicationWeb: Not ApplicableWeb: Support services are not provided for the website or application.
12.2.4 Accessible documentationSee WCAG 2.2 sectionSee information in WCAG 2.2 section

13Clause 13: ICT Providing Relay or Emergency Service Access

·Notes: The ICT covered by this report does not have any function that supports two-way communication, including the provision of relay services or access to emergency services. As such, the requirements of this chapter do not apply.

·Legal Disclaimer (GitLab)

·This document is provided for information purposes only and the contents hereof are subject to change without notice. GitLab does not warrant that this document is error-free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. GitLab specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Any modification or customization to the subject product may render some or all of this document to become inapplicable. Determination of compliance with applicable accessibility requirements is the sole responsibility of the purchaser. GitLab further makes no representation concerning the ability of assistive technologies or other products to interoperate with GitLab products. This document addresses the named product(s) only and not prerequisite products for which GitLab supplies restricted use licenses.

·Last updated at: Thursday, August 13, 2026 at 6:21 PM