I ran a scan from accessibe.com on the pages in a StoryMap collection that I've created for my agency. It returned a number of errors that I don't think I'm able to fix because they involve the underlying code. I'm not sure which of these are actually critical versus recommended. If anyone has any insight on the following and if I'm able to do anything about them from my end, I'd appreciate it.
Also, I tried using keyboard navigation along with a screen reader, and the swipe images that I have in my story did not respond to the arrow keys (but do work without the screen reader) - is there another shortcut or keys I should be using instead?
Thank you!
Solved! Go to Solution.
I would suggest getting in touch with your local Esri Distributor and ask them to investigate this further for you
I would suggest getting in touch with your local Esri Distributor and ask them to investigate this further for you
@KaraG - I would agree with @ShaneONeill_144 that getting in touch with your local distributor or account manager would be a good approach here. There isn't enough information about most of these issues provided here to provide a definitive response, so more discussion/info is needed.
However, I can provide information about some of these issues...
2 - Keyboard focus should have a noticeable outline -- In an update coming later next week, we will introduce a new style for the keyboard focus indicator. Please retest this later in the month.
4 - Unable to add alt text to images on collection main page - The images on the collection cover are considered decorative and do not require alt text.
Swipe keyboard navigation issue - We have addressed this in a recent release. Please retest.