Skip to content

Axe Accessibility Test for GlButton

Drew Cauchi requested to merge drewcauchi/gitlab-ui:2356-e2e-glbutton into main

What does this MR do?

Axe Accessibility Test for GlButton

  • Created e2e accessibility test for default button for all categories
  • Created e2e accessibility test for confirm button for all categories
  • Created e2e accessibility test for success button for all categories
  • Created e2e accessibility test for danger button for all categories
  • Created e2e accessibility test for all the mentioned in focus, hover and click states
  • Created e2e accessibility test for all the mentioned in disabled and selected states
  • Created e2e accessibility test for dropdown button with focus, hover, click and disabled states
  • Created e2e accessibility test for icon button with focus, hover, click and disabled states
  • Kept code as minimal and non-repetitive as much as possible

Integration merge requests

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.

Closes #2356 (closed)

Edited by Drew Cauchi

Merge request reports