Accessibility - non-compliant components

Hi all,

I was wondering if there is any information available regarding the components that aren’t accessible (carousels, simulation etc.) that relates to why they aren’t accessible?

There is a load of great information provided by the Evolve team as to what is compliant, and how to make the most accessible courses, but I can’t find any information about what makes certain components non-compliant. It would be great to have this kind of information so we could have even more informed conversations with client’s as to what can and can’t be used, and why.


1 Like

Hi @andyontrack I agree and I’d like to see if we can get some more info around that as while there are some components that are inherently inaccessible (e.g. Simulation) there are also some that are accessible to some extent even if not Level AA (e.g. Image Slider, Gif), There’s also one or two components that might just past muster if configured in a very specific way - and some aren’t currently accessible but could be made to be with more development.


Hi Matt, thanks for your reply. 100% agree. I’m assuming all those that are labelled as non-compliant shouldn’t be used at all, but there may be some use cases where they are acceptable. Knowing the parameters of what makes them non-compliant will allow us to make much more informed design decisions. That, and I’m genuinely curious about the specifics of what makes something compliant/non-compliant! :slight_smile: