Drilldown: referencecollection

General (4)

0.000 (4) · 10.000 (1) · 177.000 (1) · 205.000 (1) · 285.000 (1) · 4.000 (2) · 7.000 (1)

3WC - Web Accessibility Initiative - Accessibility Fundamentals (1) · Accessible CSS (1) · Concurrent Input Mechanisms (1) · Deque University - Accessibility Basic Concepts (1) · Headings and labels (1) · https://dequeuniversity.com/class/archive/basic-concepts1/types-of-disabilities/motor-disabilities (1) · https://developers.google.com/web/fundamentals/accessibility/semantics-builtin/the-accessibility-tree (1) · https://rawgit.com/w3c/coga/master/issue-papers/personalization-preferences.html (1) · https://w3c.github.io/personalization-semantics/ (1) · https://webaim.org/techniques/css/ (1) · https://www.w3.org/TR/2020/WD-personalization-semantics-requirements-1.0-20201028/ (1) · https://www.w3.org/WAI/fundamentals/accessibility-principles/#navigable (1) · https://www.w3.org/WAI/personalization/ (1) · https://www.w3.org/WAI/tips/writing/#use-headings-to-convey-meaning-and-structure (1) · https://www.w3.org/WAI/WCAG21/Understanding/concurrent-input-mechanisms.html (1) · https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.html (1) · https://www.w3.org/WAI/WCAG21/Understanding/identify-purpose.html (1) · https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html (1) · https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways (1) · https://www.w3.org/WAI/WCAG21/Understanding/section-headings (1) · Identify Purpose (1) · Meggin Kearney, Dave Gash, Alice Boxhall - Google Developers (1) · Motion Actuation (1) · Motor Disabilities (1) · Multiple Ways (1) · Personalization and User Preferences (1) · Personalization Overview (1) · Personalization Semantics Explainer 1.0 (1) · Requirements for Personalization Semantics (1) · Section Headings (1) · Standards/Guidelines - 3WC - Web Accessibility Initiative (1) · The Accessibility Tree (1) · Tips for Getting Started - 3WC Web Accessibility Initiative (1) · Understanding Web Content Accessibility Guidelines (WCAG) 2.1 (4) · Use headings to convey meaning and structure (1) · Users can easily navigate, find content, and determine where they are (1) · W3C - Cognitive Accessibility Issue Papers (1) · W3C - Technical reports (1) · WebAIM - Center for Persons with Disabilities (1)

Adjust Content Reproduction (1) · Dividing Processes (1) · Keyboard_Access (1) · Responsive (1)

0.000 · 16.000 · None · 2.000 · 328.000 · 100.000 · 105.000 · 13.000 · 140.000 · 145.000 · 151.000 · 17.000 · 177.000 · 184.000 · 20.000 · 205.000 · 229.000 · 236.387 · 256.000 · 257.000

Other values: ; 6.000 7.000 28.000 30.000 42.000 43.000 53.000 54.000 75.000 76.500 276.000 285.000 304.000 306.000 314.238 318.000 320.000 322.000 324.000 336.000 351.000 356.000

Understanding Web Content Accessibility Guidelines (WCAG) 2.1 (2)

