From 7965ae515ce490e104e6f61d0ef701d26a298208 Mon Sep 17 00:00:00 2001 From: Sarah Waldie Date: Mon, 28 Jan 2019 20:27:04 -0500 Subject: [PATCH] Minor proofing edits + anti-pattern reference (#29577) --- 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 b7dbccc9a1..4e4fe3dafe 100644 --- a/guide/english/accessibility/accessibility-basics/index.md +++ b/guide/english/accessibility/accessibility-basics/index.md @@ -76,7 +76,7 @@ The HTML specification is a document that describes how the language should be u English ``` -Guess what? All three of these elements break several criteria of WCAG and therefore are not accessible at all. +Guess what? All three of these elements break several criteria of WCAG and therefore are not accessible at all. These approaches are often referred to as "anti-patterns" [learn more here](https://medium.com/ft-product-technology/an-outbreak-of-accessibility-anti-patterns-e73577242ee8) when addressing accessibility. "An anti-pattern is “a common response to a recurring problem that is usually ineffective and risks being highly counterproductive” [Wikipedia](https://en.wikipedia.org/wiki/Anti-pattern). The first element breaks the ‘name, role, value’-criterium, which states that all elements on a web page should expose their name, role (e.g. button) and value (e.g. the contents of an edit field) to assistive technologies. This div actually doesn’t provide any of the three, rendering it invisible to screen-readers.