We had this question from a Montgomery
County site client.
Answer from our Instructional Design Director, Jessica Trace.
Side note: We used to always add a popup message at the beginning so that people who are Deaf or hard of hearing know where to locate that, but for some reason we've moved away from that. I think it stopped happening when we moved into Storyline; was a detail we used to always add into courses in SmartBuilder and was lost in the transition to Storyline. We can always add it into specific courses if need be, and I will make a note to start re-adding that into courses moving forward.
Here is a good list from the Articulate website to show what features are built into the software: https://www.articulate.com/products/storyline-section-508.php
Answer from our IT Director, Mike Maether.
Going through these lists we compensate for nearly everything. We follow the best standards for HTML development, which in turn takes care of most accessibility requirements. We always provide alt tags for images and add descriptive tags as part of creating clean code. There's a checklist on the Tech Republic site that we follow pretty closely, so for more details you can take a look there. More recently we've also been implementing aria tags, which although aren't required for the ADA compliance, they are newer HTML tags that will make the site even further accessible, which I can say most sites don't implement.
The only one I noticed that we may not compensate for relates to PDF documents on the site. The requirement states to post all documents in a text-based format, so for every PDF that we have we should also have a plain text alternative. We don't have many PDFs on the site, and they're not essential to for using the LMS. However, I did notice that PDFs do compensate for accessibility, so this point may be moot.