Other values: ; A project to help personalisation for any use - including people with learning and memory issues Accessibility Developer Guide Accessible responsive design Article: I Used The Web For A Day With Just A Keyboard Carousel Concepts Character Key Shortcuts Chris Ashton - Smashing Magazine Coga.personalisation Create designs for different viewport sizes Dave Gash, Meggin Kearney, Rachel Andrew, Rob Dodson - Google Developers Ensure that all interactive elements are keyboard accessible First Discovery Fluid: Infusion Focus Visible How to browse websites using a keyboard only How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile https://build-firstdiscovery.fluidproject.org/demos/ https://developers.google.com/web/fundamentals/accessibility/focus https://fluidproject.org/infusion.html https://github.com/ayelet-seeman/coga.personalisation https://uxplanet.org/progress-trackers-in-ux-design-4319cef1c600 https://web.dev/accessible-responsive-design/ https://web.dev/keyboard-access/ https://web.dev/style-focus/ https://web.dev/use-semantic-html/ https://www.accessibility-developer-guide.com/knowledge/keyboard-only/browsing-websites/ https://www.breadcrumbdigital.com.au/multi-step-form-design-part-1-progress-indicators-and-field-labels/ https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/#lens-keyboard https://www.smashingmagazine.com/2018/07/web-with-just-a-keyboard/ https://www.w3.org/TR/mobile-accessibility-mapping/ https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html https://www.w3.org/WAI/tips/designing/#create-designs-for-different-viewport-sizes https://www.w3.org/WAI/tips/designing/#provide-easily-identifiable-feedback https://www.w3.org/WAI/tips/developing/#ensure-that-all-interactive-elements-are-keyboard-accessible https://www.w3.org/WAI/tutorials/carousels/ https://www.w3.org/WAI/tutorials/forms/multi-page/ https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html https://www.w3.org/WAI/WCAG21/Understanding/orientation.html Infusion is a code framework for building personalizable and adaptive applications Introduction to Focus Keyboard Keyboard access fundamentals Keyboard Accessible Kristen Willis Lens Of Keyboard Lets users discover, declare and store digital preferences Link Purpose Meggin Kearney, Dave Gash, Rob Dodson - Google Developers Mobile Accessibility Multi-page Forms Multi-step form design: Progress indicators and field labels Nick Babich Orientation Progress Trackers in UX Design Provide easily identifiable feedback Rob Dodson - Google Developers Steven Lambert - Smashing Magazine Style focus Tips for Getting Started - 3WC - Web Accessibility Initiative Tips for Getting Started - 3WC Web Accessibility Initiative Use semantic HTML for easy keyboard wins W3C - Web Accessibility Tutorials Web Accessibility Tutorials - 3WC Web Accessibility Initiative

None (1) · Adjust Content Complexity (1) · Flow (1) · User_Agents (1)

None (1) · 0.000 (3) · 13.000 (1) · 177.000 (1) · 205.000 (1) · 22.000 (1) · 28.000 (1) · 341.000 (1)

Rob Dodson - Google Developers (2) · Understanding Web Content Accessibility Guidelines (WCAG) 2.1 (2)

Other values: ; Accessibility Developer Guide ARIA ARIA Hiding and Updating Content ARIA Labels and Relationships Associate a label with every form control Best practice: Users can choose Simple Language (German only) as an alternative to German or English Bypass Blocks Content reordering Control focus with tabindex Focus Order Headings and landmarks 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://handbook.floeproject.org/metadata 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/techniques/css/invisiblecontent/ https://www.accessibility-developer-guide.com/knowledge/aria/ https://www.inkl-design.de/en/ https://www.w3.org/TR/using-aria/ 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/tutorials/forms/labels/ https://www.w3.org/WAI/WCAG21/Techniques/css/C6 https://www.w3.org/WAI/WCAG21/Techniques/general/G57 https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships 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/reflow.html Info And Relationships Inkl. Design Introduction to ARIA Introduction to Semantics Invisible Content Just for Screen Reader Users Labelling Controls Location Meaningful Sequence Meggin Kearney, Dave Gash, Alice Boxhall - Google Developers Metadata Mozilla - MDN WebDocs No Keyboard Trap Ordering the content in a meaningful sequence Positioning content based on structural markup Rachel Andrew - Google Developers Reflect the reading order in the code order Reflow Semantics and screen readers Techniques for the Web Content Accessibility Guidelines (WCAG) 2.2 The Inclusive Learning Design Handbook Tips for Getting Started - 3WC - Web Accessibility Initiative Tips for Getting Started - 3WC Web Accessibility Initiative Using ARIA WAI-ARIA basics Web Accessibility Tutorials - 3WC - Web Accessibility Initiative WebAIM - Center for Persons with Disabilities World Wide Web Consortium

None (3) · Maintenance (1)

None (3) · 0.000 (1) · 205.000 (1) · 58.000 (1)

None (3) · FLOE Metadata Feedback Tool (1) · https://metadata.floeproject.org/demos/feedback/ (1) · https://www.hotjar.com/blog/on-site-surveys/ (1) · Lets users provide feedback about how a resource matched their preferences and ask for improvements (1) · On-Site Surveys (1) · The easiest way to find out what people need, right on your website (1)

None (4)

None (4)

None (4)

None (4)

Adjustability (1) · Compatibility (1) · Complexity (1) · Navigation (1)

None (4)