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
|[datagrid-needs-labelling](docs/rules/datagrid-needs-labelling.md)| Accessibility: DataGrid must have proper labelling and follow ARIA grid patterns for complex data tables | ✅ |||
186
187
|[dialogbody-needs-title-content-and-actions](docs/rules/dialogbody-needs-title-content-and-actions.md)| A DialogBody should have a header(DialogTitle), content(DialogContent), and footer(DialogActions) | ✅ |||
187
188
|[dialogsurface-needs-aria](docs/rules/dialogsurface-needs-aria.md)| DialogueSurface need accessible labelling: aria-describedby on DialogueSurface and aria-label or aria-labelledby(if DialogueTitle is missing) | ✅ |||
188
189
|[dropdown-needs-labelling](docs/rules/dropdown-needs-labelling.md)| Accessibility: Dropdown menu must have an id and it needs to be linked via htmlFor of a Label | ✅ |||
@@ -206,11 +207,13 @@ Any use of third-party trademarks or logos are subject to those third-party's po
|[spinner-needs-labelling](docs/rules/spinner-needs-labelling.md)| Accessibility: Spinner must have either aria-label or label, aria-live and aria-busy attributes | ✅ |||
208
209
|[switch-needs-labelling](docs/rules/switch-needs-labelling.md)| Accessibility: Switch must have an accessible label | ✅ |||
210
+
|[table-needs-labelling](docs/rules/table-needs-labelling.md)| Accessibility: Table must have proper labelling and semantic structure for screen readers | ✅ |||
209
211
|[tablist-and-tabs-need-labelling](docs/rules/tablist-and-tabs-need-labelling.md)| This rule aims to ensure that Tabs with icons but no text labels have an accessible name and that Tablist is properly labeled. | ✅ |||
210
212
|[tag-dismissible-needs-labelling](docs/rules/tag-dismissible-needs-labelling.md)| This rule aims to ensure that dismissible Tag components have proper accessibility labelling: either aria-label on dismissIcon or aria-label on Tag with role on dismissIcon | ✅ |||
211
213
|[tag-needs-name](docs/rules/tag-needs-name.md)| Accessibility: Tag must have an accessible name | ✅ |||
212
214
|[toolbar-missing-aria](docs/rules/toolbar-missing-aria.md)| Accessibility: Toolbars need accessible labelling: aria-label or aria-labelledby | ✅ |||
213
215
|[tooltip-not-recommended](docs/rules/tooltip-not-recommended.md)| Accessibility: Prefer text content or aria over a tooltip for these components MenuItem, SpinButton | ✅ |||
216
+
|[tree-needs-labelling](docs/rules/tree-needs-labelling.md)| Accessibility: Tree must have proper labelling and follow ARIA tree pattern for hierarchical navigation | ✅ |||
214
217
|[visual-label-better-than-aria-suggestion](docs/rules/visual-label-better-than-aria-suggestion.md)| Visual label is better than an aria-label because sighted users can't read the aria-label text. || ✅ ||
Copy file name to clipboardExpand all lines: docs/rules/datagrid-needs-labelling.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,8 @@
1
-
# datagrid-needs-labelling
1
+
# Accessibility: DataGrid must have proper labelling and follow ARIA grid patterns for complex data tables (`@microsoft/fluentui-jsx-a11y/datagrid-needs-labelling`)
2
+
3
+
💼 This rule is enabled in the ✅ `recommended` config.
4
+
5
+
<!-- end auto-generated rule header -->
2
6
3
7
DataGrid components must have accessible labelling for screen readers to understand the data structure and purpose.
Copy file name to clipboardExpand all lines: docs/rules/tree-needs-labelling.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,8 @@
1
-
# tree-needs-labelling
1
+
# Accessibility: Tree must have proper labelling and follow ARIA tree pattern for hierarchical navigation (`@microsoft/fluentui-jsx-a11y/tree-needs-labelling`)
2
+
3
+
💼 This rule is enabled in the ✅ `recommended` config.
4
+
5
+
<!-- end auto-generated rule header -->
2
6
3
7
Tree components must have accessible labelling for screen readers to understand the hierarchical structure and navigation purpose.
0 commit comments