docs(cb-a11y): Content - Form controls

Author: AlmeroSteyn

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

@@ -24,18 +24,24 @@ 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. Thus making it accessible to everyone.
+.l-sub-section
+    :marked
+        In short, `a11y` refers to creating web applications that everyone can use. Thus making it accessible to everyone.
 
+:marked
     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 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`.
+.l-sub-section
+    :marked
+        `ARIA`, or `Accessible Rich Internet Applications` refers to bringing `a11y` concepts into
+        internet applications like those we are building with Angular 2.
 
-    We will be right here waiting for you when you come back.
+:marked
+    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
@@ -50,12 +56,21 @@ include ../_util-fns
 
     We would like to suggest the following rule of thumb when building your applications:
 
-    >If there is already a standard element inside `HTML` providing the function that you are trying to build, use
-     that element instead of writing your own.
+.l-sub-section
+    :marked
+        If there is already a standard element inside `HTML` providing the function that you need, use
+        that element instead of writing your own.
 
+:marked
     So, for example, if you want to accept user text input, use the `INPUT` element instead of contructing something new.
-    And when you do write new components, use the standard `HTML` elements in your templates as often as possible.
 
+    And within component template the second rule of thumb is:
+
+.l-sub-section
+    :marked
+        Use standard `HTML` elements to construct your component templates as far as possible.
+
+:marked
     This way you have to think less about things like focus management, tabindex, etc. and have more time to think about
     your code.