[material-ui][docs] Create ADA compliance documentation

[jmadson]

It would go a long way to help pitch Material UI as a solution if I could link to documentation covering the library's support for ADA compliance.

I know Material UI does have at least some support for ADA/WCAG compliance, for instance through the use of "aria-" and "role" html attributes throughout the codebase to assist screen readers and the support for keyboard navigation such as in the Select component.

Meanwhile, Material Design itself seems to lend itself nicely to following the WCAG guideline, for instance with regards to readability, navigation and high contrast text.

However, without being a core contributor myself, I cannot speak to the library's compliance overall. I searched the material-ui.com website as well as past/present GitHub tickets and could not find a page in the documentation whose sole purpose was to outline what it does and does not do to be ADA compliant. Therefore, I am opening this ticket as a feature request to please create said documentation.

[oliviertassinari]

We are doing our best to make Material-UI accessible, following the WCAG guideline. Now, we have never passed or tried to pass the ADA certification. Could you find any specific problem?

[jmadson]

@oliviertassinari Thanks for the fast reply. I have definitely noticed attention to following the WCAG guideline within the Material UI codebase. There is no specific problem, just a desire to share a documentation link with my employer covering a high-level overview of Material UI's compliance with the WCAG guideline. I imagine this could be useful for others as well.

[josgraha]

Today I learned from our accessibility expert that most big companies publish a VPAT (Voluntary Product Accessibility Template) which lists all of the known issues. Here is the download link for the VPAT one of Microsoft's products.
https://www.microsoft.com/en-us/download/details.aspx?id=8937

Basically it just provides a date and lists all of the known issues against the success criteria. This VPAT is old and newer products would use the 38 success criteria in WCAG-2.0.

Maybe an actionable item of this issue would be to create a WCAG-2 VPAT for MUI?

[eps1lon]

It would be more helpful to have a checklist against we can verify our components. Knowing unknown issues is somewhat harder than verifying that something is working.

Many of those guidelines are not really actionable for us since we can't always verify what DOM attributes have to be set and where. Maybe we can improve/document integration with eslint-plugin-jsx-a11y.

[bramick]

I'm actually in the process of reviewing MUI for WCAG 2.0 AA as we speak. Mostly notating aria and role. After that I plan to go to each component and see what's missing from compliance. I'd be interested in contributing to this if we can figure out an acceptable documentation process.

For clarity, ADA does not have a web/interactive compliance. It does however state

The ADA encourages self-regulation of accessibility standards and the Department of Justice is currently developing regulations to provide specific guidance to the entities covered by the ADA. Organizations are encouraged to use the WCAG 2.0 level AA guidelines as a guide on how to become accessible until the DOJ defines the regulations.

[mbrookes]

if we can figure out an acceptable documentation process

We already have an accessibility section in some demo pages, so it would be good to have consistent documentation across the board as to what accessibility MUI provides out of the box, and which ones the developer needs to address.

We do show this in the examples, but it would be good to call it out explicitly.

[Mobilunity-Com]

Hello! I'm really glad to join this thread about ADA. I found great article about WCAG & ADA web compliance. If you want you can read it and share your thoughts after reading. Hope you like it! Because I found it really useful.

[oliviertassinari]

Does anyone know an audit accessibility company that could audit all our components for the ADA compliance? Bonus point if the company can sponsor it for a popular OSS project.

[bramick]

We've been using https://www.powermapper.com/buy/all/sortsite/

…

On Wed, May 15, 2019, 6:12 AM Olivier Tassinari ***@***.***> wrote: Does anyone know an audit accessibility company that could audit all our components for the ADA compliance? Bonus point if they can sponsor it for a popular OSS project. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#14187>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLMBUJ6D3QHNW3G4UI34O3PVPVZ5ANCNFSM4GQFAB2Q> .

[oliviertassinari]

@bramick I'm looking for manual tests.

[bramick]

This might be a good one to reach out to: https://accessible360.com/ Michele Landis looks like a good member to reach out to.

…

-- R. Blake Ramick Mobile: 214.454.5760 www.LinkedIn.com/in/bramick

On Wed, May 15, 2019 at 9:13 PM Olivier Tassinari ***@***.***> wrote: @bramick <https://github.com/bramick> I'm looking for manual tests. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14187>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLMBUNOFFKIZLM2OQJ2723PVS7LPANCNFSM4GQFAB2Q> .

[bramick]

Or perhaps https://www.linkedin.com/in/connor-born-b8738328/ -- R. Blake Ramick Mobile: 214.454.5760 www.LinkedIn.com/in/bramick

…

On Thu, May 16, 2019 at 8:47 AM Blake Ramick ***@***.***> wrote: This might be a good one to reach out to: https://accessible360.com/ Michele Landis looks like a good member to reach out to. -- R. Blake Ramick Mobile: 214.454.5760 www.LinkedIn.com/in/bramick On Wed, May 15, 2019 at 9:13 PM Olivier Tassinari < ***@***.***> wrote: > @bramick <https://github.com/bramick> I'm looking for manual tests. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#14187>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABLMBUNOFFKIZLM2OQJ2723PVS7LPANCNFSM4GQFAB2Q> > . >