From 4e22e660dc136a6d105eb7b0a333fa1369e1e723 Mon Sep 17 00:00:00 2001
From: rdfriesen <33337600+rdfriesen@users.noreply.github.com>
Date: Sat, 10 Nov 2018 15:04:53 -0500
Subject: [PATCH] typo fix (#21171)

* typo fix

* Update index.md
---
 guide/english/accessibility/accessibility-basics/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guide/english/accessibility/accessibility-basics/index.md b/guide/english/accessibility/accessibility-basics/index.md
index 27e42b5abd..95b8bf5da9 100644
--- a/guide/english/accessibility/accessibility-basics/index.md
+++ b/guide/english/accessibility/accessibility-basics/index.md
@@ -49,7 +49,7 @@ You may think that accessibility doesn't apply to you or to your users, so why i
 
 The truth is, you're right to a certain degree. If you have done meticulous user research and have excluded any chance of a certain group of people visiting your website, the priority for catering to that group of people diminishes quite a bit.
 
-However, doing this research is key in actually defending such a statement. Did you know there were <a href='http://audiogames.net' target='_blank' rel='nofollow'>blind gamers?</a> and even <a href='http://peteeckert.com/' target='_blank' rel='nofollow'>blind photographers?</a>. Perhaps you knew <a href='http://mentalfloss.com/article/25750/roll-over-beethoven-6-modern-deaf-musicians' target='_blank' rel='nofollow'>musicians can be deaf</a>?
+However, doing this research is key in actually defending such a statement. Did you know there were <a href='http://audiogames.net' target='_blank' rel='nofollow'>blind gamers?</a> and even <a href='http://peteeckert.com/' target='_blank' rel='nofollow'>blind photographers</a>? Perhaps you knew <a href='http://mentalfloss.com/article/25750/roll-over-beethoven-6-modern-deaf-musicians' target='_blank' rel='nofollow'>musicians can be deaf</a>?
 
 If you did, good for you. If not, I guess this drives my point home all the more.