Georgia Tech Research Institute
 
Issues

Labeling: Issue 6 of 6

Issue: Instructions may be difficult for users with cognitive impairments to understand.

A museum kiosk screen shows three icons (history, culture, and science), along with a set of complex instructions that read 'The museum is divided into three section.  There aer subcategories under each.  Please select the category that best describes your interest.'

Instructions that are poorly written, overly complex, or that are written at too high a reading level may lead to comprehension problems for users with cognitive impairments. Instructions describing a series of sequential actions may also be confusing, if the instructions are poorly structured.

Populations Impacted: Users with cognitive impairments.

Potential Solutions:
  • Use simple language in instructions. Use the simplest language that conveys the required information. Use familiar words, and use short sentences and paragraphs. Use the imperative form of verbs (e.g., "Insert memory card into the memory card slot" instead of "Memory card should be inserted into the memory card slot"). Use appropriate illustrations to reinforce the contents of the text.

  • A museum kiosk screen shows three icons (history, culture, and science), along with a set of simple instructions that read 'Select one of the following categories.'
  • Ensure that instructions are grammatically correct and free from typographical errors. Instructions should be reviewed by a technical writer or a proficient editor who is familiar with the device for which the instructions were written.

  • Separate steps in a sequence into individual instructions. Break instructions into individual steps that users can read and execute before proceeding to the next step. Present the steps in the order in which they must be performed, and use bullets or numbering to distinguish individual steps and reinforce the order of steps. White space should be used to separate steps.

  • Provide structure to the steps by grouping them into sub-goals. A long sequence of actions may appear to lack structure, making it difficult for users to understand. Provide structure by using headings to group sets of related steps. Use of indentation can help delineate sets of sub-steps.

  • Ensure that the sequence of actions is presented unambiguously and in the proper order, especially if the instructions are presented via speech output. Instructions for actions should be presented in the order in which they are to be executed (e.g., "Press the eject button before removing memory card" instead of "Before removing memory card, press the eject button").

  • Place CONDITION before ACTION. Goals or conditions for action should be presented before the action, especially if the instructions are presented via speech output. For example, use the form "To view directions to your selected destination, press 1" rather than "Press 1 to view directions to your selected destination."

  • Test instructions with members of the user population to ensure that they are easy to understand and to follow. User testing will help identify potential sources of errors or confusion in instructions. Care should be taken to sample a representative portion of the targeted user population, including users with disabilities.

Applicable Guidelines:
Section 255 - 1193.41(i)(2)(e), 1193.41(i)(2)(f)
HFDS - 2.6.3, 4.3.5.4.2, 4.3.5.4.3, 8.2.5.2.2, 15.5.1.1.1, 15.5.1.1.2, 15.6.2.3
EITAAC - 5.2.1.9.1, 5.2.1.10.1
ISO/IEC 71 - 8.7.2, 8.7.3, 8.7.4
﻿
https://accessibility.gtri.gatech.edu/assistant/products/kiosks/issue_labels6.php
accessibility.gtri.gatech.edu
crawl=CC-MAIN-2020-40
11665
application/http; msgtype=response
sha1:7O3XWTW4XA5FSJCMGQFZF64F34Z7LGOA
<urn:uuid:a23d8c17-1483-40ea-89a7-597ed6ed6aed>
2020-09-27T14:35:24Z
130.207.211.191
application/xhtml+xml
sha1:HHFJ43CGE2L3HJ3CYEZNVIEMUA4DJTXU
<urn:uuid:aa71eed1-73c7-4704-805e-4aa27c8c8f18>
https://accessibility.gtri.gatech.edu/assistant/products/kiosks/issue_labels6.php
response
<urn:uuid:1be60e53-9f46-4888-9d65-f7f2c03fa826>
isPartOf: CC-MAIN-2020-40
publisher: Common Crawl
description: Wide crawl of the web for September 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-108.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/