| stage | group | info |
|---|---|---|
none |
unassigned |
Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review. |
Accessibility is important for users who use screen readers or rely on keyboard-only functionality to ensure they have an equivalent experience to sighted mouse users.
You can enable linting for accessibility defects with a free VS Code plugin - axe Accessibility Linter. We strongly recommend that to everyone contributing to GitLab that use VS Code.
- Open VS Code editor
- Go to Extensions
- Search for axe Accessibility Linter and install the plugin
Axe Accessibility Linter works in HTML, Markdown and Vue files. As for this moment, there is no support for HAML files. You will get immediate feedback, while writing your code.
GitLab repository contains axe-linter.yml file that adds additional configuration to the plugin.
It enables the linter to analyze some of the Pajamas components by mapping them and their attributes to native HTML elements.
Uncover accessibility problems and ensure that your features stay accessible over time by implementing automated A11Y tests.
Follow these best practices to implement accessible web applications. These are some of the topics covered in that guide:
Use these tools and learning resources to improve your web accessibility workflow and skills.
We have two options for Web accessibility testing:
- The A11Y Project is a good resource for accessibility
- Awesome Accessibility is a compilation of accessibility-related material