Skip to content

Commit 213894f

Browse files
Update a11y-no-visually-hidden-interactive-element.md
### What Clean up documentation `htmlPropName` was moved to the eslint settings.
1 parent cd17c09 commit 213894f

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

docs/rules/a11y-no-visually-hidden-interactive-element.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Note: we are not guarding against visually hidden `input` elements at this time.
1212

1313
### Why do we visually hide content?
1414

15-
Visually hiding content can be useful when you want to provide information specifically to screen reader users or other assitive technology users while keeping content hidden from sighted users.
15+
Visually hiding content can be useful when you want to provide information specifically to screen reader users or other assistive technology users while keeping content hidden from sighted users.
1616

1717
Applying the following css will visually hide content while still making it accessible to screen reader users.
1818

@@ -61,16 +61,14 @@ width: 1px;
6161

6262
- className - A css className that visually hides content. Defaults to `sr-only`.
6363
- componentName - A react component name that visually hides content. Defaults to `VisuallyHidden`.
64-
- htmlPropName - A prop name used to replace the semantic element that is rendered. Defaults to `as`.
6564

6665
```json
6766
{
6867
"a11y-no-visually-hidden-interactive-element": [
6968
"error",
7069
{
7170
"className": "visually-hidden",
72-
"componentName": "VisuallyHidden",
73-
"htmlPropName": "as"
71+
"componentName": "VisuallyHidden"
7472
}
7573
]
7674
}

0 commit comments

Comments
 (0)