-
-
Notifications
You must be signed in to change notification settings - Fork 116
Linter: Implement a11y-no-visually-hidden-interactive-elements rule #1225
Copy link
Copy link
Open
Labels
a11yAccessibility linter rules and concernsAccessibility linter rules and concernserb-lintParity with the erb_lint and erblint-github gemsParity with the erb_lint and erblint-github gemslinter@herb-tools/linter for HTML+ERB templates@herb-tools/linter for HTML+ERB templateslinter-ruleIndividual linter rules and their documentationIndividual linter rules and their documentation
Description
Metadata
Metadata
Assignees
Labels
a11yAccessibility linter rules and concernsAccessibility linter rules and concernserb-lintParity with the erb_lint and erblint-github gemsParity with the erb_lint and erblint-github gemslinter@herb-tools/linter for HTML+ERB templates@herb-tools/linter for HTML+ERB templateslinter-ruleIndividual linter rules and their documentationIndividual linter rules and their documentation
Implement the
GitHub::Accessibility::NoVisuallyHiddenInteractiveElementsrule fromerblint-github.Rule Details
This rule guards against visually hiding interactive elements. If a sighted keyboard user navigates to an interactive element that is visually hidden they might become confused and assume that keyboard focus has been lost.
Note:
inputelements are not flagged at this time as some visually hidden inputs might cause false positives (e.g. file inputs).Examples
Incorrect code for this rule:
Correct code for this rule:
References
Parent Issue
erblint-githubcompatibility/parity #1205