Open liitfr opened 3 years ago
Thanks for opening the issue. We currently display nothing https://mui.com/components/skeleton/#aria however, it does sound like there is work to do.
From what I understand, the implementation of the component is correct, attributes should be handled userland, the Skeleton being too low level, but we can improve the documentation by doing the a11y correctly:
aria-busy
trick for the region that is loading.
Summary 💡
First of all, I don't know many things about ARIA best practices, so please forgive me if this issue isn't relevant.
I've read following ARIA suggestion in Circular Progress API :
Typically, it looks like the same use case as when one uses Skeletons before displaying desired content. So, for sake of consistency, shouldn't we add same guideline for Skeleton API doc ?
Thank you for your consideration
Examples 🌈
In depth reflexion can be found here : https://adrianroselli.com/2020/11/more-accessible-skeletons.html
Motivation 🔦
Consistency in documentation to increase accessibility best practices in people's app.