[axe-core] temporarily disable rule/warn for 'Focus Visible'

[neilpfeiffer]

Bug Report

Description

WCAG 2.1 (Level AA) introduced criterion 2.4.11: Focus Visible (Enhanced) which raises the WCAG 2 (Level A) 2.4.7: Focus Visible criterion standard of when a user interface element displays a visible keyboard focus that it's color contrast ratio be at least 3:1 or thickness of at least 2 CSS pixels.

All interactive terra elements have a visible keyboard focus style present, but not tested to see if they meet automated axe-core 4.0.0 testing for the 2.4.7 / 2.4.11 criterion. Until all terra components can be audited and updated to pass this criterion, for the interim, disabling the check and test failure for this rule, and switching to logging as a warning (if possible) needs to be added.

Solution

Until all terra components can be audited and updated to pass this criterion, for the interim, disabling the check and test failure for this rule, and switching to logging as a warning (if possible) needs to be added.

Related Issues

These issues will resolve updating each component to pass the rule, which then can be re-enabled.

• TODO: add other related issue numbers

.

Reference Context / Screenshots

Example: focus styling for terra-button does not meet the color contrast ratio or thickness rule when tested:

[ryanthemanuel]

We are going to update the axe core tests in terra-toolkit to be warn when appropriate as a part of #401. The thought is that we can use that functionality to warn in this type of scenario. Once this is unblocked by the work in #401 we can work on this issue.

[stale]

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed in seven days if no further activity occurs. Thank you for your contributions.