Changed some grammatical errors upto line 29 (#30607)

Line 11: removed new before technolgies//not needed
removed comma after developers
added being before invented
changed to what degree is this a good thing, 
Full stop after another time
added that after say
Removed are "dark arts" and added comma

Line 13: Rmoved all after often not //not needed
Line 15: Removed comma after user //not needed
Line 27:  Added "so" in one sense "you can say" that "your"
Line 29: changed for to by
This commit is contained in:
Manas Ojha
2019-02-05 18:53:39 +05:30
committed by Tom
parent 89f171d2a9
commit c3ce26852a

View File

@@ -15,7 +15,6 @@ As an increasing number of new technologies are being created, the toolbox of a
One tool in that toolbox should be accessibility. It should be one of the very first steps of creating any form of web content, yet is not considered enough. This could be due to a simple case of not knowing it even exists or an extreme case like not caring about it at all.
If you are reading this article, you may be in one of the following categories:
* You are a novice web developer and would like to know more about accessibility.
* You are a seasoned web developer and have lost your way. (More on that later.)
* You feel that there is a legal obligation from your employer, and you need to learn more about it.
@@ -28,7 +27,7 @@ The word "accessibility" in itself can be a bit misleading at times, especially
In one sense, if your site is public on the Internet, that website is accessible to everyone with a web browser.
But is all the content on your website actually readable, usable, and understandable for everyone? Are there no thresholds that bar certain people from "accessing" all the information you are exposing?
But, is all the content on your website actually readable, usable, and understandable by everyone? Are there no thresholds that bar certain people from 'accessing' all the information you are exposing?
You could ask yourself questions such as the following: