Drilldown: referencecollection

General (1)

0.000 (1) · 7.000 (1)

3WC - Web Accessibility Initiative - Accessibility Fundamentals (1) · Deque University - Accessibility Basic Concepts (1) · https://dequeuniversity.com/class/archive/basic-concepts1/types-of-disabilities/motor-disabilities (1) · https://www.w3.org/WAI/fundamentals/accessibility-principles/#navigable (1) · https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways (1) · Motor Disabilities (1) · Multiple Ways (1) · Understanding Web Content Accessibility Guidelines (WCAG) 2.1 (1) · Users can easily navigate, find content, and determine where they are (1)

Keyboard_Access (1)

0.000 (1) · 13.000 (1) · 7.000 (1)

Accessibility Developer Guide (1) · Article: I Used The Web For A Day With Just A Keyboard (1) · Carousel Concepts (1) · Character Key Shortcuts (1) · Chris Ashton - Smashing Magazine (1) · Ensure that all interactive elements are keyboard accessible (1) · Focus Visible (1) · How to browse websites using a keyboard only (1) · https://developers.google.com/web/fundamentals/accessibility/focus (1) · https://web.dev/keyboard-access/ (1) · https://web.dev/style-focus/ (1) · https://web.dev/use-semantic-html/ (1) · https://www.accessibility-developer-guide.com/knowledge/keyboard-only/browsing-websites/ (1) · https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-keyboard (1) · https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/ (1) · https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html (1) · https://www.w3.org/WAI/tips/designing/#provide-easily-identifiable-feedback (1) · https://www.w3.org/WAI/tips/developing/#ensure-that-all-interactive-elements-are-keyboard-accessible (1) · https://www.w3.org/WAI/tutorials/carousels/ (1) · https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html (1) · https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html (1) · https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html (1) · https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html (1) · Introduction to Focus (1) · Keyboard (1) · Keyboard access fundamentals (1) · Keyboard Accessible (1) · Lens Of Keyboard (1) · Link Purpose (1) · Meggin Kearney, Dave Gash, Rob Dodson - Google Developers (1) · Provide easily identifiable feedback (1) · Rob Dodson - Google Developers (1) · Steven Lambert - Smashing Magazine (1) · Style focus (1) · Tips for Getting Started - 3WC Web Accessibility Initiative (1) · Understanding Web Content Accessibility Guidelines (WCAG) 2.1 (1) · Use semantic HTML for easy keyboard wins (1) · W3C - Web Accessibility Tutorials (1)

Flow (1)

0.000 · None · 2.000 · 13.000 · 140.000 · 177.000 · 18.000 · 205.000 · 22.000 · 229.000 · 236.387 · 256.000 · 276.000 · 28.000 · 310.000 · 312.000 · 314.238 · 320.000 · 334.000 · 340.000 · 341.000 · 348.000 · 358.000 · 38.000 · 40.000 · 42.000 · 43.000 · 66.000 · 75.000 · Other

None · Understanding Web Content Accessibility Guidelines (WCAG) 2.1 · 3WC - Web Accessibility Initiative · Meggin Kearney, Dave Gash, Alice Boxhall - Google Developers · Rob Dodson - Google Developers · Steven Lambert - Smashing Magazine · Tips for Getting Started - 3WC - Web Accessibility Initiative · WebAIM - Center for Persons with Disabilities · Accessibility Developer Guide · Animation from Interactions · ARIA · ARIA Hiding and Updating Content · ARIA Labels and Relationships · Arielle Pardes - WIRED · Associate a label with every form control · Best practice: Users can choose Simple Language (German only) as an alternative to German or English · Bureau Of Internet Accessibility · Bypass Blocks · Chris Ashton - Smashing Magazine · Color and contrast accessibility: Don't convey information with color alone

