From b2a55d4b02faab20f6ad5408e8def1a33838fb6f Mon Sep 17 00:00:00 2001 From: Alex Delude <32208447+alexdelude@users.noreply.github.com> Date: Sun, 3 Feb 2019 15:13:34 -0800 Subject: [PATCH] Fixing spelling for "whose" and "ongoing" (#29904) --- 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 4e4fe3dafe..1660ba9a47 100644 --- a/guide/english/accessibility/accessibility-basics/index.md +++ b/guide/english/accessibility/accessibility-basics/index.md @@ -62,7 +62,7 @@ There are variations on this legislation all over the world, some more severe an ## Ok, so accessibility is a big deal. Now how do we implement it? That question, sadly, is harder to answer than it may seem. -As stated above, accessibility is important for a large group of different people, each with their own needs. Making your website work for everyone is a large, on-going task. +As stated above, accessibility is important for a large group of different people, each with their own needs. Making your website work for everyone is a large, ongoing task. The Web Content Accessibility Guidelines or WCAG were composed to help developers create accessible content. This document contains a number of criteria you can use to check your website. There are also advanced techniques like [WAI-ARIA] that are important for JavaScript-based apps.