Closed canstudios-nicolaw closed 1 year ago
oliverfoster
commented
5 years ago Yup, this is pretty much expected. Narrative mobile view needs some serious work. I was going to wait until after v5 release to tackle this but I'm happy if you're willing to get it working?
canstudios-nicolaw
commented
5 years ago I can't make any promises right now I'm afraid, I was just raising this for the record rather than expecting anyone to pick it up immediately. We've got an internal discussion about priorities tomorrow morning so I will bring this up and see how much work we would be willing to put into this component in the near future. We have got a lot of interest in helping to make more components accessible at the moment (it's just driven by which ones our content team use the most).
oliverfoster
commented
5 years ago We've concentrated on desktop view only at the moment. Which leaves the small subset of mobile adaptive components which aren't currently accessible at mobile size.
joe-allen-89
commented
1 year ago When in mobile view the screen reader reads out strapline as a button followed by the graphic alt text, back button and finally the next button before navigating you to the next component. Focus is shifted to the content when content button is selected and popup appears. This appears to have been fixed by https://github.com/adaptlearning/adapt-contrib-core/pull/90
There are some accessibility issues when using this component in mobile view.
Your environment
Steps to reproduce
The strapline is not read out by screen readers on mobile. The screen reader reads out items in the following order (which seems strange):
Expected behaviour
The strapline should be read out by screen readers, the items should be read out in a logical order.
I realise that this could be a low priority issue due to it being a mobile-only accessibility issue.