Task-Oriented Course Example


Task-Oriented Screen

In my blog article last week entitled “The Death of the (e)Learning Course Objectives Screen,” I showed some screenshots of a task-oriented course I produced which immediately engages the learners and brings them into the course.  While I incorporated screenshots in the course, I realize there’s nothing better than seeing the real thing.  So if you’d like, check it out for yourself. Watch how the “supervisor” avatar gives the assignment then actually leaves and heads off to a meeting, leaving you – the learner – there to figure out what to do next.  After you complete the task, the supervisor returns to comment on your progress. Click the image to launch the course.



4 Responses

  1. This format is perfect for the majority of training I’ve needed to get past friction points with seemingly simple tasks. The supervisor’s level of direction, and departure seemed appropriate, too. Thank you!

  2. Some suggestions after running through your course with JAWS. 1) There is no keyboard focus field indicator which will be an issue for users restricted to keyboard only. Follow my instructions in my blog post here to fix that – https://elearning.adobe.com/2017/05/maintaining-keyboard-focus-accessibility-tip/ . 2) You are missing some accessibility details in my slides. There is no slide accessibility text for the slide itself to alert the screen reader that a new slide has appeared, its contents, and instructions on what to do. As a blind user, I would not know I needed to tab down to access the main menu buttons. You could use JavaScript code to program the keyboard focus to automatically shift to the first button to make things a little more fluid. 3) While your buttons are labeled, you should probably add button to the accessibility text just to make it clear to the user. Example – “Create a PD button”. Also, your text boxes are not included in the tab order. If you change them to smartshape buttons (turn off rollover/down states, Set No Action, put in accessibility text) then your text boxes will be included in the tab order and can be more easily accessible. Same goes for your images. Put an invisible smartshape button over the image with the appropriate accessibility text. Your PD Generator interaction would need to have both smartshape buttons and JavaScript focus codes for a blind user to make sense of it. JAWS does not recognize any of your static elements on the pages when tabbing. 4) Any audio or narration should have a pause/play element. Not all users want to listen to narration, no matter how good it sounds, and may prefer accessing a narration transcript with their screen reader. WCAG Guideline 2.2.2 suggests “For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential”

Leave a reply