Accessibility API/WCAG compliance

[gselderslaghs]

Context

This issue is the epic referencing multiple accessibility issues within the Materialize framework

Current Behavior

I've found many items already are compliant with accessibility standards and would like to thank the community for working on those items 🚀

As of today, multiple components are still missing accessibility implementations and as result his causes a web accessibility reduction regarding accessibility API and WCAG compliance

Expected behavior

Materialize should be accessibile to

• People who rely on keyboard control
• People with dexterity impairments using voice control or a keyboard-like switch device
• People with low vision who use screen magnification with keyboard control
• People using a screen reader, including blind, low vision, and neurodivergent people
• Neurodivergent people who use the keyboard
• Older adults who use the keyboard

Possible Solutions or Causes

In order to align with accessibility API and WCAG compliance the following issues should be addressed and validated using accessibility checker tools

• Tab Accessibility Missing  #81
• Material Box improvement: When zooming in we should add a closing button so users know how to exit zoomed in view clearly #246
• [Bug]: tabindex properties on select elements are destroyed during initialization #510
• [Bug]: Accessibility: focus states missing from select dropdown input elements #522
• [Accessibility]: Autocomplete options not accessible by keyboard interaction #538
• [Accessibility] Card reveal button not accessible by keyboard interaction #539
• [Accessibility] Floating action button not accessible by keyboard interaction #540
• [Accessibility] Feature Discovery open/close not accessible by keyboard interaction #541
• [Accessibility] Sidenav missing close handler when opened by keyboard interaction #542

Your Environment

• Version used: 2.1.1