-
-
Notifications
You must be signed in to change notification settings - Fork 895
Labels
A-CLIArea: CLIArea: CLIA-LinterArea: linterArea: linterL-HTMLLanguage: HTML and super languagesLanguage: HTML and super languagesS-Help-wantedStatus: you're familiar with the code base and want to help the projectStatus: you're familiar with the code base and want to help the projectgood first issueGood for newcomersGood for newcomers
Description
Description
All lint rules that belong to a11y are applied only to JSX language. Now that our HTML linter is up and running, we can port those rules. Here's the list:
- noAccessKey
- noAriaHiddenOnFocusable
- noAriaUnsupportedElements
- noAutofocus feat(linter): add noAutofocus rule for HTML #8641
- noHeaderScope
- noInteractiveElementToNoninteractiveRole
- noLabelWithoutControl
- noNoninteractiveElementInteractions
- noNoninteractiveElementToInteractiveRole
- noNoninteractiveTabindex
- noPositiveTabindex feat(html/noPositiveTabindex): port noPositiveTabindex rule to HTML #8501
- noRedundantAlt feat(html): implement noRedundantAlt #8666
- noRedundantRoles
- noStaticElementInteractions
- noSvgWithoutTitle feat(lint/html): implement noSvgWithoutTitle for html #8412
- useAltText feat(html): add
useAltTexta11y rule #8661 - useAnchorContent feat(biome_html_analyze): implement useAnchorContent rule for HTML #8769
- useAriaActivedescendantWithTabindex
- useAriaPropsForRole feat(lint/html): implement useAriaPropsForRole for html #8381
- useAriaPropsSupportedByRole
- useFocusableInteractive
- useHeadingContent feat(html/a11y): port useHeadingContent rule to HTML #9262
- useHtmlLang feat(lint/html): add
useHtmlLang#8262 - useKeyWithClickEvents
- useKeyWithMouseEvents
- useMediaCaption feat(biome_html_analyze): add useMediaCaption rule for HTML #8742
- useSemanticElements
- useValidAnchor
- useValidAriaProps
- useValidAriaRole feat(lint/html): implement useValidAriaRole for html #8307
- useValidAriaValues
- useValidAutocomplete
Important
- PRs must go to the
nextbranch, with aminorchangeset - You have to comment if you're working on a rule. This will avoid having multiple contributors working on the same rule. In case of double PRs, precedence will go to users that comment here
Note
- When working on a rule, you also need to consider
.astro,.vueand.sveltefiles. These files might have their own syntax and nodes. Refer to thehtml.ungramfile - We still don't have a way to query variables and components exposed by the JavaScript embedded code. If you happen to need that information, please consider making the rule more lax and adding this to the documentation using the following syntax
:::note Explanation here... :::
Want to contribute? Let us know you are interested! We will assign you to the issue to prevent several people to work on the same issue. Don't worry, we can unassign you later if you are no longer interested in the issue! Read our contributing guide and analyzer contributing guide.
Reactions are currently unavailable
Sub-issues
Metadata
Metadata
Assignees
Labels
A-CLIArea: CLIArea: CLIA-LinterArea: linterArea: linterL-HTMLLanguage: HTML and super languagesLanguage: HTML and super languagesS-Help-wantedStatus: you're familiar with the code base and want to help the projectStatus: you're familiar with the code base and want to help the projectgood first issueGood for newcomersGood for newcomers