Hey team!
I’ve just had someone from my team who uses ‘Spoken Content’ (an Apple feature that enables devices like iPhones, iPads, and Macs to read aloud various types of content) to test one of my modules. Clickable content (buttons, multiple-choice answers, links, etc.) is not read aloud to them with this feature.
Is there a reason for this? The content is accessible via Apple VoiceOver, but this is not their preferred tool.
I really appreciate any help you can provide 
Jess
Hi @JSobanski that’s not a tool we have tested with or had any requests about previously. I understand that it not working on those items must be frustrating for your colleague, but with the large number of assistive technologies out there, it’s very tough for us to guarantee support for them all - we do our best to make evolve accessible, and that’s why we are externally audited every year and are able to certify most of the component and extensions as conformant with WCAG 2.1 AA. I will ask my colleagues about but I’m not sure if there’s an easy solution I’m afraid.
Cheers-Sam
Hi @JSobanski - this is fairly typical behaviour for tools like this which are really aimed at reading out ‘web article’ style content rather for accessing interactive content like e-learning.
If you look at the help article for this feature you’ll note that it specifically says that it reads out ‘text that’s on the screen’. It also references VoiceOver as the tool to use if you need to actually interact with content on the screen.
Also see this post about Microsoft Edge’s ‘reader’ function.
Finally, just to make it clear that this isn’t just an ‘Evolve issue’, try using the Spoken Content feature with the accessibility ‘best practice’ examples provided by the W3C such as this one. Note how it only reads out the visible portion of the tabs widget, it completely skips over the tabs that are hidden.
Hey @Sam_Cook_Evolve_LQA and @Matt_Leathes,
Thanks so much for your responses! This is great insight, I appreciate it