Can anyone share why the iFrame component in Evolve is not accessible? Does it have to do with the content presented using iFrame, or does the component itself present accessibility barriers? I just successfully navigated the content using the NVDA screen reader, and was able to access all content using a keyboard.
Would be interested in getting additional insight on this. Thank you.
Good question. It’s one of those where it can be made to be accessible if set up correctly.
Unfortunately we haven’t managed to come up with a good way of flagging those in Evolve - though we did (recently) add this to the KB article:
This component is recommended for use when creating accessible courses ONLY if the content that will be displayed in the iFrame meets the appropriate level of accessibility for the target audience.
We had concerns that if we labelled it as ‘Accessible’ people might assume it automatically makes any content displayed in it accessible.
If you’ve tested it and you’re happy that it works OK with a screen reader then it should be fine to use.
One thing you might consider (if you haven’t done already) is adding a short description of the content for screen reader users in General > iFrame Title.
Thank you for the info, @Matt_Leathes. I’m glad to know it’s more about the content being presented using the component, as opposed to the component introducing an accessibility barrier.