Difference between revisions of "Navigation References"
| (22 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{References  | {{References  | ||
|headline1=General  | |headline1=General  | ||
| − | |  | + | |coordhead1=7.000, 7.000, 0.000    | 
|references1=  | |references1=  | ||
| + | Users can easily navigate, find content, and determine where they are;  | ||
| + | 3WC - Web Accessibility Initiative - Accessibility Fundamentals;  | ||
| + | https://www.w3.org/WAI/fundamentals/accessibility-principles/#navigable;  | ||
Multiple Ways;  | Multiple Ways;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways;  | https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways;  | ||
| + | Motor Disabilities;  | ||
| + | Deque University - Accessibility Basic Concepts;  | ||
| + | https://dequeuniversity.com/class/archive/basic-concepts1/types-of-disabilities/motor-disabilities;  | ||
|headline2=Keyboard_Access  | |headline2=Keyboard_Access  | ||
| − | |  | + | |coordhead2=13.000, 7.000, 0.000  | 
|references2=  | |references2=  | ||
How to browse websites using a keyboard only;  | How to browse websites using a keyboard only;  | ||
| Line 13: | Line 19: | ||
https://www.accessibility-developer-guide.com/knowledge/keyboard-only/browsing-websites/;  | https://www.accessibility-developer-guide.com/knowledge/keyboard-only/browsing-websites/;  | ||
Keyboard access fundamentals;  | Keyboard access fundamentals;  | ||
| − | Rob Dodson;  | + | Rob Dodson - Google Developers;  | 
https://web.dev/keyboard-access/;  | https://web.dev/keyboard-access/;  | ||
Ensure that all interactive elements are keyboard accessible;  | Ensure that all interactive elements are keyboard accessible;  | ||
| − | 3WC   | + | Tips for Getting Started - 3WC Web Accessibility Initiative;  | 
https://www.w3.org/WAI/tips/developing/#ensure-that-all-interactive-elements-are-keyboard-accessible;  | https://www.w3.org/WAI/tips/developing/#ensure-that-all-interactive-elements-are-keyboard-accessible;  | ||
Keyboard Accessible;  | Keyboard Accessible;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html;  | https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html;  | ||
Keyboard;  | Keyboard;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html;  | https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html;  | ||
Focus Visible;  | Focus Visible;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html;  | https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html;  | ||
Link Purpose;  | Link Purpose;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html;  | https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html;  | ||
Character Key Shortcuts;  | Character Key Shortcuts;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html;  | https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html;  | ||
Article: I Used The Web For A Day With Just A Keyboard;  | Article: I Used The Web For A Day With Just A Keyboard;  | ||
| − | Chris Ashton;  | + | Chris Ashton - Smashing Magazine;  | 
https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/;  | https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/;  | ||
Provide easily identifiable feedback;  | Provide easily identifiable feedback;  | ||
| − | 3WC   | + | Tips for Getting Started - 3WC Web Accessibility Initiative;  | 
https://www.w3.org/WAI/tips/designing/#provide-easily-identifiable-feedback;  | https://www.w3.org/WAI/tips/designing/#provide-easily-identifiable-feedback;  | ||
Lens Of Keyboard;  | Lens Of Keyboard;  | ||
| − | Steven Lambert;  | + | Steven Lambert - Smashing Magazine;  | 
https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-keyboard;  | https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-keyboard;  | ||
Introduction to Focus;  | Introduction to Focus;  | ||
| − | Meggin Kearney, Dave Gash, Rob Dodson;  | + | Meggin Kearney, Dave Gash, Rob Dodson - Google Developers;  | 
https://developers.google.com/web/fundamentals/accessibility/focus;  | https://developers.google.com/web/fundamentals/accessibility/focus;  | ||
Use semantic HTML for easy keyboard wins;  | Use semantic HTML for easy keyboard wins;  | ||
| − | Rob Dodson;  | + | Rob Dodson - Google Developers;  | 
https://web.dev/use-semantic-html/;  | https://web.dev/use-semantic-html/;  | ||
Style focus;  | Style focus;  | ||
| − | Rob Dodson;  | + | Rob Dodson - Google Developers;  | 
https://web.dev/style-focus/;  | https://web.dev/style-focus/;  | ||
| + | Carousel Concepts;  | ||
| + | W3C - Web Accessibility Tutorials;  | ||
| + | https://www.w3.org/WAI/tutorials/carousels/;  | ||
|headline3=Flow  | |headline3=Flow  | ||
| − | |  | + | |coordhead3=13.000, 341.000, 0.000  | 
|references3=  | |references3=  | ||
Reflect the reading order in the code order;  | Reflect the reading order in the code order;  | ||
| − | 3WC   | + | Tips for Getting Started - 3WC Web Accessibility Initiative;  | 
https://www.w3.org/WAI/tips/developing/#reflect-the-reading-order-in-the-code-order;  | https://www.w3.org/WAI/tips/developing/#reflect-the-reading-order-in-the-code-order;  | ||
Focus Order;  | Focus Order;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html;  | https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html;  | ||
Location;  | Location;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/location.html;  | https://www.w3.org/WAI/WCAG21/Understanding/location.html;  | ||
Bypass Blocks;  | Bypass Blocks;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html;  | https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html;  | ||
No Keyboard Trap;  | No Keyboard Trap;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html;  | https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html;  | ||
Reflow;  | Reflow;  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | |
https://www.w3.org/WAI/WCAG21/Understanding/reflow.html;  | https://www.w3.org/WAI/WCAG21/Understanding/reflow.html;  | ||
Content reordering;  | Content reordering;  | ||
| − | Rachel Andrew;  | + | Rachel Andrew - Google Developers;  | 
https://web.dev/content-reordering/;  | https://web.dev/content-reordering/;  | ||
Control focus with tabindex;  | Control focus with tabindex;  | ||
| − | Rob Dodson;  | + | Rob Dodson - Google Developers;  | 
https://web.dev/control-focus-with-tabindex/;  | https://web.dev/control-focus-with-tabindex/;  | ||
| + | Meaningful Sequence;  | ||
| + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1;  | ||
| + | https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html;  | ||
| + | Ordering the content in a meaningful sequence;  | ||
| + | Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2;  | ||
| + | https://www.w3.org/WAI/WCAG21/Techniques/general/G57;  | ||
| + | Positioning content based on structural markup;  | ||
| + | Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2;  | ||
| + | https://www.w3.org/WAI/WCAG21/Techniques/css/C6;  | ||
|headline4=  | |headline4=  | ||
| − | |  | + | |coordhead4=  | 
|references4=  | |references4=  | ||
|headline5=  | |headline5=  | ||
| − | |  | + | |coordhead5=  | 
|references5=  | |references5=  | ||
|linksto=  | |linksto=  | ||
| Line 95: | Line 113: | ||
===Multiple Ways===  | ===Multiple Ways===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways  | https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways  | ||
| + | |||
| + | ===Motor Disabilities===  | ||
| + | Deque University - Accessibility Basic Concepts  | ||
| + | |||
| + | https://dequeuniversity.com/class/archive/basic-concepts1/types-of-disabilities/motor-disabilities  | ||
==Keyboard Access==  | ==Keyboard Access==  | ||
| Line 106: | Line 129: | ||
===Keyboard access fundamentals===  | ===Keyboard access fundamentals===  | ||
| − | Rob Dodson  | + | Rob Dodson - Google Developers  | 
https://web.dev/keyboard-access/  | https://web.dev/keyboard-access/  | ||
===Ensure that all interactive elements are keyboard accessible===  | ===Ensure that all interactive elements are keyboard accessible===  | ||
| − | 3WC   | + | Tips for Getting Started - 3WC Web Accessibility Initiative  | 
https://www.w3.org/WAI/tips/developing/#ensure-that-all-interactive-elements-are-keyboard-accessible  | https://www.w3.org/WAI/tips/developing/#ensure-that-all-interactive-elements-are-keyboard-accessible  | ||
===Keyboard Accessible===  | ===Keyboard Accessible===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html  | https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html  | ||
===Keyboard===  | ===Keyboard===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html  | https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html  | ||
===Focus Visible===  | ===Focus Visible===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html  | https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html  | ||
===Link Purpose===  | ===Link Purpose===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html  | https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html  | ||
===Character Key Shortcuts===  | ===Character Key Shortcuts===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html  | https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html  | ||
===Article: I Used The Web For A Day With Just A Keyboard===  | ===Article: I Used The Web For A Day With Just A Keyboard===  | ||
| − | Chris Ashton  | + | Chris Ashton - Smashing Magazine  | 
https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/  | https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/  | ||
===Provide easily identifiable feedback===  | ===Provide easily identifiable feedback===  | ||
| − | 3WC   | + | Tips for Getting Started - 3WC Web Accessibility Initiative  | 
https://www.w3.org/WAI/tips/designing/#provide-easily-identifiable-feedback  | https://www.w3.org/WAI/tips/designing/#provide-easily-identifiable-feedback  | ||
===Lens Of Keyboard===  | ===Lens Of Keyboard===  | ||
| − | Steven Lambert  | + | Steven Lambert - Smashing Magazine  | 
https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-keyboard  | https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-keyboard  | ||
===Introduction to Focus===  | ===Introduction to Focus===  | ||
| − | Meggin Kearney, Dave Gash, Rob Dodson  | + | Meggin Kearney, Dave Gash, Rob Dodson - Google Developers  | 
https://developers.google.com/web/fundamentals/accessibility/focus  | https://developers.google.com/web/fundamentals/accessibility/focus  | ||
===Use semantic HTML for easy keyboard wins===  | ===Use semantic HTML for easy keyboard wins===  | ||
| − | Rob Dodson  | + | Rob Dodson - Google Developers  | 
https://web.dev/use-semantic-html/  | https://web.dev/use-semantic-html/  | ||
| + | |||
| + | ===Carousel Concepts===  | ||
| + | W3C - Web Accessibility Tutorials  | ||
| + | |||
| + | https://www.w3.org/WAI/tutorials/carousels/  | ||
| + | |||
| + | ===Style focus===  | ||
| + | Rob Dodson - Google Developers  | ||
| + | |||
| + | https://web.dev/style-focus/  | ||
==Flow==  | ==Flow==  | ||
===Reflect the reading order in the code order===  | ===Reflect the reading order in the code order===  | ||
| − | 3WC   | + | Tips for Getting Started - 3WC Web Accessibility Initiative  | 
https://www.w3.org/WAI/tips/developing/#reflect-the-reading-order-in-the-code-order  | https://www.w3.org/WAI/tips/developing/#reflect-the-reading-order-in-the-code-order  | ||
===Focus Order===  | ===Focus Order===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html  | https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html  | ||
===Location===  | ===Location===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/location.html  | https://www.w3.org/WAI/WCAG21/Understanding/location.html  | ||
===Bypass Blocks===  | ===Bypass Blocks===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html  | https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html  | ||
===No Keyboard Trap===  | ===No Keyboard Trap===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html  | https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html  | ||
===Reflow===  | ===Reflow===  | ||
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
https://www.w3.org/WAI/WCAG21/Understanding/reflow.html  | https://www.w3.org/WAI/WCAG21/Understanding/reflow.html  | ||
===Content reordering===  | ===Content reordering===  | ||
| − | Rachel Andrew  | + | Rachel Andrew - Google Developers  | 
https://web.dev/content-reordering/  | https://web.dev/content-reordering/  | ||
===Control focus with tabindex===  | ===Control focus with tabindex===  | ||
| − | Rob Dodson  | + | Rob Dodson - Google Developers  | 
https://web.dev/control-focus-with-tabindex/  | https://web.dev/control-focus-with-tabindex/  | ||
| − | ===  | + | ===Meaningful Sequence===  | 
| − | + | Understanding Web Content Accessibility Guidelines (WCAG) 2.1  | |
| + | |||
| + | https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html  | ||
| + | |||
| + | ===Ordering the content in a meaningful sequence===  | ||
| + | Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2  | ||
| + | |||
| + | https://www.w3.org/WAI/WCAG21/Techniques/general/G57  | ||
| + | |||
| + | ===Positioning content based on structural markup===  | ||
| + | Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2  | ||
| − | https://  | + | https://www.w3.org/WAI/WCAG21/Techniques/css/C6  | 
Latest revision as of 12:43, 7 June 2021
| headline 1 | General | 
|---|---|
| headline 1 coordinates | 7.000, 7.000, 0.000 | 
| references 1 | Users can easily navigate, find content, and determine where they are;
 3WC - Web Accessibility Initiative - Accessibility Fundamentals; https://www.w3.org/WAI/fundamentals/accessibility-principles/#navigable; Multiple Ways; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways; Motor Disabilities; Deque University - Accessibility Basic Concepts; https://dequeuniversity.com/class/archive/basic-concepts1/types-of-disabilities/motor-disabilities;  | 
| headline 2 | Keyboard_Access | 
| headline 2 coordinates | 13.000, 7.000, 0.000 | 
| references 2 | How to browse websites using a keyboard only;
 Accessibility Developer Guide; https://www.accessibility-developer-guide.com/knowledge/keyboard-only/browsing-websites/; Keyboard access fundamentals; Rob Dodson - Google Developers; https://web.dev/keyboard-access/; Ensure that all interactive elements are keyboard accessible; Tips for Getting Started - 3WC Web Accessibility Initiative; https://www.w3.org/WAI/tips/developing/#ensure-that-all-interactive-elements-are-keyboard-accessible; Keyboard Accessible; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html; Keyboard; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html; Focus Visible; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html; Link Purpose; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html; Character Key Shortcuts; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html; Article: I Used The Web For A Day With Just A Keyboard; Chris Ashton - Smashing Magazine; https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/; Provide easily identifiable feedback; Tips for Getting Started - 3WC Web Accessibility Initiative; https://www.w3.org/WAI/tips/designing/#provide-easily-identifiable-feedback; Lens Of Keyboard; Steven Lambert - Smashing Magazine; https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-keyboard; Introduction to Focus; Meggin Kearney, Dave Gash, Rob Dodson - Google Developers; https://developers.google.com/web/fundamentals/accessibility/focus; Use semantic HTML for easy keyboard wins; Rob Dodson - Google Developers; https://web.dev/use-semantic-html/; Style focus; Rob Dodson - Google Developers; https://web.dev/style-focus/; Carousel Concepts; W3C - Web Accessibility Tutorials; https://www.w3.org/WAI/tutorials/carousels/;  | 
| headline 3 | Flow | 
| headline 3 coordinates | 13.000, 341.000, 0.000 | 
| references 3 | Reflect the reading order in the code order;
 Tips for Getting Started - 3WC Web Accessibility Initiative; https://www.w3.org/WAI/tips/developing/#reflect-the-reading-order-in-the-code-order; Focus Order; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html; Location; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/location.html; Bypass Blocks; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html; No Keyboard Trap; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html; Reflow; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/reflow.html; Content reordering; Rachel Andrew - Google Developers; https://web.dev/content-reordering/; Control focus with tabindex; Rob Dodson - Google Developers; https://web.dev/control-focus-with-tabindex/; Meaningful Sequence; Understanding Web Content Accessibility Guidelines (WCAG) 2.1; https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html; Ordering the content in a meaningful sequence; Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2; https://www.w3.org/WAI/WCAG21/Techniques/general/G57; Positioning content based on structural markup; Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2; https://www.w3.org/WAI/WCAG21/Techniques/css/C6;  | 
| headline 4 | |
| headline 4 coordinates | |
| references 4 | |
| headline 5 | |
| headline 5 coordinates | |
| references 5 | |
| links to | |
| belongs to | Navigation | 
| contains | 
General[edit]
[edit]
3WC - Web Accessibility Initiative - Accessibility Fundamentals
https://www.w3.org/WAI/fundamentals/accessibility-principles/#navigable
Multiple Ways[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways
Motor Disabilities[edit]
Deque University - Accessibility Basic Concepts
https://dequeuniversity.com/class/archive/basic-concepts1/types-of-disabilities/motor-disabilities
Keyboard Access[edit]
How to browse websites using a keyboard only[edit]
Accessibility Developer Guide
https://www.accessibility-developer-guide.com/knowledge/keyboard-only/browsing-websites/
Keyboard access fundamentals[edit]
Rob Dodson - Google Developers
https://web.dev/keyboard-access/
Ensure that all interactive elements are keyboard accessible[edit]
Tips for Getting Started - 3WC Web Accessibility Initiative
https://www.w3.org/WAI/tips/developing/#ensure-that-all-interactive-elements-are-keyboard-accessible
Keyboard Accessible[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html
Keyboard[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html
Focus Visible[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html
Link Purpose[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html
Character Key Shortcuts[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html
Article: I Used The Web For A Day With Just A Keyboard[edit]
Chris Ashton - Smashing Magazine
https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/
Provide easily identifiable feedback[edit]
Tips for Getting Started - 3WC Web Accessibility Initiative
https://www.w3.org/WAI/tips/designing/#provide-easily-identifiable-feedback
Lens Of Keyboard[edit]
Steven Lambert - Smashing Magazine
https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-keyboard
Introduction to Focus[edit]
Meggin Kearney, Dave Gash, Rob Dodson - Google Developers
https://developers.google.com/web/fundamentals/accessibility/focus
Use semantic HTML for easy keyboard wins[edit]
Rob Dodson - Google Developers
https://web.dev/use-semantic-html/
Carousel Concepts[edit]
W3C - Web Accessibility Tutorials
https://www.w3.org/WAI/tutorials/carousels/
Style focus[edit]
Rob Dodson - Google Developers
Flow[edit]
Reflect the reading order in the code order[edit]
Tips for Getting Started - 3WC Web Accessibility Initiative
https://www.w3.org/WAI/tips/developing/#reflect-the-reading-order-in-the-code-order
Focus Order[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html
Location[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/location.html
Bypass Blocks[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html
No Keyboard Trap[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html
Reflow[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/reflow.html
Content reordering[edit]
Rachel Andrew - Google Developers
https://web.dev/content-reordering/
Control focus with tabindex[edit]
Rob Dodson - Google Developers
https://web.dev/control-focus-with-tabindex/
Meaningful Sequence[edit]
Understanding Web Content Accessibility Guidelines (WCAG) 2.1
https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html
Ordering the content in a meaningful sequence[edit]
Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2
https://www.w3.org/WAI/WCAG21/Techniques/general/G57
Positioning content based on structural markup[edit]
Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2