Forum Discussion
Most accessible interactions
Hi LisaEdmondson-4 the following link provides information on which interactions are accessible, and which are not: https://www.articulate.com/about/accessibility/storyline-360-accessibility-conformance-report-vpat/
It is possible to make the drag and drop interactions keyboard accessible, but treating the interaction differently. For example, allowing the keyboard user to "select" the drag item, then tab to the drop target and "select" the drop target. You can then have a trigger that checks if X is selected and Y is selected, then correct and so on. This is a simplified explanation, as they is more to it than that, but this is the solution that is required.
Hi LisaEdmondson-4
Perhaps a bit late on your post but recently discovered this Accessibility group.
I have been advocating for accessibility in my team for a few years. I understand and agreed about the accessibility issue with drag and drops. I haven't watched the video provided at another reply but one of the biggest issue with drag and drops are that they are not workable if your learners are in a mobile devise and they tend to be very difficult with keyboard focus too.
To be honest it also depends on your target audience and what accessibility consideration you may need to put up-front in your design/development process.
We (in me team) have decided not to use drag and drops and what I did to compensate that was a different interaction that delivers similar results, basically a "select from list" type of interaction. So far working well.
My advise for you is to always put accessibility up-front in the process and to understand your user needs. There are accessibility standards that are a must but some others are audience specific.
I would advise, for anybody considering using Storyline 360 to deploy mobile learning. Don't.
It is not a fit for purpose tool and was developed long before mobile learning was a thing.
If you must use Articulate software, to build mobile learning, you should definitely leave SL360 on the shelf, and reach for R360 instead.
The way that SL360 "scales" content, rather than adapts it to the screen is not conducive to a good learner experience, and it is very likely to be unusable for many users as it presents fine motor and visual impairment issues.
I see that you suggested that SL360 should be moved away from due to the learner experience and its stability. Are all the blocks on R360 accessible (say, the built-in drag-and-drop)? Do you think this recommendation holds true today?
I find myself torn between the two tools as I like the ease of R360 build, but I know some users (especially my target audience, veteran teachers), gravitate to the PowerPoint-like slideshow look of SL360. What are your thoughts?
Hi snugent. Storyline 360 is a stable piece of software, it's just not responsive and so is not fit for mobile. The content is scaled to fit different device sizes meaning elements can end up being too small to read and interactive with on mobile.
In my opinion, if you are building content to be mobile compatible, it's not a decision to be made on preference of slideshow style, as it just won't be fit for mobile.
If you are building for mobile, Rise 360 is definitely the way to go for responsive content. Most blocks are accessible, but you should refer to this document to see which blocks are not yet fully accessible:
https://www.articulate.com/about/accessibility/rise-360-accessibility-maturity-plan/
You could break up Rise content into several pages if you want that individual slide feel rather than multiple blocks on a single page.
