primer/css
1
1
Fork 0
mirror of https://github.com/primer/css.git synced 2024-09-20 05:07:11 +03:00
Code Issues Projects Releases Wiki Activity

Fixed a repeating text in a sentence (#1473)

Browse Source 
In a sentence in general guide lined there were repeated text, Removed them
This commit is contained in:
Arnav Kumar 2021-06-25 18:37:14 +05:30 committed by GitHub
parent 8541ed1db1
commit aa0715a947
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/content/principles/accessibility.md
View File

@ -27,7 +27,7 @@ Making our products accessible benefits everyone, not just people with disabilit
Always use semantic HTML elements, like `button`, `ul`, `nav`. Most modern browsers implement the accessibility features outlined in the specs for these elements; without them, elements will need additional [ARIA attributes and roles](https://www.w3.org/WAI/PF/aria) to be recognized by assistive technologies.
Elements like `h1`-`h6`, `nav`, `footer`, `header` have [meaningful roles](https://www.w3.org/WAI/PF/aria/roles) assigned, so use them, and use them carefully. This can help assistive technologies read the page better and help users find information quicker.
Elements like `h1`-`h6`, `nav`, `footer`, `header` have [meaningful roles](https://www.w3.org/WAI/PF/aria/roles) assigned, so use them carefully. This can help assistive technologies read the page better and help users find information quicker.
Only use a `div` or a `span` to markup up content when there isn't another HTML element that would semantically be more appropriate, or when an element is needed exclusively for applying CSS styles or JS behaviors.