From 72fd7ff75aa6994ce49f024750d6cb79740c8b05 Mon Sep 17 00:00:00 2001 From: Tatyana Tsvetkova Date: Fri, 30 Mar 2018 17:09:02 +0300 Subject: [PATCH] Update accessibility.md (#708) Fix for broken links to W3C --- content/docs/accessibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/accessibility.md b/content/docs/accessibility.md index 634ce452..e1b5d516 100644 --- a/content/docs/accessibility.md +++ b/content/docs/accessibility.md @@ -203,7 +203,7 @@ initially triggered the modal. A more complex user experience should not mean a less accessible one. Whereas accessibility is most easily achieved by coding as close to HTML as possible, even the most complex widget can be coded accessibly. -Here we require knowledge of [ARIA Roles](https://www.w3.org/TR/wai-aria/roles) as well as [ARIA States and Properties](https://www.w3.org/TR/wai-aria/states_and_properties). +Here we require knowledge of [ARIA Roles](https://www.w3.org/TR/wai-aria/#roles) as well as [ARIA States and Properties](https://www.w3.org/TR/wai-aria/#states_and_properties). These are toolboxes filled with HTML attributes that are fully supported in JSX and enable us to construct fully accessible, highly functional React components. Each type of widget has a specific design pattern and is expected to function in a certain way by users and user agents alike: