Materialize CSS form components lack ARIA roles and default focus outlines, creating accessibility uncertainty

Materialize CSS’s user‑facing workflow lacks explicit ARIA role definitions for its form components, creating ambiguity for screen readers, and its default focus outline is removed in production builds, which can impede keyboard navigation for users with visual impairments.

Because accessibility changes may differ across versions and custom theming can obscure default behavior, the timeline for addressing these issues remains undefined, leaving developers uncertain about when improvements will be implemented.

Which version of Materialize CSS should serve as the baseline for accessibility verification? How can explicit ARIA roles be added to form components without breaking custom theming?