docs(cb-a11y): Content - Form controls

Author: AlmeroSteyn

public/docs/ts/latest/cookbook/a11y.jade

@@ -1,16 +1,18 @@
 include ../_util-fns
 
 :marked
-    Welcome! You are about to learn some key concepts that will make your Angular 2 application accessible for
+    ## Welcome to A11y!
+
+    You are about to learn how to make your Angular 2 application accessible for
     as many people as possible. This is no small goal, there is a large group of people out there who find it
-    very hard or even impossible to use your applications without thinking about the concepts mentioned here.
+    very hard or even impossible to use applications that has not been built with these concepts in mind.
 
-    We will show you that this can often be achieved with little to no extra effort on your part,
-    if you bring these concepts right into the design phase of your application.
+    We will show you that these concepts can be integrated with little to no extra effort on your part,
+    provided you take them into account right from the design phase of your application.
 
     So page through this cookbook, apply the recipes contained herein and watch your userbase grow.
 
-    If you are seeing the concepts `Web Accessibility`, `ARIA` or `a11y` for the first time, you are at the start of an
+    If you are seeing the terms `Web Accessibility`, `ARIA` or `a11y` for the first time, you are at the start of an
     incredible journey. And for those who already enjoy the benefits of `Accessible Web Applications`, we will
     show you how to apply your knowledge in the new and exciting world of Angular 2.
 
@@ -22,16 +24,18 @@ include ../_util-fns
     as it has eleven letters, starts with an `a` and ends with a `y`, we shorten this word to `a11y`. We will
     refer to `a11y` when we actually want to say `accessibility`.
 
-    In short, `a11y` refers to creating web applications that everyone can use.
+    In short, `a11y` refers to creating web applications that everyone can use. Thus making it accessible to everyone.
 
-    If you are totally new to the concept you may want to have a look at what the folks at the `W3C` have to say about
-    [a11y](http://www.w3.org/WAI/intro/accessibility.php), to put the rest of the article into perspective. We will be
-    right here waiting for you when you come back.
+    If you are totally new to the term you may want to have a look at what the folks at the `W3C` have to say about
+    [a11y](https://www.w3.org/WAI/intro/accessibility.php), to put the rest of the article into perspective.
 
     But what is that other word?
 
-    `ARIA`, or `Accessible Rich Internet Applications` refers to bringing `a11y` concepts right into
-    internet applications like those we are building using Angular 2.
+    `ARIA`, or `Accessible Rich Internet Applications` refers to bringing `a11y` concepts into
+    internet applications like those we are building with Angular 2. You can also see what they say about
+    [ARIA](https://www.w3.org/WAI/intro/aria) at the `W3C`.
+
+    We will be right here waiting for you when you come back.
 
 .l-main-section
 :marked
@@ -41,7 +45,7 @@ include ../_util-fns
     thought for the standard `HTML` elements before you decide to build something new.
 
     The makers of the browsers have spent a lot of time thinking about the very same issue that has brought
-    us to this page today and have provided you with a lot of functionality out-of-the-box when you make use of
+    you to this page today and have provided you with a lot of functionality out-of-the-box when you make use of
     standard `HTML` elements in your component templates.
 
     We would like to suggest the following rule of thumb when building your applications:
@@ -60,7 +64,7 @@ include ../_util-fns
 
     So without further ado, let us see how easy it is to get big accessibility gains in our applications!
 
-    **Feel free to follow along in this [live example](/resources/live-examples/cb-a11y/ts/plnkr.html)**.
+
 
 .l-main-section
 :marked
@@ -92,6 +96,8 @@ include ../_util-fns
 
     [Managing focus](#managin-focus)
 
+    **Feel free to follow along in this [live example](/resources/live-examples/cb-a11y/ts/plnkr.html)**.
+
 .l-main-section
 <a id="form-control-labels"></a>
 :marked