TAG – Training Accessibility Guidelines (Question 14)
The examples discussed below will focus on using two popular training development tools (Articulate Storyline 2 and Camtasia Studio).
Content will focus on how you can meet the success criteria for each section of the WCAG 2.0 Guidelines.
Content Recommendation is for the following WCAG 2.0 Sections:
1.4.4 Resize text
Questions to consider:
|Is the screen readable and functional when the text size is doubled?|
How Articulate Storyline 2 can meet success criteria:
- No built in zoom feature is provided by Articulate Storyline 2.
- Zoom can be implemented for an embedded webpage.
- IE 11 using the (CTRL and +) together does permit a zoom level of 1000% without pixelization and/or lost of readability.
Your comments and suggestions are welcome please post below to assist in improving this document. Take note discussion need not be limited to the development tools provided.
What are the best options to meet WCAG 1.4.4 Resize text when using Articulate Storyline?
Here are a list of recommendations based on existing development tool limitations as of May 2, 2016.
1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)
STORYLINE – ANSWER EXTRACTED FROM SUPPORT GROUP
Official Answer from Articulate:
More discussion on the topic:
It is in my opinion that the answer provided is not a correct interpretation of the requirement – As font size can not be dynamically changed by a user and must be done at the developer level with access to the source file.
WCAG FOR ELEARNING TOOL
Also refer to question 14, when using this tool: http://www.cansomebodyhelpme.com/wcag/story.html
- Provide an embedded HTML version of the entire course include navigational controls or/jump links using HTML anchor tags to specific target content groupings.
- Implement self identification slide, it is the solution we use. If you use accessibility software we provide a higher end accessible product with more accessible features. Take note that it is important to deliver the correct product to the correct target audience that is why we have implemented self-identification. A user would provide at the start of a course that they are using accessible software such as ZoomText, Dragon or Jaws.
CREATING AN ACCESSIBLE GRAPHIC USER INTERFACE
- An optimized GUI for an accessible user is often simplified with access to all the same content.
- An optimized GUI for a non-accessible tool user is often more complex with access to all the same content.
EXAMPLE OF CUSTOM CONTENT FOR ACCESSIBLE TOOL AND NON ACCESSIBLE TOOL USERS
- We turn off our voice over track so Dragon users do not hear two sets of audio describing the same screen at the same time (Dragon audio and our audio). We also provide instructions on how Dragon works best when navigating a Storyline Project (Not all Dragon commands work with Storyline).
- We provide a downloadable SRT Caption for those who have self-identified as using an accessible tool. However this feature does not need to be provided to non-accessible tool users.
Please feel free to share your comments below.