Hi, I have listened to one of our courses with the LMS inbuilt screen reader. When it reached a component it does not appear to give time to allow the user to action. So for an example an accordion, the screen reader just whips ahead and reads the headings but does not give me time to click to read the accordion contents. Please advise how I can slow this down TIA
Hi @Shane, firstly it’s great to hear you have been carrying out your own accessibility testing! It’s hard for me to know the quirks of an LMS inbuilt screenreader, but to me that sounds like a ‘command’ issue rather than a functional issue with Evolve.
Screenreaders have a tendency to go into a ‘read all mode’ sometimes when a piece of content first loads - I have had this happen with JAWS and NVDA. Usually, to stop a screen reader doing that once its started its pressing the spacebar. You would need to refer to the documentation for the LMS that covers the screenreader, and find out what the different keyboard commands are for navigating. It sounds like you need a different command to go through the content bit by bit.
For example, when I am testing with JAWS. NVDA or VoiceOver, I use the commands that will let me step through all the content on a page. In JAWS its the down arrow, and in NVDA its holding caps lock down and the next arrow. Note that this is different to using the tab key to move through a page, as this just jumps from interactive element to interactive element, and doesn’t read content.
Lastly, I would guess if a screenreader user access the course on the LMS, chances are they would use the screenreader they normally use, and not switch to a different tool just for the LMS - but that’s just a guess on my part!
Cheers-Sam
4 Likes