Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(599)

Issues Search
    My Issues | Starred     Open | Closed | All

Side by Side Diff: chrome/common/extensions/docs/a11y.html

Issue 3610008: Merge 61535 - A couple of accessibility-related updates/fixes.... (Closed) Base URL: svn://svn.chromium.org/chrome/branches/517/src/
Patch Set: Created 10 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | chrome/common/extensions/docs/devguide.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note: 1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:
2 1) The <head> information in this page is significant, should be uniform 2 1) The <head> information in this page is significant, should be uniform
3 across api docs and should be edited only with knowledge of the 3 across api docs and should be edited only with knowledge of the
4 templating mechanism. 4 templating mechanism.
5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a 5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
6 browser, it will be re-generated from the template, json schema and 6 browser, it will be re-generated from the template, json schema and
7 authored overview content. 7 authored overview content.
8 4) The <body>.innerHTML is also generated by an offline step so that this 8 4) The <body>.innerHTML is also generated by an offline step so that this
9 page may easily be indexed by search engines. 9 page may easily be indexed by search engines.
10 --><html xmlns="http://www.w3.org/1999/xhtml"><head> 10 --><html xmlns="http://www.w3.org/1999/xhtml"><head>
(...skipping 537 matching lines...) Expand 10 before | Expand all | Expand 10 after
548 <h3 id="navigation"> Navigation </h3> 548 <h3 id="navigation"> Navigation </h3>
549 549
550 <p> 550 <p>
551 Check that the user can navigate between 551 Check that the user can navigate between
552 the different parts of your extension 552 the different parts of your extension
553 without using the mouse. 553 without using the mouse.
554 Also check that any popups on page actions or browser actions 554 Also check that any popups on page actions or browser actions
555 are keyboard navigable. 555 are keyboard navigable.
556 </p> 556 </p>
557 557
558 <p id="builtin">
559 On Windows, you can use <b>Shift+Alt+T</b>
560 to switch the keyboard focus to the toolbar,
561 which lets you navigate to the icons of page actions and browser actions.
562 The help topic
563 <a href="http://www.google.com/support/chrome/bin/static.py?hl=en&amp;page=guide .cs&amp;guide=25799&amp;from=25799&amp;rd=1">Keyboard and mouse shortcuts</a>
564 lists all of Google Chrome's keyboard shortcuts;
565 details about toolbar navigation
566 are in the section <b>Google Chrome feature shortcuts</b>.
567 </p>
568
558 <p class="note"> 569 <p class="note">
559 <b>Note:</b> 570 <b>Note:</b>
560 We're improving keyboard accessibility to Google Chrome's interface; 571 The Windows version of Google Chrome 6 was the first
561 keyboard navigation to the icons of page actions and browser actions 572 to support keyboard navigation to the toolbar.
562 is expected in Google Chrome 6. 573 Support is also planned for Linux.
563 For details, see 574 On Mac OS X,
564 <a href="#builtin">Built-in toolbar navigation</a>. 575 access to the toolbar is provided through VoiceOver,
576 Apple's screenreader.
565 </p> 577 </p>
566 578
567 <p> 579 <p>
568 Make sure that it's easy to see 580 Make sure that it's easy to see
569 which part of the interface has keyboard focus. 581 which part of the interface has keyboard focus.
570 Usually a focus outline moves around the interface, 582 Usually a focus outline moves around the interface,
571 but if you’re using CSS heavily this outline might be suppressed 583 but if you’re using CSS heavily this outline might be suppressed
572 or the contrast might be reduced. 584 or the contrast might be reduced.
573 Two examples of focus outline follow. 585 Two examples of focus outline follow.
574 </p> 586 </p>
575 587
576 <img src="images/a11y/focus-outline-2.png" width="200" height="75" alt="A focus outline on a Search button"> 588 <img src="images/a11y/focus-outline-2.png" width="200" height="75" alt="A focus outline on a Search button">
577 <br> 589 <br>
578 <img src="images/a11y/focus-outline.png" width="400" height="40" alt="A focus ou tline on one of a series of links"> 590 <img src="images/a11y/focus-outline.png" width="400" height="40" alt="A focus ou tline on one of a series of links">
579 591
580 <h4 id="builtin"> Built-in toolbar navigation </h4>
581
582 <p>
583 Here are the keyboard shortcuts that we expect to be in Google Chrome 6.
584 You can try them out now in the Dev channel.
585 </p>
586
587 <p>
588 </p><table>
589 <tbody><tr>
590 <td> <b>Alt+Shift+T</b> </td>
591 <td> Focus on the first tool in the main toolbar. </td></tr>
592
593 <tr><td> <b>Tab</b>, <b>Shift+Tab</b>, <b>Home</b>, <b>End</b> </td>
594 <td> Move around in the toolbar,
595 including focusing on page actions and browser actions. </td></tr>
596
597 <tr><td> <b>Left&nbsp;arrow</b>, <b>Right&nbsp;arrow</b> </td>
598 <td> Move around in the toolbar,
599 unless you're in an edit box like the location bar,
600 where those keys are used for text editing. </td></tr>
601
602 <tr><td> <b>Space</b>, <b>Enter</b> </td>
603 <td> Activate toolbar buttons,
604 including page actions and browser actions. </td></tr>
605
606 <tr><td> <b>Context&nbsp;menu&nbsp;key</b>, <b>Shift+F10</b> </td>
607 <td> Open a toolbar button's context menu. </td></tr>
608
609 <tr><td> <b>Escape</b> </td>
610 <td> Return focus from the toolbar to the previous location. </td></tr>
611
612 <tr><td> <b>F6</b>, <b>Shift+F6</b> </td>
613 <td> Switch focus to the next keyboard-accessible pane,
614 where panes include the
615 main web content,
616 toolbar,
617 and bookmarks bar (if visible). </td></tr>
618
619 </tbody></table>
620 <p></p>
621
622 592
623 <h3 id="shortcuts"> Shortcuts </h3> 593 <h3 id="shortcuts"> Shortcuts </h3>
624 594
625 <p> 595 <p>
626 Although the most common keyboard navigation strategy involves 596 Although the most common keyboard navigation strategy involves
627 using the Tab key to move focus through the extension interface, 597 using the Tab key to move focus through the extension interface,
628 that's not always the easiest or most efficient way 598 that's not always the easiest or most efficient way
629 to use the interface. 599 to use the interface.
630 You can make keyboard navigation easier 600 You can make keyboard navigation easier
631 by providing explicit keyboard shortcuts. 601 by providing explicit keyboard shortcuts.
(...skipping 361 matching lines...) Expand 10 before | Expand all | Expand 10 after
993 _uff=0; 963 _uff=0;
994 urchinTracker(); 964 urchinTracker();
995 } 965 }
996 catch(e) {/* urchinTracker not available. */} 966 catch(e) {/* urchinTracker not available. */}
997 </script> 967 </script>
998 <!-- end analytics --> 968 <!-- end analytics -->
999 </div> 969 </div>
1000 </div> <!-- /gc-footer --> 970 </div> <!-- /gc-footer -->
1001 </div> <!-- /gc-container --> 971 </div> <!-- /gc-container -->
1002 </body></html> 972 </body></html>
OLDNEW
« no previous file with comments | « no previous file | chrome/common/extensions/docs/devguide.html » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698