You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2024. It is now read-only.
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 testing for the 2.4.7 / 2.4.11 criterion. All components in tera-core need to be audited and provide updated styling as needed, as well as adding any appropriate additional tests for confirmation of pass/fail.
.
Solution
Audit, Add testing, and UX to provide appropriate changes to all components in terra-application
Components affected:
TODO: list out each component needing update here...
Feature Request
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 testing for the 2.4.7 / 2.4.11 criterion. All components in
tera-core
need to be audited and provide updated styling as needed, as well as adding any appropriate additional tests for confirmation of pass/fail..
Solution
Audit, Add testing, and UX to provide appropriate changes to all components in terra-application
Components affected:
Related Issues
Reference Context / Screenshots
see terra-core #3174 for reference screenshot
The text was updated successfully, but these errors were encountered: