Show accessibility issues in review app post scan

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

As a developer reviewing front end changes, I want to see where accessibility issues may appear/toggle problems that may be sight related, so I can more easily identify and fix issues for our users.

Intended users

• Sasha (Software Developer) - who is using a review app, runs our accessibility scan and can't figure out where an accessibility is/how bad it is from the report.
• Parker (Product Manager) - who wants their app to be more accessible for users and wants to see the impact without loading up a bunch of browser plugins or loading the site in a different tool
• Simone (Software Engineer in Test) - who is validating accessibility requirements and wants to do it as efficiently as possible.

User experience goal

The user should be able to use the UI (review app) to see accessibility issues.

Proposal

• Take information from the accessibility report to identify where in the DOM an accessibility issue is.
• Inject into the app a visual indicator that this text/color/etc. is an accessibility issue
• Show details on hover/click/etc.
• Allow a user to toggle this off if they need to

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

GitLab Premium

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

TBD

What is the type of buyer?

Is this a cross-stage feature?

Yes this is cross stage with ~"devops::release" / ~"group::release" who manages most things Category:Review Apps related.

Links / references