Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46,626
    • Issues 46,626
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,530
    • Merge requests 1,530
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #218551
Closed
Open
Issue created May 20, 2020 by James Heimbuck@jheimbuck_gl☑Developer

Add more accessibility scanners to make a more comprehensive report

Problem to solve

Accessibility scanning is great but the current offering is limited, this leads to missed items in the existing scan.

Intended users

User experience goal

When an accessibility scan is run by GitLab, I want the result to be comprehensive/inclusive of serious issues, so that everyone can utilize my app / website.

Proposal

pa11y is just one scanner, there are others such as the offering from IBM and more as mentioned in the original implementation item.

We should investigate a few things:

  1. How do scans of the existing engine and alternative engine differ?
    • Content and readability of report
    • Speed of scan
  2. What would the level of effort be to combine reports from multiple scanners to a singular format for presentation in the UI?

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited Jan 05, 2022 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Time tracking