Extensions Docs Server: Doc conversion script - SVN

chrome/common/extensions/docs/server2/templates/articles/a11y.html

-<div id="pageData-name" class="pageData">Accessibility (a11y)</div>
-<div id="pageData-showTOC" class="pageData">true</div>
+<h1>Accessibility (a11y)</h1>
+
 
 <p>
 When you design an extension,
 try to make it as accessible as possible
 to people with disabilities such as
 visual impairment, hearing loss, and limited dexterity.
 </p>
 
 <p>
 Everyone &mdash; not just people with special needs &mdash;
@@ skipping 43 matching lines @@
 
 <h3 id="htmlcontrols">Standard controls</h3>
 
 <p>
 Try to use standard HTML UI controls whenever possible.
 Standard HTML controls (shown in the following figure)
 are keyboard accessible, scale easily,
 and are generally understood by screen readers.
 </p>
 
-<img src="../images/a11y/standard-html-controls.png"
+<img src="{{static}}/images/a11y/standard-html-controls.png"
  width="550" height="350"
  alt="Screenshots and code for button, checkbox, radio, text, select/option, and link">
 
 
 <h3 id="aria">ARIA in custom controls</h3>
 
 <p>
 ARIA is a specification for making UI controls accessible to screen readers
 by means of a standard set of DOM attributes.
 These attributes provide clues to the screen reader
@@ skipping 185 matching lines @@
 
 <p>
 Make sure that it's easy to see
 which part of the interface has keyboard focus.
 Usually a focus outline moves around the interface,
 but if you’re using CSS heavily this outline might be suppressed 
 or the contrast might be reduced.
 Two examples of focus outline follow.
 </p>
 
-<img src="../images/a11y/focus-outline-2.png"
+<img src="{{static}}/images/a11y/focus-outline-2.png"
   width="200" height="75"
   alt="A focus outline on a Search button">
 <br />
-<img src="../images/a11y/focus-outline.png"
+<img src="{{static}}/images/a11y/focus-outline.png"
   width="400" height="40"
   alt="A focus outline on one of a series of links">
 
 
 <h3 id="shortcuts"> Shortcuts </h3>
 
 <p>
 Although the most common keyboard navigation strategy involves
 using the Tab key to move focus through the extension interface,
 that's not always the easiest or most efficient way
@@ skipping 169 matching lines @@
 <a href="http://www.webaim.org/techniques/alttext/">WebAIM article on appropriate alt text</a>.
 
 <h2 id="examples">Examples</h2>
 
 <p>
 For an example that implements keyboard navigation and ARIA properties, see
 <a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/extensions/news_a11y/">examples/extensions/news_a11y</a>
 (compare it to
 <a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/extensions/news/">examples/extensions/news</a>).
 For more examples and for help in viewing the source code,
-see <a href="samples.html">Samples</a>.
-
+see <a href="samples.html">Samples</a>.