You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As much as I like the motivation of this project i.e. a feature-packed, small and functional material look, I very much miss the accessible design specs. So far, it has not been possible for us to inject accessibility attributes (a.k.a. contributing to this project) and am a bit concerned that for projects where alyle is used, such projects would lose a major audience who have special needs.
Describe the solution you'd like
I would very much appreciate the author(s) and/or the community to support the WAI-ARIA guidelines for all the components
Describe alternatives you've considered
Typically for the end-user, implementations are not a concern (and should not even be). As material usage increases by the day, and more and more libraries/frameworks incorporate the material guidelines, I believe, unless accessibility is a central part of this project, it'd leave many concerned developers with no choice but to switch to other much heavier or similar frameworks (e.g. Angular Material, UIKit, or even plain materialize.css, etc.). Perhaps, the official Angular Material project can project itself as a source of inspiration for this project's author(s) and the accessible sections of code for such components can be retro-fitted somehow.
The text was updated successfully, but these errors were encountered:
🚀 Feature request
Description
As much as I like the motivation of this project i.e. a feature-packed, small and functional
material
look, I very much miss the accessible design specs. So far, it has not been possible for us to inject accessibility attributes (a.k.a. contributing to this project) and am a bit concerned that for projects wherealyle
is used, such projects would lose a major audience who have special needs.Describe the solution you'd like
I would very much appreciate the author(s) and/or the community to support the WAI-ARIA guidelines for all the components
Describe alternatives you've considered
Typically for the end-user, implementations are not a concern (and should not even be). As
material
usage increases by the day, and more and more libraries/frameworks incorporate thematerial guidelines
, I believe, unless accessibility is a central part of this project, it'd leave many concerned developers with no choice but to switch to other much heavier or similar frameworks (e.g. Angular Material, UIKit, or even plain materialize.css, etc.). Perhaps, the official Angular Material project can project itself as a source of inspiration for this project's author(s) and theaccessible
sections of code for such components can be retro-fitted somehow.The text was updated successfully, but these errors were encountered: