Idaho Official Government Website
|

Instructional Design

Focus: Creating online employee trainings within an LMS platform (eLearning, forms, multimedia) and overseeing third parties or vendors in their development of trainings on behalf of the State of Idaho.


Responsibilities

  • Provide alternative text and descriptions for images, icons, and diagrams.
  • Ensure video content has captions, transcripts, and audio descriptions.
  • Structure slide content with consistent headings and logical reading order.
  • Test that all navigation and interactive elements are keyboard accessible.
  • Avoid hover-only or gesture-only interactions.
  • Make sure tooltips and pop-ups are reachable by keyboard and persist long enough to read.
  • Make sure quiz questions have clear labels, instructions, and error messages.
  • Ensure responsive modules work on mobile and reflow appropriately.
  • Test modules for keyboard accessibility, test with screen readers, and use other avenues of manual testing necessary to ensure full accessibility.
  • Test keyboard-only navigation and ensure there are no traps or dead ends.

Relevant WCAG 2.1 new success criteria

The success criteria states that content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. 

Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where content is not necessarily restricted to landscape or portrait display orientation. 

Key takeaway: Content must not lock orientation. Users should be able to view visualizations in either portrait or landscape unless essential.  

Sufficient techniques: 

How it applies to instructional design 

  • Design learning modules, slides, interactions, and assessments that function correctly whether the learner is using their device vertically or horizontally. 
  • Avoid creating training layouts that break when a learner rotates their device.  
  • Reconfigure videos, images, and infographics to scale correctly in both orientations. 
  • Test mobile views of training modules for readability and accessibility. 

Video orientation failure and success

 

The success criteria states that content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:  

  • Vertical scrolling content at a width equivalent to 320 CSS pixels; 
  • Horizontal scrolling content at a height equivalent to 256 CSS pixels. 

Except for parts of the content which require two-dimensional layout for usage or meaning. 

Key takeaway: Learners must be able to zoom to 400% or use training modules at narrow widths without losing functionality (no horizontal scrolling). 

Sufficient techniques 

How it applies to instructional design 

  • Make sure slide-based modules don’t contain fixed-width text boxes that break at small viewports. 
  • Avoid placing critical instructions on the far left/right edges where reflow might hide them. 
  • Make sure image-based content has text alternatives so zooming doesn’t break comprehension. 

Reflow failure (horizontal scrolling required)

Reflow success (no horizontal scrolling)

Tools 

  • Manually test by using browser zoom to 400%.

The success criteria states that the visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):  

  • User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; 
  • Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. 

Key takeaway: Non-text elements (such as icons, charts, graphs, diagrams, data points) must be visually recognizable. Instructional designers often reference visuals in directions, so clarity is critical.  

Sufficient techniques 

How it applies to instructional design 

  • When selecting color palettes, ensure that each data series meets the 3:1 contrast ratio relative to its background and adjacent elements. 
  • Avoid relying only on faint color differences to differentiate series — use patterns, markers, shapes, and outlines. 
  • When building custom interactions (drag-and-drop, click-to-reveal), make sure all interactive objects remain visible under low vision.  
  • Add borders or outlines around low-contrast elements when necessary (e.g., pastel bars). 
  • When exporting visuals (PNG, SVG, embed), check that contrast hasn’t been reduced due to compression or theme settings. 
  • Provide alternatives for complex visuals, such as: 
    • descriptive summaries 
    • downloadable data tables 
    • text alternatives for key insights 

Icon color contrast failure and success

Tools 

Examples of graphics the success criterion applies to

Icons, graphs, diagrams, and infographics are examples of graphic objects that are composed of lines or shapes and a limited color palette over which the content author has creative control. Instructional designers should ensure that these graphics conveying important information have a 3:1 contrast ratio against the background.

Note: Not every graphical object needs to contrast with its surroundings; only those that are required for a user to understand what the graphic is conveying.

Exceptions 

  • If a graphic contains text that is embedded or overlayed and conveys the same information. An example would be the labels and values on a bar graph.  
  • The graphic does not convey any meaningful information and is for decorative purposes only. 
  • The information is available in another form. 
  • The graphic is part of a logo or brand name.  

The success criteria states that in content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:  

  • Line height (line spacing) to at least 1.5 times the font size; 
  • Spacing following paragraphs to at least 2 times the font size; 
  • Letter spacing (tracking) to at least 0.12 times the font size; 
  • Word spacing to at least 0.16 times the font size. 

Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script. 

Key takeaway: Instructional content must be created with flexible spacing; not fixed line height paragraphs or tightly packed text boxes. Users must be able to increase text spacing without breaking the layout.  

Sufficient techniques 

How it applies to instructional design 

  • Avoid manually adjusting line heights or stacking text tightly in slide-authoring tools. 
  • Avoid “click-to-reveal” layers with cramped text that will break under increased spacing. 
  • Ensure captions and onscreen instructions remain readable when spacing changes. 
  • Avoid formatting text inside images; use real text whenever possible. 

Text spacing failure

Text spacing success

Tools 

  • Use the browser’s zoom controls to magnify the content to test for any overlapping. Note if there’s any horizontal scrolling necessary to read the text.  

The success criteria states where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:  

  • Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; 
  • Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; 
  • Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. 

Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author. 

Key takeaway: When additional content appears on hover or focus, it must remain visible when the pointer is over it, not disappear immediately when moving to the tooltip, and be dismissible. 

Sufficient techniques 

How it applies to instructional design 

  • Ensure tooltips and pop-ups remain open long enough for reading. 
  • Enable keyboard access to tooltip-triggered insights. 
  • Avoid hover-only access — provide click or focus equivalents. 

Content on hover failure

Content on hover success

Tools 

  • Manually test the page with keyboard navigation (Tab / Shift+Tab) and note any content that appears and disappears when focused on specific elements. 

The success criteria states that if a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:  

  • Turn off: A mechanism is available to turn the shortcut off; 
  • Remap: A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt); 
  • Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus. 

Key takeaway: Single-character keyboard shortcuts must be reversible or only work when an element has focus. If training modules use keyboard shortcuts, they must not trigger unexpectedly.   

Sufficient techniques 

How it applies to instructional design 

  • Make sure character-only shortcut keys can be turned off/modified using one or more modifier keys. 
  • Scope shortcuts to focused elements only.  
  • Test different devices and assistive technologies to check for any accidental keyboard shortcut triggers.  

Tools 

  • If information on shortcut keys is not available, check code for shortcut keys or manually search for them using the keyboard for every character.  

The success criteria states that all functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. 

Note: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology). 

Key takeaway: Training modules must not rely on multi-touch gestures for essential interactions. 

Sufficient techniques 

How it applies to instructional design 

  • Avoid requiring pinch-zoom for navigation. Instead provide a zoom in and out options. 
  • Avoid swipe-only navigation and provide buttons for “next/back”.

The success criteria states that for functionality that can be operated using a single pointer, at least one of the following is true:  

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function; 
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; 
  • Up Reversal: The up-event reverses any outcome of the preceding down-event; 
  • Essential: Completing the function on the down-event is essential. 

Key takeaway: Users must be able to cancel or avoid accidental activation of touch interactions. A tap should not trigger immediate irreversible action.  

Sufficient techniques 

How it applies to instructional design 

  • Allow users to review and confirm their action before critical information is submitted. 
  • Prevent accidental activation when dragging or touching data points. 
  • Manually review your training course and make sure all necessary pointer cancellations are there.  

The success criteria states that for user interface components with labels that include text or images of text, the name contains the text that is presented visually. 

Note: A best practice is to have the text of the label at the start of the name. 

Key takeaway: The visible text label must match the accessible name used by assistive technologies. This includes buttons, toggles, legends, filters, and map tools. 

Sufficient techniques 

How it applies to instructional design 

  • Buttons with visible text (like next or submit) must use the same label in the accessible name. 
  • Example: If the visible text on a drop-down menu says “Filter,” the accessible name should also be “Filter” and not “Refine Results.” 
  • Correct HTML:  
    • <label for=”filters”>Filters</label> 
    • <select id=”filters” name=”filters”> 
  • Incorrect HTML: 
    • <label for=”filters”>Filters</label> 
    • <select id=”filters” name=”Refine Results”> 
  • Avoid icon-only buttons unless they have appropriate accessible labels.  

The success criteria states that functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:

  • Supported Interface: The motion is used to operate functionality through an accessibility supported interface;
  • Essential: The motion is essential for the function and doing so would invalidate the activity.

Key takeaway: If content uses device motion for interactions (such as shaking, tilting, rotating, etc.), users must have non-motion alternatives and be able to turn off motion controls.

Sufficient techniques

How it applies to instructional design

  • Avoid including interactive effects or experiences that require users to move their device unless there is also a simple tap option.
  • When writing instructions, use accessible wording like “Tap to start”.
  • If you work with vendors who create interactive content, confirm that any motion‑based features have an easy non‑motion alternative.
  • Ensure that all users can participate in interactive content, including people who cannot physically move their device or who have motion sensitivity.

The success criteria states that in content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Key takeaway: Screen reader users must be notified when meaningful changes happen in dashboards, charts, or map views without losing their keyboard focus.

Sufficient techniques

How it applies to instructional design

  • Ensure important status messages (like progress updates, errors, confirmations) are announced clearly and don’t rely solely on visuals.
  • Use built‑in LMS or authoring‑tool components that automatically expose status changes to assistive technology users.
  • Make sure status messages persist long enough for all learners to perceive them and don’t disappear too quickly.
  • Example: If a login attempt has invalid credentials the status message would be “The username or password is not correct. Please try again.”

Successful status messages