Remove .html extension from links

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

 <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>
 
@@ skipping 285 matching lines @@
 <a href="http://dev.aol.com/dhtml_style_guide">guidelines for keyboard shortcuts</a>.
 </p>
 
 <p>
 A good way to ensure discoverability of keyboard shortcuts
 is to list them somewhere.
 {{?is_apps}}
   Your application's options page
 {{:is_apps}}
   Your extension's
-  <a href="options.html">Options page</a>
+  <a href="options">Options page</a>
 {{/is_apps}}
 might be a good place to do this.
 </p>
 
 <p>
 For the example toolbar,
 a simple JavaScript keyboard handler could look like the following.
 Note how the ARIA property <code>aria-activedescendant</code>
 is updated in response to user input
 to reflect the current active toolbar button.
@@ skipping 143 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="sampleshtml">Samples</a>.