Accessibility Features of Popular Authoring Tools
- 1. Evaluating the Accessibility Options in Popular Authoring Tools Diane Elkins Artisan E-Learning
- 2. Special Thanks • Rhonda Willis, CDC • Josh Miller, 3PlayMedia • Tanya Seidel, Trivantis • Jeanette Brooks and Arlyn Asch, Articulate • Allen Partridge and Sushma Vichwas, Adobe
- 3. Primary Concerns Text equivalents for visual elements Keyboard access No recognition of color required Size and contrast Text equivalents for auditory elements Keyboard access Medium to large elements
- 6. Not LEGAL Not LEGALDESCRIPTIONS DESCRIPTIONS Section 508 Paraphrased § 1194.22 Web-based intranet and internet information and applications. a)Text equivalents are provided for non-text elements b)Alternatives for multimedia are synchronized c)Information conveyed with color is also available without color d)Style sheets are not required e)For server-side image maps, provide redundant text links. f)Client-side image maps shall be provided instead of server- side image maps… g)Tables need identifiable row and column headers h)Tables with multiple headers need identifiers
- 7. Not LEGAL Not LEGALDESCRIPTIONS DESCRIPTIONS Section 508 Paraphrased § 1194.22 Web-based intranet and internet information and applications j)Frames need identifiers k)No flicker between 3 Hz and 54 Hz. l)Use a text-only page with equivalent information or functionality if compliance is not possible m)Information provided by scripting languages needs to be identified with text that can be read by assistive technology. n)Provide links to players, plug-ins, etc. o)Online forms need to be accessible p)Allow users to skip repetitive navigation links. q)Give students extra time for timed responses.
- 8. Determining Your Requirements • Legal Requirements • Legal Ramifications • Current audience • Future audience • Support staff • Reasonable accommodation • Instructional design needs
- 9. Design Considerations • Instructional Integrity • Optional vs. Required Course Features • Preference Settings • Alternate Paths • Usability • Instructions
- 11. Feature Comparison Feature Captivate Lectora Storyline Transcript • Static text boxes can be added for transcript text. • Static or scrolling text boxes can be added for transcript text. • Notes panel displays transcript text. • Static text boxes can be added for transcript text. Closed/Open Captions • Caption text and time stops can be added in a dialog box. Captions are displayed in an overlay at the bottom of the slide. • Text captions can be added to the slide and manually timed to audio. • You can import closed captions to FLV audio or video using an XML file. • Text captions can be added to the slide and manually timed via actions. • Text captions can be added to the slide and manually timed to audio. Alternative Text • Object name can be used as alt text. • You can enter a longer description in a dialog box. • Non-content objects can have empty alt text. • Object name can be used as alt text. • You can use separate text box for descriptions longer than 128 characters. • Non-content objects can have empty alt text. • Object name can be used as alt text. • You can enter a longer description in a dialog box. • Non-content objects can have empty alt text. Screen Reader Process • User must press Ctrl+Home (or similar) on each slide. • Objects are read when tabbed to. • All objects that appear on page load are announced automatically. • Objects that appear after page load are read when tabbed to. • Objects are read when tabbed to. Tab/Screen Reader Order • Screen is read from top to bottom and left to right. • Third-party widget is available to adjust tab order. • Order is determined by order in object list, which is also the front-to-back order. • Screen is read from top to bottom and left to right. Tables • There is no native table function. Tables imported as graphics may not be accessible. • Tables with a single row heading and single column heading can be made accessible. • There is no native table function. Tables imported as graphics may not be accessible.
- 12. Feature Comparison Feature Captivate Lectora Storyline Screen Reading of Timed Objects or Objects Shown via an Action • Objects are accessible only while they appear on the slide. • Slide objects cannot be played independently of the audio. • Objects that appear on page load are announced automatically. • All objects are accessible once they appear when tabbed to. • Slide objects can be played independently of the audio. • Objects are accessible only while they appear on the slide. • Slide objects cannot be played independently of the audio. Rollover Actions (Mouse Enter/Exit) • Rollover actions trigger when object is tabbed to. • Rollover actions are not keyboard accessible. • Rollover actions are not keyboard accessible. Displayed Variables • Screen readers read the name of the variable instead of the value. • Screen readers read the value of the variable. • Screen readers read the value of the variable.** Accessible Question Types • Multiple choice • True/false • Rating scale • Multiple choice • True/false • Short answer • Essay • Fill in the blank • Likert • Ordinal • Multiple choice** • True/false** • Matching drop-down** • Sequence drop-down** • Likert** • Fill in the blank • Numeric • Short answer • Essay Inaccessible Question Types • Fill in the blank • Matching • Hot spot • Short answer • Sequence • Matching • Drag and drop • Hot spot • Likert scale • Word bank • Matching drag and drop • Sequence drag and drop • Hotspot Skip Navigation • Not applicable as the entire project plays on a single HTML page.* • Action can be added to the interface to skip repetitive elements. • Items in the navigation bar (menu bar, etc.) are read on every page and cannot be skipped. Preferences • Variables can be used to track accessibility preference and change settings accordingly. • Variables can be used to track accessibility preference and change settings accordingly. • Variables can be used to track accessibility preference and change settings accordingly.
- 13. Appendix: The official 508 language
- 14. Section 508: Official Standard § 1194.22 Web-based intranet and internet information and applications. (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. (d) Documents shall be organized so they are readable without requiring an associated style sheet. (e) Redundant text links shall be provided for each active region of a server- side image map. (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. (g) Row and column headers shall be identified for data tables. (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. (i) Frames shall be titled with text that facilitates frame identification and navigation.
- 15. Section 508: Official Standard § 1194.22 Web-based intranet and internet information and applications. (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text- only page shall be updated whenever the primary page changes. (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. (o) A method shall be provided that permits users to skip repetitive navigation links. (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.