Other values: ; Content On Hover Or Focus Content reordering Control focus with tabindex Dave Gash, Meggin Kearney, Rachel Andrew, Rob Dodson - Google Developers Ditch the Fancy Vocabulary for Accessible Language Don’t use color alone to convey information Examples of designs that work well or don't work for colorblind people Focus Order Gov.uk: Accessibility in government Headings and landmarks How to create content that works well with screen readers I Used The Web For A Day Using A Screen Reader Images of text Info And Relationships Inkl. Design Introduction to ARIA Introduction to Screen Readers Introduction to Semantics Invisible Content Just for Screen Reader Users Label in Name Labelling Controls Lens Of Structure Lens of Color Link Purpose (In Context) Link Purpose (Link Only) Location Meaningful Sequence Metadata Mozilla - MDN WebDocs No Keyboard Trap Ordering the content in a meaningful sequence Page Structure Concepts Plain English Campaign Plain Language Action and Information Network Pointer Gestures Positioning content based on structural markup Provide controls for content that starts automatically Provide informative, unique page titles Rachel Andrew - Google Developers Re-authenticating Reflect the reading order in the code order Reflow Resize Text SVG patterns for Data Visualization Saving data so that it can be used after a user re-authenticates Screen Reader Accessibility Testing: An Introduction Semantics and Navigating Content Semantics and screen readers Success Criterion 1.4.2 Audio Control Techniques for the Web Content Accessibility Guidelines (WCAG) 2.1 Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2 Testing with Screen Readers - Questions and Answers Text Alternatives Textures.js The A - Z of alternative words The Inclusive Learning Design Handbook The Internet Is for Everyone, Right? Not With a Screen Reader Timeouts Tips for Getting Started - 3WC Web Accessibility Initiative Trace Dissemination - Youtube Understand and create sign language interpretation for audio and video Understanding the Web Content Accessibility Guidelines (WCAG) 2.1 Use simple words and phrases Using ARIA W3C - Web Accessibility Tutorials WAI-ARIA basics We Are Colorblind Web Accessibility Tutorials - 3WC - Web Accessibility Initiative Will Saunders - TestLodge World Wide Web Consortium http://www.plainenglish.co.uk/the-a-z-of-alternative-words.html https://accessibility.blog.gov.uk/2017/02/08/advice-for-creating-content-that-works-well-with-screen-readers/ https://blog.testlodge.com/screen-reader-accessibility-testing/ https://developer.mozilla.org/en-US/docs/Learn/Accessibility/WAI-ARIA_basics https://developers.google.com/web/fundamentals/accessibility/semantics-aria https://developers.google.com/web/fundamentals/accessibility/semantics-aria/aria-labels-and-relationships https://developers.google.com/web/fundamentals/accessibility/semantics-aria/hiding-and-updating-content https://developers.google.com/web/fundamentals/accessibility/semantics-builtin https://developers.google.com/web/fundamentals/accessibility/semantics-builtin/navigating-content https://handbook.floeproject.org/metadata https://riccardoscalco.it/textures/ https://wearecolorblind.com/examples/ https://web.dev/color-and-contrast-accessibility/#don't-convey-information-with-color-alone https://web.dev/content-reordering/ https://web.dev/control-focus-with-tabindex/ https://web.dev/headings-and-landmarks/ https://web.dev/semantics-and-screen-readers/ https://webaim.org/articles/screenreader_testing/ https://webaim.org/techniques/css/invisiblecontent/ https://www.accessibility-developer-guide.com/knowledge/aria/ https://www.boia.org/blog/ditch-the-fancy-vocabulary-for-accessible-language https://www.inkl-design.de/en/ https://www.plainlanguage.gov/guidelines/words/use-simple-words-phrases/ https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-color https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-structure https://www.smashingmagazine.com/2018/12/voiceover-screen-reader-web-apps/ https://www.w3.org/TR/using-aria/ https://www.w3.org/WAI/WCAG21/Techniques/css/C6 https://www.w3.org/WAI/WCAG21/Techniques/general/G105.html https://www.w3.org/WAI/WCAG21/Techniques/general/G57 https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html https://www.w3.org/WAI/WCAG21/Understanding/audio-control.html https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html https://www.w3.org/WAI/WCAG21/Understanding/images-of-text-no-exception.html https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-link-only https://www.w3.org/WAI/WCAG21/Understanding/location.html https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html https://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html https://www.w3.org/WAI/WCAG21/Understanding/re-authenticating.html https://www.w3.org/WAI/WCAG21/Understanding/reflow.html https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html https://www.w3.org/WAI/WCAG21/Understanding/text-alternatives https://www.w3.org/WAI/WCAG21/Understanding/timeouts.html https://www.w3.org/WAI/media/av/sign-languages https://www.w3.org/WAI/tips/designing/#dont-use-color-alone-to-convey-information https://www.w3.org/WAI/tips/designing/#provide-controls-for-content-that-starts-automatically https://www.w3.org/WAI/tips/developing/#associate-a-label-with-every-form-control https://www.w3.org/WAI/tips/developing/#reflect-the-reading-order-in-the-code-order https://www.w3.org/WAI/tips/writing/#provide-informative-unique-page-titles https://www.w3.org/WAI/tutorials/forms/labels/ https://www.w3.org/WAI/tutorials/page-structure/ https://www.wired.com/story/web-accessibility-blind-users-dominos/ https://www.youtube.com/watch?v=o_mvO6EQ0tM

None (1)

None (1)

None (1)

None (1)

None (1)

None (1)

None (1)

Navigation (1)

None (1)