diff options
| -rw-r--r-- | doc/development/new_fe_guide/development/accessibility.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/development/new_fe_guide/development/accessibility.md b/doc/development/new_fe_guide/development/accessibility.md index a5dc6894850..2a3a126ca5c 100644 --- a/doc/development/new_fe_guide/development/accessibility.md +++ b/doc/development/new_fe_guide/development/accessibility.md @@ -2,7 +2,9 @@ Using semantic HTML plays a key role when it comes to accessibility. ## Accessible Rich Internet Applications - ARIA -WAI-ARIA, the Accessible Rich Internet Applications specification, defines a way to make Web content and Web applications more accessible to people with disabilities. +WAI-ARIA, the Accessible Rich Internet Applications specification, defines a way to make Web content and Web applications more accessible to people with disabilities. + +> Note: It is [recommended][using-aria] to use semantic elements as the primary method to achieve accessibility rather than adding aria attributes. Adding aria attributes should be seen as a secondary method for creating accessible elements. ### Role The `role` attribute describes the role the element plays in the context of the document. @@ -36,6 +38,7 @@ In forms we should use the `for` attribute in the label statement: - [Audit Rules Page][audit-rules] for best practices - [Lighthouse Accessibility Score][lighthouse] for accessibility audits +[using-aria]: https://www.w3.org/TR/using-aria/#notes2 [dev-tools]: https://github.com/GoogleChrome/accessibility-developer-tools [audit-rules]: https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules [aria-w3c]: https://www.w3.org/TR/wai-aria-1.1/ |