Use of Color > Perform Audit > Verify
With &896, we will perform an audit of GitLab to ensure that we are following standard WCAG standards in terms of Use of Color.
1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)
Prep
Not all features are accessible on GitLab.com, such as the admin area. For this reason, it is helpful to set up your local environment in order to perform your audit. This will allow you to perform actions and simulate different interactions, such as form errors, success messages, etc. To get started:
-
Configure two local GitLab Development Kit instances -
Create a list detailing each page and/or area that relates to your individual stage group -
Ensure you are including features that may only be in higher tier subscriptions (EE codebase)
-
Audit
-
Using GDK (CE and EE), review each page/area to ensure that color is not solely used to: -
Convey information -
Indicate an action -
Prompt a response -
Distinguish a visual element
-
-
Create issues in either CE or EE, depending on whether it relates specifically to a higher tier feature. -
Attach it to the Verify sub-epic. If the issue expands across all of GitLab, attach it to the top-level epic if one does not already exist.
-
-
Determine a solution for each created issue -
Work with your PM to discuss found issues and schedule accordingly
Areas of interest
-
Pipelines List -
Pipelines Detail view -
General information -
Graph -
Test information -
Job list
-
-
Jobs List -
Jobs detail view -
Pipeline Schedules -
Pipeline Schedule detail view -
CI/CD charts -
Merge request widget -
Pipeline information -
Test information -
Pipeline list
-
-
Web ide pipeline information sidebar -
Web ide pipeline information bottombar -
Project settings -
CI/CD
-
-
Group settings -
CI/CD -
Webhooks -
Pipeline quota
-
-
Instance/admin settings -
Runners -
Runner detail view -
Jobs
-
-
Pipeline dashboard -
New project -
CI/CD pipelines for external repositories`
-
https://about.gitlab.com/features/#verify
Features from-
Gitlab ci -
Built-in and custom project templates -
Browser Performance Testing -
CI/CD for external repo -
CI/CD for GitHub -
See JUnit test summaries in merge request widget -
Junit test summaries mr widget -
Free CI/CD with shared or personal Runners -
CI/CD Horizontal Autoscaling -
CI/CD Pipelines Dashboard -
Online visualization of HTML artifacts -
Scheduled triggering of pipelines -
Code Quality -
Protected variables -
Group-level variables -
Customizable path for CI/CD configuration -
Run CI/CD jobs on Windows -
Run CI/CD jobs on macOS -
Run CI/CD jobs on Linux ARM -
Run CI/CD jobs on FreeBSD -
Show code coverage rate for your pipelines -
Protected Runners -
Minimal CI/CD configuration -
Automatic Retry for Failed CI Jobs -
Pipelines security -
Include external files in CI/CD pipeline definition -
Instance file templates -
Group file templates -
Run jobs only when there are changes to a file or path -
Run jobs only/except in the context of a merge request -
Pipeline deletion -
Explicit support for monorepos
https://colororacle.org/ is a helpful tool to utilize during the audit process. Change pages to greyscale to simulate an experience with no color. To help get you thinking, the following are some common problems (not necessarily related to GitLab):
- Text links have no visual cue other than color
- Required fields are only indicated by the use of red
- “Mary's sales are in red, Tom's are in blue"
- Using color to indicate that a database entry has been updated successfully
- Using highlighting on form fields to indicate that a required field had been left blankr