From 24c6737a21242e71f9490f90b98900029859d8d3 Mon Sep 17 00:00:00 2001
From: TKrishnasamy <105902964+TKrishnasamy@users.noreply.github.com>
Date: Fri, 20 May 2022 14:52:17 +1000
Subject: [PATCH 1/6] Update links.md

---
 docs/data/material/components/links/links.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/data/material/components/links/links.md b/docs/data/material/components/links/links.md
index b583e0ba20e673..19f9175e7c3d9d 100644
--- a/docs/data/material/components/links/links.md
+++ b/docs/data/material/components/links/links.md
@@ -52,4 +52,15 @@ Here is a [more detailed guide](/material-ui/guides/routing/#link).
 - For the best user experience, links should stand out from the text on the page. For instance, you can keep the default `underline="always"` behavior.
 - If a link doesn't have a meaningful href, [it should be rendered using a `<button>` element](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md).
 
+Keyboard Accessibility:
+Make sure interactive (active) elements receives keyboard tab focus
+Make sure user can open the link / Activate the link using keyboard Enter key
+
+Screen reader
+Make sure the screen reader announce the descriptive link name when user tab to it
+If the link opens in new window or new browser tab, add the the help text in the code for SR users (Example "To know more about <org name> offers link opnes in new window)
+
+Others:
+ 
+
 {{"demo": "ButtonLink.js"}}

From a998bf22f3a5e156e80b543ca4100eaadfb606a2 Mon Sep 17 00:00:00 2001
From: Sam Sycamore <71297412+samuelsycamore@users.noreply.github.com>
Date: Wed, 10 Aug 2022 10:52:01 -0500
Subject: [PATCH 2/6] prettier

---
 docs/data/material/components/links/links.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/docs/data/material/components/links/links.md b/docs/data/material/components/links/links.md
index 19f9175e7c3d9d..a80822130be6ad 100644
--- a/docs/data/material/components/links/links.md
+++ b/docs/data/material/components/links/links.md
@@ -61,6 +61,5 @@ Make sure the screen reader announce the descriptive link name when user tab to
 If the link opens in new window or new browser tab, add the the help text in the code for SR users (Example "To know more about <org name> offers link opnes in new window)
 
 Others:
- 
 
 {{"demo": "ButtonLink.js"}}

From 6a9134f4e0725b0f0f787cf7ae0212481b277a51 Mon Sep 17 00:00:00 2001
From: Sam Sycamore <71297412+samuelsycamore@users.noreply.github.com>
Date: Wed, 10 Aug 2022 11:09:58 -0500
Subject: [PATCH 3/6] copyediting and prettier

---
 docs/data/material/components/links/links.md | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/docs/data/material/components/links/links.md b/docs/data/material/components/links/links.md
index a80822130be6ad..178c774a4bc78d 100644
--- a/docs/data/material/components/links/links.md
+++ b/docs/data/material/components/links/links.md
@@ -51,15 +51,16 @@ Here is a [more detailed guide](/material-ui/guides/routing/#link).
   Instead, use [specific descriptions](https://developers.google.com/web/tools/lighthouse/audits/descriptive-link-text).
 - For the best user experience, links should stand out from the text on the page. For instance, you can keep the default `underline="always"` behavior.
 - If a link doesn't have a meaningful href, [it should be rendered using a `<button>` element](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md).
+  The demo below illustrates how to properly link with a `<button>`:
 
-Keyboard Accessibility:
-Make sure interactive (active) elements receives keyboard tab focus
-Make sure user can open the link / Activate the link using keyboard Enter key
+{{"demo": "ButtonLink.js"}}
 
-Screen reader
-Make sure the screen reader announce the descriptive link name when user tab to it
-If the link opens in new window or new browser tab, add the the help text in the code for SR users (Example "To know more about <org name> offers link opnes in new window)
+### Keyboard accessibility
 
-Others:
+- Interactive elements should receive focus in a coherent order when the user presses the <kbd class="key">Tab</kbd> key.
+- Users should be able to open a link by pressing <kbd class="key">Enter</kbd>.
 
-{{"demo": "ButtonLink.js"}}
+### Screen reader accessibility
+
+- When a link receives focus, screen readers should announce a descriptive link name.
+  If the link opens in a new window or browser tab, add help text in the code to inform screen reader users—for example, _"To learn more, visit the **About** page which opens in a new window."_

From 133edfddec410a8da4c8718f6ff3fad5447ea8b3 Mon Sep 17 00:00:00 2001
From: Sam Sycamore <71297412+samuelsycamore@users.noreply.github.com>
Date: Wed, 10 Aug 2022 11:47:56 -0500
Subject: [PATCH 4/6] prettier and markdownlint

---
 docs/data/material/components/links/links.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/data/material/components/links/links.md b/docs/data/material/components/links/links.md
index 374dc700541701..06cef8e04142bd 100644
--- a/docs/data/material/components/links/links.md
+++ b/docs/data/material/components/links/links.md
@@ -63,4 +63,4 @@ Here is a [more detailed guide](/material-ui/guides/routing/#link).
 ### Screen reader accessibility
 
 - When a link receives focus, screen readers should announce a descriptive link name.
-  If the link opens in a new window or browser tab, add help text in the code to inform screen reader users—for example, _"To learn more, visit the **About** page which opens in a new window."_
+  If the link opens in a new window or browser tab, add help text in the code to inform screen reader users—for example, _"To learn more, visit the About page which opens in a new window."_

From 8ede3f1f2dfc6599a1d0333d940547cfb33751a7 Mon Sep 17 00:00:00 2001
From: Sam Sycamore <71297412+samuelsycamore@users.noreply.github.com>
Date: Fri, 12 Aug 2022 14:46:19 -0500
Subject: [PATCH 5/6] aria label

---
 docs/data/material/components/links/links.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/data/material/components/links/links.md b/docs/data/material/components/links/links.md
index 06cef8e04142bd..e88e2166072365 100644
--- a/docs/data/material/components/links/links.md
+++ b/docs/data/material/components/links/links.md
@@ -63,4 +63,4 @@ Here is a [more detailed guide](/material-ui/guides/routing/#link).
 ### Screen reader accessibility
 
 - When a link receives focus, screen readers should announce a descriptive link name.
-  If the link opens in a new window or browser tab, add help text in the code to inform screen reader users—for example, _"To learn more, visit the About page which opens in a new window."_
+  If the link opens in a new window or browser tab, add an [`aria-label`](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA8#:~:text=The%20aria%2Dlabel%20attribute%20provides,used%20instead%20of%20aria%2Dlabel%20) to inform screen reader users—for example, _"To learn more, visit the About page which opens in a new window."_

From 3c858007f2221b44ae65dc9b08c5366638c78159 Mon Sep 17 00:00:00 2001
From: Sam Sycamore <71297412+samuelsycamore@users.noreply.github.com>
Date: Fri, 12 Aug 2022 14:47:43 -0500
Subject: [PATCH 6/6] clean up link

---
 docs/data/material/components/links/links.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/data/material/components/links/links.md b/docs/data/material/components/links/links.md
index e88e2166072365..5a6d7d29d16285 100644
--- a/docs/data/material/components/links/links.md
+++ b/docs/data/material/components/links/links.md
@@ -63,4 +63,4 @@ Here is a [more detailed guide](/material-ui/guides/routing/#link).
 ### Screen reader accessibility
 
 - When a link receives focus, screen readers should announce a descriptive link name.
-  If the link opens in a new window or browser tab, add an [`aria-label`](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA8#:~:text=The%20aria%2Dlabel%20attribute%20provides,used%20instead%20of%20aria%2Dlabel%20) to inform screen reader users—for example, _"To learn more, visit the About page which opens in a new window."_
+  If the link opens in a new window or browser tab, add an [`aria-label`](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA8) to inform screen reader users—for example, _"To learn more, visit the About page which opens in a new window."_