From 99a99c12e5006a0ba285b68d16f38bc57cb58751 Mon Sep 17 00:00:00 2001 From: konpyuta Date: Sat, 15 Dec 2018 11:13:46 -0500 Subject: [PATCH] fix: update Accessibility guide article (#26646) Made edits such as correcting capitalization of proper nouns, removing repetitive content, and modifying sentences for better grammar and flow. --- guide/english/accessibility/index.md | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/guide/english/accessibility/index.md b/guide/english/accessibility/index.md index e2446e96ed..a1d85313e6 100644 --- a/guide/english/accessibility/index.md +++ b/guide/english/accessibility/index.md @@ -4,24 +4,16 @@ title: Accessibility ## Accessibility Web accessibility means that people with disabilities can use the Web. -More specifically, Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can -contribute to the Web. Web accessibility also benefits others, including [older people](https://www.w3.org/WAI/bcase/soc.html#of) with changing abilities -due to aging. +More specifically, Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. -Web accessibility encompasses all disabilities that affect access to the Web, including visual, auditory, physical, speech, cognitive, and neurological -disabilities. The article [How People with Disabilities Use the Web](http://www.w3.org/WAI/intro/people-use-web/Overview.html) describes how different -disabilities affect Web use and includes scenarios of people with disabilities using the Web. +Web accessibility encompasses all disabilities that affect access to the Web, including visual, auditory, physical, speech, cognitive, and neurological disabilities. The article [How People with Disabilities Use the Web](http://www.w3.org/WAI/intro/people-use-web/Overview.html) describes how different disabilities affect Web use and includes scenarios of people with disabilities using the Web. -Web accessibility also **benefits** people *without* disabilities. For example, a key principle of Web accessibility is designing Web sites and software -that are flexible to meet different user needs, preferences, and situations. This **flexibility** also benefits people *without* disabilities in certain -situations, such as people using a slow Internet connection, people with "temporary disabilities" such as a broken arm, and people with changing abilities -due to aging. The article [Developing a Web Accessibility Business Case for Your Organization](https://www.w3.org/WAI/bcase/Overview) describes many +Web accessibility also **benefits** people *without* disabilities. For example, a key principle of Web accessibility is designing Web sites and software that are flexible to meet different user needs, preferences, and situations. This **flexibility** also benefits people *without* disabilities in certain situations, such as people using a slow Internet connection, people with "temporary disabilities" such as a broken arm, and older people with changing abilities due to aging. The article [Developing a Web Accessibility Business Case for Your Organization](https://www.w3.org/WAI/bcase/Overview) describes many different benefits of Web accessibility, including **benefits for organizations**. Web accessibility should also include the people who don't have access to the internet or to computers and also the countries with slow Internet. -A prominent guideline for web development was introduced by the [World Wide Web Consortium (W3C)](https://www.w3.org/), the [Web Accessibility Initiative](https://www.w3.org/WAI/) from which we get the [WAI-ARIA](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/WAI-ARIA_basics), the Accessible Rich Internet Applications Suite. Where WAI tackles the semantics of HTML to more easily nagivate the DOM Tree, ARIA attempts to make web apps, especially those developed with javascript and AJAX, more accessible. - +A prominent guideline for web development was introduced by the [World Wide Web Consortium (W3C)](https://www.w3.org/), the [Web Accessibility Initiative](https://www.w3.org/WAI/) from which we get the [WAI-ARIA](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/WAI-ARIA_basics), the Accessible Rich Internet Applications Suite. Where WAI tackles the semantics of HTML to more easily nagivate the DOM Tree, ARIA attempts to make web apps, especially those developed with JavaScript and AJAX, more accessible. The use of images and graphics on websites can decrease accessibility for those with visual impairments. However, this doesn't mean designers should avoid using these visual elements. When used correctly, visual elements can convey the appropriate look and feel to users without disabilities. In order to use these elements appropriately, web designers must use alt text to communicate the message of these elements to those who cannot see them. Alt text should be short and to the point--generally [no more than five to 15 words](https://www.thoughtco.com/writing-great-alt-text-3466185). If a graphic is used to convey information that exceeds the limitations of alt text, that information should also exist as web text in order to be read by screen readers. [Learn more about alt text](https://webaim.org/techniques/alttext/).