Fix a lot of support 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 226 matching lines @@
 without using the mouse.
 Also check that any popups on page actions or browser actions
 are keyboard navigable. 
 </p>
 
 <p id="builtin">
 On Windows, you can use <b>Shift+Alt+T</b>
 to switch the keyboard focus to the toolbar,
 which lets you navigate to the icons of page actions and browser actions.
 The help topic
-<a href="http://www.google.com/support/chrome/bin/static.py?hl=en&page=guide.cs&guide=25799&from=25799&rd=1">Keyboard and mouse shortcuts</a>
+<a href="https://support.google.com/chrome/answer/157179">Keyboard and mouse shortcuts</a>
 lists all of Google Chrome's keyboard shortcuts;
 details about toolbar navigation
 are in the section <b>Google Chrome feature shortcuts</b>.
 </p>
 
 <p class="note">
 <b>Note:</b>
 The Windows version of Google Chrome 6 was the first
 to support keyboard navigation to the toolbar.
 Support is also planned for Linux.
@@ skipping 203 matching lines @@
 
 <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="sampleshtml">Samples</a>.