MIL-STD-1472 Compliance
The Astro Space UX Design System is designed to support the development of custom space applications with established interaction patterns and best practices. To this end, Astro UXDS strives to achieve compliance with applicable DOD design standards. Astro 7 was audited to determine its level of compliance with relevant items in Section 5.17 (Information Systems) of MIL-STD-1472, and as of September 29, 2022 this is our assessment of Astro UXDS compliance.
For the items determined to be Non-Compliant, we are looking at the level of effort to achieve compliance.
For the items determined to be Not Applicable to Astro UXDS, many times the onus is on the application developer to ensure compliance for those items is met. Astro UXDS often offers guidance or components that can help achieve compliance, but cannot do so directly.
If you have a question on Astro compliance or would like to give feedback, please submit your input here.
| Section | Description | Astro UXDS 7.0 Compliance |
|---|---|---|
| 5.17 | Information systems. | |
| 5.17.1 | General. | |
| 5.17.1.1 | Functional interface. Computer programs and equipment interfaces shall provide a functional interface between the system for which they are designed and users of that system. | Compliant |
| 5.17.1.2 | Compatible with personnel. Interfaces shall be compatible with the work performed by, and the cognitive processes of, personnel. | Compliant |
| 5.17.1.3 | Human performance. The interface should minimize conditions that can degrade human performance or contribute to human error. | Compliant |
| 5.17.1.4 | Display content. Equipment interfaces provide a functional interface between the system for which they are designed and users of that system. This interface should optimize compatibility with personnel and should minimize conditions that can degrade human performance or contribute to human error. | Compliant |
| 5.17.1.4.1 | Overlays. The system shall not require mechanical overlays. | Not Applicable |
| 5.17.1.4.2 | CBRNE contamination. Displays or indicators that show the presence of CBRNE agents shall also show when such agent contaminations decrease to safe levels. | Not Applicable |
| 5.17.2 | Command dialogs. | |
| 5.17.2.1 | Command language. | |
| 5.17.2.1.1 | Use. Command language may be used for tasks that involve a wide range of user inputs and where user familiarity with command language can be used to take advantage of the flexibility and speed of this control technique. | Not Applicable |
| 5.17.2.1.2 | User viewpoint. Command language commands shall be logically related to the user’s expectation of what the commands will initiate. | Not Applicable |
| 5.17.2.1.3 | Naming distinctiveness. Command names shall be distinct from one another. | Not Applicable |
| 5.17.2.1.4 | Punctuation and special characters. The command language dialog shall minimize the use of punctuation and special characters. | Not Applicable |
| 5.17.2.1.5 | Standardization. All commands and corresponding abbreviations shall be identical across systems and platforms. | Not Applicable |
| 5.17.2.1.6 | Standard location. Commands shall be entered and displayed in a standard location on the software user interface. | Not Applicable |
| 5.17.2.1.7 | Command prompts. The user shall be provided a means, such as prompts or tooltips, to determine required parameters or available options for command entry. | Not Applicable |
| 5.17.2.1.8 | Complexity. The command language shall accommodate the skill levels of users ranging from novice to experienced. | Not Applicable |
| 5.17.2.1.9 | User definition of macro commands. The command dialog shall not allow a user to name macros with existing command names (“reserved keywords”). | Not Applicable |
| 5.17.2.1.10 | Standard techniques for command editing. Command and data entries shall be edited using the same techniques. | Not Applicable |
| 5.17.2.1.11 | Destructive commands. If a command entry has destructive consequences, the system shall display the consequences of the command so that the user may review and cancel or confirm before it is executed. | Not Applicable |
| 5.17.2.2 | Question and answer. | |
| 5.17.2.2.1 | Use. Question-and-answer dialogs may be used for routine data entry tasks where data items are known, their ordering can be constrained, and where users will have little or no training. | Not Applicable |
| 5.17.2.2.2 | Questions displayed separately. For multiple questions in a dialog box, each question shall be listed separately. | Not Applicable |
| 5.17.2.2.3 | Distinct response area. When responses are required for a question, each question shall have a separate and distinct response area. | Not Applicable |
| 5.17.2.2.4 | Recapitulating prior answers. When a series of system-posed questions are interrelated, answers to previous questions shall be displayed if they provide context to help a user answer the current question. | Not Applicable |
| 5.17.2.2.5 | Source document capability. When questions prompt entry of data from a source document, the question sequence shall match the data sequence in the source document. | Not Applicable |
| 5.17.2.3 | Query language. | |
| 5.17.2.3.1 | Natural organization of data. Query languages should reflect a data structure or organization perceived by users to be natural. For example, if a user would have reason to suppose that all data about a particular topic would be stored in one place, then the query language should permit such data to be retrieved by a single query, even though various pieces of data may be stored in different computer files. | Not Applicable |
| 5.17.2.3.2 | Coherent representation of data organization. A single representation of the data organization for use in query formulation shall be established (i.e., the user does not need to know if different queries will access different databases via different routes). | Not Applicable |
| 5.17.2.3.3 | Task-oriented wording. Users shall be able to specify the data being requested in a query without being required to specify where the data are stored. | Not Applicable |
| 5.17.2.3.4 | Logic to link queries. The query language should be designed to include logic elements that permit users to link (e.g., “and”, “or”) sequential queries as a single entry. | Not Applicable |
| 5.17.2.3.5 | Confirming large-scale data retrieval. If a user’s query request will retrieve a large amount of data, the user shall be provided the options to continue, cancel, or refine the query during processing. | Not Applicable |
| 5.17.2.3.6 | Estimate of remaining time. When processing takes a long time, the user shall be provided with an indication of the status that includes an estimate of the proportion remaining in terms of either time or amount. | Not Applicable |
| 5.17.3 | Visually displayed menus. | |
| 5.17.3.1 | Menu types. | |
| 5.17.3.1.1 | Drop-down menu bars. Drop-down menus contain a list of contextual commands that are presented in a menu bar along the top edge of a window. The menu bar shall contain a set of menu category labels (e.g., Edit) from which drop-down menus are accessed. | Compliant |
| 5.17.3.1.1.1 | Use. Drop-down menus and the associated menu bars should be used when there are more than three commands and categories. | Compliant |
| 5.17.3.1.1.2 | Primary windows. Drop-down menus and menu bars should be used when commands appear in primary windows (i.e., popup dialogs). | Compliant |
| 5.17.3.1.2 | Submenus. Submenus shall consist of a group of options related to a higher-level toolbar menu item. | Compliant |
| 5.17.3.1.2.1 | Additional menu options. Submenus should allow additional menu options to be viewed without increasing the length of the overall menu. | Compliant |
| 5.17.3.1.2.2 | Shorten length. Submenus may be used to shorten the length of a long menu when a higher-level menu item may be used to describe several related functionalities. | Compliant |
| 5.17.3.1.2.3 | Frequently needed functions. Submenus should not be used for functions that are frequently needed and accessed. | Compliant |
| 5.17.3.1.2.4 | Indication. An indicator (e.g., a right-pointing triangle) should be used to display the presence of a submenu on a higher-level menu. | Compliant |
| 5.17.3.1.2.5 | Presentation of options. When the higher level option is selected, the options shall be presented without further input from the user. | Compliant |
| 5.17.3.1.2.6 | Number of levels. Submenus should be limited to three levels (i.e., Main>Sub1>Sub2) to ensure discoverability of nested items. | Compliant |
| 5.17.3.1.3 | Menu bar. Users should interact with menu bars by left-clicking the menu category within the menu bar to open the drop-down menu command list. | Compliant |
| 5.17.3.1.3.1 | Toolbar menu. Toolbars may be used to graphically present command actions for easy and efficient access. | Compliant |
| 5.17.3.1.3.2 | Use in primary windows. Toolbars should be used in primary windows to provide a small number of icons as immediate commands. | Compliant |
| 5.17.3.1.3.3 | Use in secondary windows. Toolbars should not be used in secondary windows, with text-only commands, with crowded icons, and with non-immediate commands (e.g., configuring a filter). | Compliant |
| 5.17.3.1.3.4 | Toolbar options. Toolbar options that are fixed should be limited to those commands used most frequently by a large percentage of users. Alternatively, a means may be provided for users who wish to configure them to have access to frequently accessed options. | Compliant |
| 5.17.3.1.3.5 | Toolbar labels. Toolbars with icons shall provide labels via a tooltip (hover over to show label). | Non-Compliant |
| 5.17.3.1.3.6 | Non-standard icons. Non-standard icons should be avoided but if present, shall provide labels via a tooltip (hover over to show label) and should include fixed-text labels. | Non-Compliant |
| 5.17.3.1.3.7 | Selection. Toolbar menus should be left-clicked for devices like mice and trackballs to make a selection. | Compliant |
| 5.17.3.1.4 | Ribbon menus. Ribbon menus separate dedicated task commands within a window. In these menus, a list of task-related commands appears under an active tab. Ribbon menus may be used when there are multiple menu categories with items under each category. | Compliant |
| 5.17.3.1.5 | Right-click and context menus. Right-click menus may be used to provide contextually relevant options and actions pertaining only to the selected item or pane. | Non-Compliant |
| 5.17.3.1.5.1 | Method of accomplishment. Right-click menus shall not provide the only method of accomplishing any command. | Non-Compliant |
| 5.17.3.1.5.2 | Accessibility. Right-click and context menus shall not include options that cannot be accessed elsewhere by a means that is apparent. | Non-Compliant |
| 5.17.3.1.5.3 | Availability. Right-click menus should be available to initiate basic and frequently used commands. | Non-Compliant |
| 5.17.3.1.5.4 | Not substitute. Right-click menus shall not be used as a substitute for primary menus (e.g., drop-down menus). | Non-Compliant |
| 5.17.3.2 | Using menus. | |
| 5.17.3.2.1 | Interactive menu use. Interactive menu selection shall be used for tasks that involve little or no entry of arbitrary data, users that may have relatively little training, or a command set that is too large to commit to memory. | Compliant |
| 5.17.3.2.2 | Selection method. Selection of devices shall be in accordance with the criteria in 5.17.3.2.2.1 through 5.17.3.2.2.4. | |
| 5.17.3.2.2.1 | Mouse. A mouse or other pointing input device (including touch technology) shall be an available method for menu selection (see 5.1.3.3). | Compliant |
| 5.17.3.2.2.2 | Pointing. If menu selection is accomplished by pointing, a selection action shall be made to initiate the command (i.e., left click of mouse or tap for touch input). | Compliant |
| 5.17.3.2.2.3 | Submenus. Each submenu shall have a title that clearly identifies the purpose of that menu. | Compliant |
| 5.17.3.2.2.4 | Multiple pages. Menus shall not consist of multiple pages of options. | Compliant |
| 5.17.3.2.3 | Active option presentation. Menu options that are not available shall either not be presented or be greyed out to make it clear that they are not available. | Compliant |
| 5.17.3.2.4 | Format consistency. Menus shall be presented in a consistent format throughout the system and across other related systems the user is expected to operate. | Compliant |
| 5.17.3.2.5 | Accessible. Menus shall be readily accessible at all times. | Compliant |
| 5.17.3.2.6 | Option sequence. Menu selections shall be listed in a logical order, such as alphabetically or by frequency of use. | Compliant |
| 5.17.3.2.7 | Simple menus. If the number of selections can fit on one page in no more than two columns, a single menu may be used. If the selection options exceed two columns, a hierarchical menu structure should be employed. | Compliant |
| 5.17.3.2.8 | Option presentation. Textual menu options should be presented on separate lines to ensure that the items are discriminable and selectable. | Compliant |
| 5.17.3.2.9 | Direct function call. A direct function call capability shall be provided for frequently used options. | Not Applicable |
| 5.17.3.2.10 | Shortcut commands. Shortcut commands (e.g., “control C” for copy) should be provided for frequently used actions. | Non-Compliant |
| 5.17.3.2.11 | Option coding. When selections may be made by keyboard shortcuts, the shortcuts associated with each alternative option shall be included next to the menu option. | Non-Compliant |
| 5.17.3.2.12 | Keyboard shortcuts. If menu selections are made by keyboard entry of alphanumeric codes, the options shall be coded by letters that are associated with the name of the option or standard shortcuts rather than by more arbitrary codes. | Non-Compliant |
| 5.17.3.2.13 | Duplication. Keyed codes shall not duplicate any other user function codes. | Non-Compliant |
| 5.17.3.2.14 | Position in structure. When menu selection traverses multiple levels, all of the levels shall remain visible until the selection is made. | Compliant |
| 5.17.3.2.15 | Menu hierarchy. A menu tree showing the menu hierarchy shall be included in the user manual or online Help section. | Non-Compliant |
| 5.17.3.2.16 | Tooltips. A tooltip should be displayed over an item as the user hovers the pointer without clicking on the item. | Non-Compliant |
| 5.17.3.2.17 | Icons. Menus may use icons to represent the control options. | Compliant |
| 5.17.3.2.17.1 | Currently being used. When possible, icons should be consistent with icons that are currently being used in other systems, familiar to the user, and used consistently within an application. | Compliant |
| 5.17.3.2.17.2 | Graphic menu use. Graphic menus may use icons to represent control options and be consistent within an application. | Compliant |
| 5.17.4 | Form filling dialogs and dialog boxes. | |
| 5.17.4.1 | Data entry. Data entry functions shall be designed to establish consistency of data entry transactions, minimize input actions, minimize memory load on the user, ensure compatibility of data entry with data display, and provide the user control over data entry. | Compliant |
| 5.17.4.2 | User pacing. The pace of data entry shall be controlled by the user, rather than by the system. | Compliant |
| 5.17.4.3 | Positive feedback. The system shall provide feedback to the user regarding the acceptance or rejection of an entered datum. | Compliant |
| 5.17.4.4 | Response time. Feedback response times shall be in accordance with 5.17.9.5. | Not Applicable |
| 5.17.4.5 | Processing delay. Where system overload or other system conditions results in a processing delay, the system shall acknowledge the data entry and provide an indication of the delay to the user. | Compliant |
| 5.17.4.6 | Completion time. The system should provide some indication of the completion time or of the fraction of the process completed. | Compliant |
| 5.17.4.7 | Explicit action. Each data entry shall require an explicit completion action, such as pressing an ENTER key or other key (e.g., TAB key). | Compliant |
| 5.17.4.8 | Validation. Data entries shall be validated by the system for correct format, legal value, and range of values prior to processing. | Compliant |
| 5.17.4.9 | Software-available data. The user shall not be required to enter data already available to the software. | Not Applicable |
| 5.17.4.10 | Input units. Data shall be entered in units that are familiar to the user. | Not Applicable |
| 5.17.5 | Cursors. Cursors shall meet the criteria in 5.17.5.1 through 5.17.5.14. | |
| 5.17.5.1 | Control. The user shall be able to adjust the sensitivity of the cursor movement to be compatible with the required task and user skills where appropriate. The user’s ability to adjust the sensitivity of the cursor movement shall only be provided where adjustment of this control could not adversely affect the ability to fulfill the mission. | Not Applicable |
| 5.17.5.2 | Distinctive cursor. The cursor shall have differing visual attributes that distinguish various usages, such as selecting an object or editing text. | Compliant |
| 5.17.5.3 | Distinctive cursor position. The current cursor position on graphic or image processing application displays that require precise positioning shall be indicated by displaying a distinctive cursor symbol that indicates a point (e.g., a plus-sign or crosshairs whose intersection can mark a position with reasonable precision). | Not Applicable |
| 5.17.5.4 | Obscuration. The cursor shall not obscure displayed entities. | Not Applicable |
| 5.17.5.5 | Display boundaries. The cursor shall not move beyond the display boundaries (off of the monitor) and disappear from sight. | Not Applicable |
| 5.17.5.6 | Cursor movement using arrow keys. If the cursor is moved by pressing a key, releasing the key shall cause the cursor to stop moving. | Non-Compliant |
| 5.17.5.7 | Precise positioning. Where data entry requires exact placement of graphic elements, users shall be provided the capability for expansion of the critical display area (e.g., zooming and panning) to make the positioning task easier and more precise. | Not Applicable |
| 5.17.5.8 | Home position. The home position for the cursor shall be consistent across similar types of displays. | Not Applicable |
| 5.17.5.9 | Explicit actuation. A separate explicit action distinct from cursor position, (i.e., pressing a button or toggling) shall be required for a control selection. | Compliant |
| 5.17.5.10 | Incremental cursor positioning. Where cursor positioning is incremented in discrete steps, the step size of cursor movement shall be consistent horizontally (in both right and left directions), and vertically (in both up and down directions). | Not Applicable |
| 5.17.5.11 | Keyboard cursor control. | Non-Compliant |
| 5.17.5.11.1 | Position designation. When position designation is required in a task emphasizing keyed data entry, cursor control shall be available by the keyboard, preferably using the arrow keys. | Not Applicable |
| 5.17.5.11.2 | Means of control. If keys other than the arrow keys are used for movement (as with an abbreviated keyboard), the display should clearly indicate the means of control. | Not Applicable |
| 5.17.5.12 | Movement relationships. | Not Applicable |
| 5.17.5.12.1 | User expectations. The response of a cursor to user input shall be consistent and compatible with the user’s expectations. | Compliant |
| 5.17.5.12.2 | Move in corresponding direction. For cursor control by key action, the cursor shall move in the corresponding direction of the arrow key that was pressed (i.e., left arrow to left, right arrow to right, up arrow up, down arrow down). | Not Applicable |
| 5.17.5.12.3 | Control by joystick. For cursor control by joystick, movement of the control shall result in the cursor moving in the corresponding direction (i.e., left movement moves the cursor to the left, right movement moves the cursor to the right, push movement moves the cursor upward, pull movement moves the cursor down). | Not Applicable |
| 5.17.5.12.4 | Cursor responses. Cursor responses to movements of other controls shall be in accordance with 5.17.6.16 or to the movement-related provisions of the applicable control specified in 5.1. | Compliant |
| 5.17.5.13 | Explicit delete action. Data deletion or cancellation shall require an explicit action, such as pressing a DELETE key. | Compliant |
| 5.17.5.14 | Permanent deletion. Permanent deletion (in the absence of an “undo” function) of more than one character shall not be allowed without an affirmative response to a validation query. | Not Applicable |
| 5.17.6 | Form filling. | |
| 5.17.6.1 | Use. Form filling interactive control may be used where some flexibility in data entry is needed. | Compliant |
| 5.17.6.2 | Grouping. Displayed forms shall be organized to group related items together. | Compliant |
| 5.17.6.3 | Format and content consistency. The format and content of displayed forms shall duplicate in every major parameter the (paper) form it is intended to represent. | Not Applicable |
| 5.17.6.4 | Advancing through form fields. When using TAB or ENTER keys to advance through form fields, the system shall require a response for every data entry field; advancing through a field (i.e., leaving a blank) for which no entry is desired shall require an explicit action (TAB or ENTER keystrokes). | Not Applicable |
| 5.17.6.5 | Separation. Fields or groups of fields shall be separated by spaces, lines, or other delineation cues. | Compliant |
| 5.17.6.6 | Distinctiveness of fields. Required fields shall be distinguished from optional fields. | Compliant |
| 5.17.6.7 | Field labels. Field labels shall be distinctively presented such that they can be distinguished from data entry space. | Compliant |
| 5.17.6.8 | Additional cueing. Labels for data entry fields shall incorporate additional cueing when the data format could logically be made in more than one format (e.g., “DATE (MM/DD/YYYY): _ _ / _ _ / _ _ _ _”). | Compliant |
| 5.17.6.9 | Informative labels. Descriptive wording shall be employed when labeling data fields. | Compliant |
| 5.17.6.10 | Arbitrary codes. Use of arbitrary codes shall be avoided. | Not Applicable |
| 5.17.6.11 | Top-aligned labels. Top-aligned labels shall be used when labels are long or the form requires horizontal space for grouping related input fields. | Compliant |
| 5.17.6.12 | Vertical space limited. Top-aligned labels shall not be used if vertical space is limited. | Compliant |
| 5.17.6.13 | Right-aligned labels. Right-aligned labels shall be used for forms that require users to quickly scan labels and may be used when vertical space is limited. | Non-Compliant |
| 5.17.6.14 | Left-aligned labels. Left-aligned labels shall be used when a form requires users to carefully consider labels. | Compliant |
| 5.17.6.15 | Limited vertical space. Left-aligned labels shall not be used when labels are so long that they do not allow for data entry in the same vertical space. | Compliant |
| 5.17.6.16 | Cursor default position. When a form is displayed, a displayed cursor shall be positioned at the first data entry field by default. | Not Applicable |
| 5.17.6.16.1 | Cursor advancement. The cursor shall be advanced to the next data entry field by the TAB key or the ENTER key when the user has completed entry of the current field. | Compliant |
| 5.17.6.16.2 | Exceptions. Exceptions to using the ENTER key for advancement occur in cases where some fields require or allow multiple lines to be input; in which case, only the TAB key shall be used to advance the cursor. | Not Applicable |
| 5.17.6.17 | Entry length indication. The maximum acceptable length for variable length fields shall be displayed. | Not Applicable |
| 5.17.6.18 | Maximum characters inputted. An indication shall be provided to the user if the maximum number of characters has been inputted. | Compliant |
| 5.17.6.19 | Overwriting. Characters other than those indicating format that must be overwritten shall not be entered into unfilled data fields by default. | Not Applicable |
| 5.17.6.20 | Dimensional units. When a consistent dimensional unit is intended as the unit of entry in a given field, the dimensional unit shall be provided by the computer to the right of the field. | Non-Compliant |
| 5.17.6.21 | Variable dimensional units. When the dimensional unit may vary for a given field, the user shall be informed and a separate field with options shall be provided to the right of the numeric field for the entry of units from a drop down list. | Compliant |
| 5.17.6.22 | User omissions. The user shall be informed when required data entries have not been entered. | Compliant |
| 5.17.6.23 | Non-entry areas. Non-entry (protected) areas of the display shall be displayed in a way that makes them distinguishable from areas where data may be entered. | Compliant |
| 5.17.6.24 | Inaccessible by cursor. Non-entry areas shall be inaccessible via the cursor. | Not Applicable |
| 5.17.6.25 | Flexible data entry. When multiple data items are entered, the user shall be allowed to re-enter, change, or cancel any item before submitting. | Compliant |
| 5.17.6.26 | Logical order. Where no source document is involved, forms shall be designed so that data items are ordered in a logical sequence of input. | Compliant |
| 5.17.6.27 | Dialog boxes for control entry. Dialog boxes may be used as an aid for composing complex control entries or for selecting options. For example, for a print request, a displayed form might help a user invoke the various format controls that are available. | Compliant |
| 5.17.7 | Notifications, messaging, and dialogs. | |
| 5.17.7.1 | Information presentation using speech output. Where possible, speech outputs should be used in applications that are expected to be used in conjunction with another activity that requires focused visual attention or hands-free response. | Not Applicable |
| 5.17.7.1.1 | Speech output design. Design of speech displays shall conform to the criteria in 5.3.10. | Not Applicable |
| 5.17.7.1.2 | Hands-free. The device shall have a hands-free method of activation and deactivation. | Not Applicable |
| 5.17.7.1.3 | Use. Speech recognition should be used when: a. The consequences of recognition errors are low. b. Identifying and correcting errors would be easy. c. Use is expected to be infrequent. d. The device has an alternative method of input so that speech recognition can be turned off when it is not desired. | Not Applicable |
| 5.17.7.2 | Communication methods. | |
| 5.17.7.2.1 | Common method use. Visual displays of communication (e.g., chat) shall be provided under the following conditions: a. The message is very complex, long, or may need to be referred to at a later time. b. When the message does not necessarily call for immediate action (e.g., can be addressed after receiver has finished current task). c. When the auditory system of the receiver is overburdened. d. When the environment is too noisy to ensure reliable receipt of an aural message. e. When the receiver will remain in a position where they can continue to watch the visual displays. f. When joint communication is required (particularly with non-native English speakers). | Non-Compliant |
| 5.17.7.2.2 | Multimodal communication. Visual displays of communication (e.g., chat) shall not be the only means of real-time communication of critical information if high workload situations are to be expected. See 5.3.1 for situations in which auditory information should be provided to the user. | Non-Compliant |
| 5.17.7.2.3 | Notifications. Audio notifications should be programmable and available for instances such as arrival of new message, message from certain individuals, and messages that contain certain key words. | Non-Compliant |
| 5.17.7.2.4 | Chat. | Not Applicable |
| 5.17.7.2.4.1 | Saving text. Message text should automatically be saved for long-term storage. Additionally, a mechanism for short-term saving of text should be implemented for use during a session. | Not Applicable |
| 5.17.7.2.4.2 | Receipt after viewing. A confirmation that the communicated message has been seen should be sent to the sender during real-time, two-way discussions. | Not Applicable |
| 5.17.7.2.4.3 | Promoting typing efficiency. Features such a voice-to-text, auto-fill, hotkeys, and pre-formatted messages should be used to increase chat efficiency by reducing typing time. | Non-Compliant |
| 5.17.7.2.4.4 | Text-to-speech. The contents of the message should be able to be read via a text-to-speech system if the user is not able to view the window. | Not Applicable |
| 5.17.7.2.4.5 | Chat integration. Chat windows should be integrated into primary displays that require attention to help keep user focus on the displays. | Not Applicable |
| 5.17.7.2.4.6 | Standardized lexicon. A standardized lexicon should be provided to ensure that information in the message can be understood across staffs. | Not Applicable |
| 5.17.7.2.5 | Audio displays. Audio displays may be used as part of the information presentation, where: a. The common mode of visual display is restricted by overburdening or user mobility needs and it is desirable to cue, alert, or warn the user. b. The user will be provided feedback after control actuation, data entry, or completion of timing cycles and sequences. | Not Applicable |
| 5.17.7.2.6 | Supportive function. Audio signals used in conjunction with visual displays shall be supplementary to the visual signals. | Not Applicable |
| 5.17.7.2.7 | Direct user. Audio signals shall be used to alert users to the appropriate visual display. | Not Applicable |
| 5.17.7.2.8 | Signal characteristics. Signals may be one-time or intermittent. | Not Applicable |
| 5.17.7.2.9 | Intermittent signals. Intermittent signals shall be automatically terminated when no longer applicable or terminated by user control. For more information on signal characteristics, see 5.3.4. | Not Applicable |
| 5.17.7.2.10 | Alarm settings. Alarm settings shall be in accordance with the criteria in 5.17.7.2.10.1 and 5.17.7.2.10.2. | Non-Compliant |
| 5.17.7.2.10.1 | Customized settings. When alarm settings are user-customized, users shall be permitted to view status information regarding current settings established as critical. | Compliant |
| 5.17.7.2.10.2 | Alarm status. Alarm status information shall be provided where responsibility may be shifted from one user to another (e.g., as in changes of shift). | Compliant |
| 5.17.8 | Windows and window interactions. | |
| 5.17.8.1 | Information from diverse sources. Web portals shall bring information together from diverse sources in a single location. | Compliant |
| 5.17.8.2 | Dedicated area. Each information source shall get its own dedicated area on the page for displaying information in a portlet. | Compliant |
| 5.17.8.2.1 | Title. The title of a portlet should be a short descriptive phrase that clearly indicates the subject of the portlet (see figure 95). | Compliant |
| 5.17.8.2.1.1 | Multiple screens. If the portlet presents multiple screens of content, a name that indicates the particular screen should be included with the portlet title or appear as a heading in the content area of the portlet. | Compliant |
| 5.17.8.2.1.2 | Screen name part of title. When a screen name is part of the title, the format should include the portlet name followed by the screen name using the format “Portlet Name – Screen Name”. | Not Applicable |
| 5.17.8.2.1.3 | Screen name as part of portlet title. When a screen name is included in the portlet title, it should not be duplicated as a heading in the content area of the portlet. | Not Applicable |
| 5.17.8.2.2 | Title bar. The title bar of a portlet shall include action buttons (i.e., decorations) that allow the users to perform the following functions: a. Detach – Allows the user to open the portlet in a separate browser window. b. Edit – Allows the user to open a page for changing the appearance or content of the portlet. c. Help – Allows the user to open a page with information about how to use the portlet and its functions. d. Maximize – Allows the user to maximize the portlet to the full size of the browser window. e. Open and close – Allows the user to toggle the portlet between displaying the full page and displaying the title bar only. f. Properties – Allows the user to open a page with information about the portlet (e.g., version, author). g. Refresh – Allows the user to update the contents of the portlet when the content may change over time. h. Remove – Allows the user to remove the portlet from a page. i. Restore down – Allows the user to return a maximized portlet to its original size. | Non-Compliant |
| 5.17.8.3 | Action buttons. Portlet action buttons shall be presented in the same order in each portlet in a portal. | Compliant |
| 5.17.8.4 | Number of portlets. A page should not contain more than seven portlets. | Compliant |
| 5.17.8.5 | Vertical height. The portlets should fit within three or fewer screens in vertical height in order to minimize the amount of scrolling required to view them. | Non-Compliant |
| 5.17.8.6 | Support for multiple tasks. A portlet that supports tasks within a page should be available in multiple pages in which users might be required to support those same tasks. | Not Applicable |
| 5.17.8.7 | Portlets for specific roles. The portlets that are common to specific roles should be access-controlled via privilege levels. For users who do not have permission to see certain portlets or groups of tasks associated with a particular role, the tab or other control that provides access to that content should be hidden and unavailable for retrieval by users lacking the relevant permissions. | Compliant |
| 5.17.8.8 | Fixed-width portlets. A portlet may be a fixed-width, or it may adjust to fit the width of the column where it is placed. A fixed-width portlet should be used in layouts with fixed-width columns. A variable-width portlet may be used in layouts with either fixed- or variable-width columns and self-adjust to fit the fixed width when used in a fixed-width portlet. | Compliant |
| 5.17.8.9 | Variable-width portlets. Variable-width portlets shall display all content correctly regardless of portlet size. | Compliant |
| 5.17.8.10 | Access control. Portals should support public key infrastructure (PKI)-based access so users can log in once and automatically be authenticated to all components and applications to which they have access. | Not Applicable |
| 5.17.8.11 | Public pages. A portal shall include a public page that users can access prior to logging on to the portal. | Not Applicable |
| 5.17.8.12 | Public page content. The public page should provide organizational information (e.g., mission overview, points of contact), information about how to register for a certificate or obtain an account, and either a means for direct log-in or a link to the log-in screen for the portal. | Not Applicable |
| 5.17.8.13 | Personalization. Users should be allowed to make changes to unrestricted portal pages or to add or delete default and customize pages when permitted by the portal owner. | Compliant |
| 5.17.8.14 | Content areas. Those content areas, which can be changed, shall be predefined and selectable. | Compliant |
| 5.17.9 | User guidance. | |
| 5.17.9.1 | Feedback. Feedback that presents status information, confirmation, and verification of input throughout system interactions shall be provided. | Compliant |
| 5.17.9.2 | System status. System status information regarding operational modes and availability shall be accessible to users, either automatically or by request as needed. | Compliant |
| 5.17.9.3 | Computer responses. Every input by a user shall produce a consistent perceptible response output from the computer. | Compliant |
| 5.17.9.4 | Alternative form. If the feedback is not presented visually, an alternative form of feedback (e.g., sound) shall be provided. | Non-Compliant |
| 5.17.9.5 | System response time. Maximum system response times for critical systems (e.g., fire control systems, command and control systems) shall not exceed the values provided in table V. | Not Applicable |
| 5.17.9.5.1 | Non-critical systems. Non-critical systems may permit relaxed response times. | Not Applicable |
| 5.17.9.5.2 | Existing or predecessor systems. System response times for critical and non-critical systems shall not exceed the response time of equivalent existing or predecessor systems. | Not Applicable |
| 5.17.9.5.3 | System processing indication. When computer response times will exceed 1 second, the system shall provide a message indicating that the system is processing. For remotely handled automated systems, see 5.12. | Compliant |
| 5.17.9.6 | Task performance time. The time required to accurately complete a standard time-sensitive action or sequence of actions (including system response times) shall not exceed the time to complete the same action(s) on equivalent existing or predecessor systems. | Not Applicable |
| 5.17.9.7 | Time-consuming processes. The system shall provide warning information when a command is invoked that will be time-consuming or resource-intensive to process. | Not Applicable |
| 5.17.9.8 | Aborting time-consuming processes. The system shall provide users an option to abort time-consuming processes. | Compliant |
| 5.17.9.9 | System processing. When system processing requires a user to wait before taking further action, an appropriate message or icon shall be displayed until user interaction is again possible. | Compliant |
| 5.17.9.9.1 | Status message. Where the delay is expected to exceed 1 second, the system shall provide a status message. | Compliant |
| 5.17.9.9.2 | Progress indicator. For delays exceeding 10 seconds, the display shall provide a progress indicator. | Compliant |
| 5.17.9.10 | User input rejection. If the system rejects a user input, feedback shall be provided to indicate the reason for rejection and the required corrective action. | Compliant |
| 5.17.9.11 | Highlighted option selection. Any items as an option or input to the system shall be highlighted to indicate acknowledgment by the system. | Compliant |
| 5.17.9.12 | Process outcome. When a control process or sequence of related actions is either completed or aborted by the system, the system shall provide an indication of the outcome to the user. | Compliant |
| 5.17.9.13 | Subsequent actions. Following an aborted action, the system shall provide any requirements for subsequent user action. | Compliant |
| 5.17.9.14 | Feedback message content. Feedback messages shall be explicit and informative. | Compliant |
| 5.17.9.14.1 | Understandable. Feedback shall not require a reference system or codebook to be understood. | Compliant |
| 5.17.9.14.2 | Non-standard abbreviations. Non-standard abbreviations should be avoided in feedback messages. | Non-Compliant |
| 5.17.10 | Error management. | |
| 5.17.10.1 | Error correction. An easy means for correcting erroneous user entries shall be provided. | Compliant |
| 5.17.10.2 | Partial correction. The system shall permit partial correction of entries. | Compliant |
| 5.17.10.3 | Early detection. A capability to detect and correct errors after keying in but before entering into the system shall be provided. | Compliant |
| 5.17.10.4 | Logical data breaks. Error checking shall occur at logical data entry breaks, such as at the end of data fields rather than characters to minimize disruption. | Compliant |
| 5.17.10.5 | Internal software checks. Software shall provide checks of user entries for validity of item, sequence of entry, completeness of entry, and range of values. | Compliant |
| 5.17.10.6 | Critical entries. The system shall require the user to acknowledge entries that have irreversible or potentially destructive consequences prior to their being implemented by the system. | Compliant |
| 5.17.10.7 | Error message content. | |
| 5.17.10.7.1 | Describe error. Error messages shall describe the error simply and provide diagnostic information in terms of the application rather than system function (e.g., “too many characters” vs. “stack overflow”). | Compliant |
| 5.17.10.7.2 | Instruct user. Error messages shall instruct the user how to recover from the error or escape from the error situation. | Compliant |
| 5.17.10.7.3 | Constructive and neutral tone. Error messages shall be constructive and neutral in tone, avoiding phrases that suggest a judgment of the user’s behavior. | Compliant |
| 5.17.10.7.4 | Consistent with user understanding. The error message shall be written in a manner consistent with the user’s understanding and expected level of knowledge of the system. | Compliant |
| 5.17.10.7.5 | Correction entry and confirmation. When the user enters correction of an error, such corrections shall be implemented by an explicit action by the user (e.g., actuation of an ENTER key). | Non-Compliant |
| 5.17.10.7.6 | Error correction acknowledgement. The system shall acknowledge all error corrections by the user either by accepting the corrected entry or by providing a separate error message for an erroneous entry. | Compliant |
| 5.17.10.7.7 | Errors in elements not normally visible. References to errors in elements of the system not normally visible to users shall not be included unless the user has explicitly requested detailed diagnostic information for programmer-level troubleshooting. | Not Applicable |
| 5.17.10.8 | Error description. If a simple error message is presented, users shall be provided access to a more detailed description of the error. | Compliant |
| 5.17.10.9 | Message timing. Error messages shall be provided within 0.2 second of the time in which an error is detected. | Compliant |
| 5.17.10.10 | Error recovery and process change (multi-level “undo”). The user shall be able to stop a control process at any point in a sequence and easily return to previous levels in multi-step processes in order to nullify an error or effect a desired change. | Not Applicable |
| 5.17.10.11 | Spelling errors. Spelling and other common errors shall not produce valid system commands or initiate transactions. | Not Applicable |
| 5.17.10.12 | Recognize common misspellings. The system shall recognize common misspellings of commands and inform users of unrecognized entries, provide a similar correct entry, and display the recommendation for revision and confirmation by the user. | Not Applicable |
| 5.17.10.13 | Errors in stacked commands. To prompt for corrections of an error in stacked commands, the system shall display the stacked command sequence with the error(s) highlighted. Where possible, a procedure shall be provided to correct the error and salvage the stack. | Non-Compliant |
| 5.17.10.13.1 | Error correction procedure. When possible, a procedure shall be provided to correct the error and salvage the stack. | Not Applicable |
| 5.17.10.13.2 | Partial execution. If the error was not detected until after some of the commands in the stack have executed, the system shall provide a message to inform the user which commands were successfully executed. | Compliant |
| 5.17.10.14 | Display of erroneous entries. An error message shall be displayed continuously until either the error is corrected or the user dismisses the error message. | Compliant |
| 5.17.10.15 | Automatic error correction. Automatic correction of user errors by the system should be provided if: a. The error being corrected has a unique solution. b. The correction of the error is apparent to the user. c. The automatic correction functionality can be disabled upon user request. | Not Applicable |
| 5.17.10.16 | Location of error messages. Error messages shall appear as near as possible to the user entry that caused the message but not obscure any control or display area the user requires to perform the task. | Compliant |
| 5.17.10.17 | Obscure information. If an error message obscures task-relevant information, a means for the user to move the message shall be provided. | Non-Compliant |
| 5.17.10.18 | Multiple error messages. If a user repeats an entry error, the second error message shall be revised to include a noticeable change so that the user may be certain that the computer has processed the attempted correction. | Non-Compliant |
| 5.17.11 | Simultaneous access. | |
| 5.17.11.1 | Two or more users. When two or more users must have simultaneous read access to a computer program or data processing results from separate interfaces, operations by one person shall not interfere with the operations of another person unless mission survival may be contingent upon preemption. | Not Applicable |
| 5.17.11.2 | Preemption. If preemption occurs, provisions shall be made so that the preempted user can resume operations at the point of preemption without information loss. | Not Applicable |
| 5.17.12 | Help. In addition to the requirements provided herein, detailed guidance and best practices may be found in ANSI\HFES 200.3. | |
| 5.17.12.1 | Access. The system shall provide built-in guidance by allowing users to easily access built-in technical help. | Compliant |
| 5.17.12.2 | Explicit error management aids. Help shall be available through explicit error management aids (labels, prompts, advisory messages) and implicit aids (cueing). | Compliant |
| 5.17.12.3 | Standard action to request help. A simple standard action shall always be available for the user to access help. | Compliant |
| 5.17.12.4 | Built-in help. At a minimum, built-in help shall include definitions of allowable options, system capabilities, procedures, and ranges of values. | Compliant |
| 5.17.12.5 | Context sensitive help. Context-sensitive help shall be specific to the context from which it was accessed. After initial access, the system shall provide the user the ability to query the help documentation. | Compliant |
| 5.17.12.6 | Minimize cross-referencing. Individual built-in help displays should contain enough information to respond to a user’s query even if this capability produces redundancy in the built-in help system as a whole. | Compliant |
| 5.17.12.7 | Definitions. The help section should contain a list of abbreviations and acronyms that are used in the main application. | Not Applicable |
| 5.17.12.8 | Multilevel help. If an initial Help display provides only summary information, more detailed explanations shall be available via user query or drill-down. | Compliant |
| 5.17.12.9 | Consistent help terminology. Online documentation, offline documentation, and help instructions shall use identical terminology to describe or define identical concepts or processes. | Compliant |
| 5.17.12.10 | System-initiated help. For systems expected to have novice or infrequent users, a system-initiated Help function may be used. When provided, such functionality shall have the following characteristics. | Compliant |
| 5.17.12.10.1 | Specific. System-initiated help shall only provide help specific to the user’s current task or context. | Compliant |
| 5.17.12.10.2 | Non-intrusive. System-initiated help shall not interfere with or obscure any control or display area the user requires to perform the current task. | Compliant |
| 5.17.12.10.3 | Easy to enable and disable. A relatively novice user shall be able to disable and enable system-initiated help functionality with minimal effort. | Compliant |
| 5.17.13 | Prompts. Prompts shall be in accordance with the criteria in 5.17.13.1 through 5.17.13.10. | |
| 5.17.13.1 | Use. Prompts and help instructions shall be used to explain commands, error messages, system capabilities, display formats, procedures, and sequences as well as to provide data. | Compliant |
| 5.17.13.2 | Prompts for special modes. When operating in special modes, the system shall display the mode designation and file(s) being processed. | Compliant |
| 5.17.13.3 | User confirmation. Before processing any user requests that would result in extensive or final changes to existing data, the system shall require user confirmation. | Compliant |
| 5.17.13.4 | Confirm abort operations. When data entries or changes will be nullified by an abort action, the system shall require user confirmation. | Compliant |
| 5.17.13.5 | Prompt for missing data. When missing data are detected, the system shall prompt the user to supply the missing data. | Compliant |
| 5.17.13.6 | Standard display. Prompting messages shall be displayed in a standardized area of the displays. | Compliant |
| 5.17.13.7 | Explicit prompts. Prompts and help instructions for system-controlled dialog shall be explicit. | Compliant |
| 5.17.13.8 | Memorization. Prompts shall be presented in such a way that the user is not required to memorize lengthy sequences or refer to secondary written procedural references in order to respond. | Compliant |
| 5.17.13.9 | Prompt clarity. Prompts shall be clear and understandable. | Compliant |
| 5.17.13.10 | Coding schemes. Prompts shall not require reference to coding schemes or conventions that may be unfamiliar to occasional users. | Compliant |
| 5.17.14 | Information content. | |
| 5.17.14.1 | Amount of information. The amount of information required shall be in accordance with the criteria in 5.17.14.1.1 through 5.17.14.1.5. | Compliant |
| 5.17.14.1.1 | Scope. Information displayed to a user shall be clear enough to allow the user to perform the intended mission. | Compliant |
| 5.17.14.1.2 | Precision. Information displayed shall be limited to the precision required to perform specific actions or to make decisions. | Compliant |
| 5.17.14.1.3 | Context for displayed data. Each data display shall provide contextual information, including data from prior displays as necessary. | Compliant |
| 5.17.14.1.4 | Combining operator and maintainer information. Operator and maintainer information shall not be combined in a single display unless the information content, format, and timeliness support the needs of both users. | Compliant |
| 5.17.14.1.5 | Information density. Critical information shall be separate and distinct enough to be salient from non-critical information. | Compliant |
| 5.17.14.2 | Presentation of information. Information shall be presented in accordance with the criteria in 5.17.14.2.1 through 5.17.14.2.7. | Not Applicable |
| 5.17.14.2.1 | Plain text. Information shall be displayed in language appropriate to the user’s level of training and be as specific as possible to the user’s particular application. | Non-Compliant |
| 5.17.14.2.2 | Abbreviations. Abbreviations should be in accordance with JSSG-2010. | Not Applicable |
| 5.17.14.2.3 | New abbreviations. New abbreviations, if required, shall be developed using logical rules. | Not Applicable |
| 5.17.14.2.4 | Distinctive. Abbreviations shall be distinctive to avoid confusion. | Not Applicable |
| 5.17.14.2.5 | Consistent. Words shall have only one consistent abbreviation. | Not Applicable |
| 5.17.14.2.6 | Punctuation. No punctuation shall be used in abbreviations. | Not Applicable |
| 5.17.14.2.7 | Definitions. Definitions of all abbreviations, mnemonics, and codes shall be available to access within the system. | Compliant |
| 5.17.14.3 | Quantitative information. Quantitative information shall be displayed in accordance with the following rules. | Not Applicable |
| 5.17.14.3.1 | Numeric digital displays. Digital displays shall be used when the task requires identifying a specific numeric quantity. | Compliant |
| 5.17.14.3.2 | Pattern display. Analog or graphic displays shall be used when the comparison of quantities is important. | Compliant |
| 5.17.14.3.3 | Comparison of quantities. Numeric digital displays shall not be used as the only display of information when the comparison of quantities is important for accurate interpretation. | Compliant |
| 5.17.14.3.4 | Hybrid displays. Hybrid displays, which combine both digital and analog or graphic displays, shall be provided when a task requires both identification of a specific numeric quantity and the ability to compare quantities. | Compliant |
| 5.17.14.3.5 | Units. Displays of quantitative information shall include units of measure. | Compliant |
| 5.17.15 | Format. | |
| 5.17.15.1 | Critical data. Critical data shall not be obscured by pagination or scrolling. | Compliant |
| 5.17.15.2 | Readily usable form. Information shall be presented to the user in a directly usable form that does not require the user to transpose, compute, interpolate, or mentally translate the information into other units, number bases, or languages. | Compliant |
| 5.17.15.3 | Format consistency. | |
| 5.17.15.3.1 | Display output consistency. The content of displays and their formats shall be consistent within a system and across systems that are used by the same users. | Compliant |
| 5.17.15.3.2 | Consistency between output and input. The same format shall be used for inputting data and displaying the output within a task (e.g., a date entered in the form of “mm/dd/yyyy” will be outputted in the same form). | Compliant |
| 5.17.15.3.3 | Recurring data field labels. Recurring data fields within a system and across systems used by the same users shall have consistent labels. | Compliant |
| 5.17.15.3.4 | Comparative data fields. Data fields to be compared on a character-by-character basis shall be positioned one above the other with alignment of characters to be compared. | Compliant |
| 5.17.15.3.5 | Position of recurring data fields. Recurring data fields within a system and across systems used by the same users shall occupy consistent relative positions across displays. | Compliant |
| 5.17.15.3.6 | Consistency of data entry formats. Whenever data has to be entered by hand, order and format should be as consistent as possible. | Compliant |
| 5.17.15.4 | Critical messages in dialog boxes. Messages that are critical or that require user acknowledgment (e.g., error messages) shall appear in their own dialog boxes. | Compliant |
| 5.17.15.5 | Page numbering. Each page of a multiple-page display should be labeled to identify the currently displayed page and the total number of pages, if applicable (e.g., “Page 2 of 5”). | Compliant |
| 5.17.15.6 | Display titles and headers. Each display shall be labeled with a title or header. | Compliant |
| 5.17.15.6.1 | Unique. The title or header shall be unique within the system. | Compliant |
| 5.17.15.6.2 | Position. The title or header should be positioned at the top left corner or centered on the page. | Compliant |
| 5.17.15.6.3 | Content. The title or header shall briefly describe the contents or purpose of the page. | Compliant |
| 5.17.15.6.4 | Meaningful. The title or header shall be meaningful enough to be learned and remembered easily. | Compliant |
| 5.17.15.7 | Use of frames. Frames shall border the window. | Not Applicable |
| 5.17.15.7.1 | Position. Frame identification shall be prominently displayed in the top left corner of the frame. | Not Applicable |
| 5.17.15.7.2 | Size. Frame identification shall not exceed the size of the frame when resized to its minimum size. | Not Applicable |
| 5.17.15.7.3 | Meaningful. Frame identification shall be meaningful enough to be learned and remembered easily. | Not Applicable |
| 5.17.15.7.4 | Content. Frame identification shall describe the content within that frame. | Not Applicable |
| 5.17.15.7.5 | Separation. At least one blank line shall separate the frame identification and the body of the frame. | Not Applicable |
| 5.17.15.8 | Grouping of multiple displays. | |
| 5.17.15.8.1 | Grouping. All displays necessary to support a user activity or sequence of activities shall be grouped together. | Compliant |
| 5.17.15.8.2 | Frequency of use. Displays used most frequently shall be grouped together and placed in the optimum visual zone. | Compliant |
| 5.17.15.8.3 | Importance. Important or critical displays shall be located in the optimum projected visual zone or otherwise highlighted. | Compliant |
| 5.17.15.8.4 | Function and sequence. Displays shall be arranged in relation to one another according to their sequence of use or the functional relations of the components they represent such that order in functional groups provide a viewing flow from left-to-right or top-to-bottom. This requirement does not apply to master warning, caution, or advisory indicators. | Compliant |
| 5.17.15.8.5 | Consistency. The arrangement of displays within a system shall be consistent in principle from one application to another. | Compliant |
| 5.17.16 | Use with individual protective equipment. Where users may be required to use visual displays while wearing CBRNE or other mission-required PPE gear, displays shall be designed for foveal vision under relatively high levels of illumination; displays in the peripheral field of view shall only be used to attract attention. | Not Applicable |
| 5.17.17 | Grouping within a display. Information or data shall be ordered in accordance with a specific purpose or context. When the purpose or context does not suggest a method of grouping information or data on a display, they may be grouped according to the following guidelines listed in order of preference. | Compliant |
| 5.17.17.1 | Order and sequences. When data fields have a naturally occurring order, such as chronological or sequential, such order should be reflected in the format organization of the fields. | Compliant |
| 5.17.17.2 | Grouped by importance. Displayed data items that are critical or require immediate user response may be ordered at the top of the list. | Compliant |
| 5.17.17.3 | Ordered by function. Sets of data that are associated with specific questions or related to particular functions may be ordered together to signify those functional relationships. | Compliant |
| 5.17.17.4 | Ordered by frequency. Data items used more frequently than others may be ordered at the top of the list. | Compliant |
| 5.17.18 | Text and alphanumeric presentation. | |
| 5.17.18.1 | Aircrew station signals. Aircrew station signals shall be designed using the guidance of JSSG-2010. | Not Applicable |
| 5.17.18.2 | Alphanumeric character and symbol sizes. When measured from the greatest anticipated viewing distance, the height of alphanumeric characters and pictorial symbols shall subtend not less than 2.9 milliradians (10 minutes) of visual angle and should subtend not less than 4.5 milliradians (15 minutes) of visual angle. | Not Applicable |
| 5.17.18.3 | Alphanumeric character and symbol sizes for viewing from ejection seats. Aircraft display characters and symbols that must be read in flight shall subtend not less than 7 milliradians (24 minutes) of visual angle. | Not Applicable |
| 5.17.18.4 | Character stroke width. Assuming that the character height conforms to 5.17.18.2, stroke width shall be not less than 0.0834 nor greater than 0.1667 of the number of pixels used for character height. | Not Applicable |
| 5.17.18.5 | Character width. Character width shall be approximately 0.9 of the height. | Not Applicable |
| 5.17.18.6 | Symbol size and image quality for complex shapes. The size of a symbol or graphic shall be such that all text or graphics embedded within the symbol (e.g., label within symbol) shall subtend not less than 2.9 milliradians (10 minutes) of visual angle from the greatest anticipated viewing distance. | Not Applicable |
| 5.17.18.7 | Font characteristics. Font style shall enable discrimination of similar characters (e.g., letter l/number 1, letter Z/number 2). | Compliant |
| 5.17.18.7.1 | Standard font. A common standard font shall be used (e.g., Arial, Times New Roman, Courier, Verdana). | Compliant |
| 5.17.18.7.2 | Sans-serif. Where users must read under adverse conditions (e.g., poor lighting), a sans-serif style shall be used (e.g., Arial, Verdana, Helvetica). | Compliant |
| 5.17.18.8 | Protective gear. Display characteristics (e.g., legibility) shall be compatible with viewing while wearing a CBRNE or other mission-required PPE protective mask. | Not Applicable |
| 5.17.18.9 | Viewing with PPE. Symbols viewed while wearing a CBRNE or other mission-required PPE mask shall subtend not less than 5.8 milliradians (20 minutes) of visual angle. | Not Applicable |
| 5.17.18.10 | Alphanumerics. | |
| 5.17.18.10.1 | Alphanumeric organization. When five or more alphanumeric characters are presented, they shall be separated into groups per their natural organization and punctuation schemes (e.g., “mm/dd/yyyy”, “(123) 555-6789”, and “123-45-6789”). | Compliant |
| 5.17.18.10.2 | Combination of letters and digits. When a code consists of both letters and digits, common character types shall be grouped together. | Not Applicable |
| 5.17.18.10.3 | Blocking. When five or more alphanumeric characters without natural organization are displayed, characters shall be grouped in blocks of three to five characters. | Non-Compliant |
| 5.17.18.10.4 | Separation of groups. When five or more alphanumeric characters without natural organization are displayed, groups of characters and digits shall be separated from one another by a minimum of one blank space. | Non-Compliant |
| 5.17.18.10.5 | Long numeric fields. When five or more numeric characters without natural organization are displayed, long numeric fields shall be punctuated with commas, spaces, or slashes. | Compliant |
| 5.17.18.10.6 | Leading zeros. Leading zeros shall not be used in numerical data. | Not Applicable |
| 5.17.19 | Text and program editing. Text and program editing shall be in accordance with the criteria in 5.17.19.1 through 5.17.19.12. | |
| 5.17.19.1 | Buffer. When appropriate, when inserting characters, words, or phrases (e.g., editing), items to be inserted shall be collected in a buffer area and displayed in the prescribed insert area of the screen for subsequent insertion by user command. | Compliant |
| 5.17.19.2 | Edit commands. Edit commands, such as MOVE, COPY, PASTE, INSERT and DELETE, for adding, inserting, or deleting text and program segments shall be provided. | Not Applicable |
| 5.17.19.2.1 | Text edit commands. In text editing, editing commands shall be based on character, word, sentence, paragraph, and higher-order segments. | Not Applicable |
| 5.17.19.2.2 | Program edit commands. In program editing, the special commands shall be based on lines or subprograms. | Not Applicable |
| 5.17.19.2.3 | Program lines. Program lines shall reflect a numbering scheme for ease in editing and error correction. | Not Applicable |
| 5.17.19.2.4 | Syntax checking. Line-by-line syntax checking shall be under user control. | Not Applicable |
| 5.17.19.2.5 | Tab controls. For editing programs or tabular data, cursor tab controls or other provisions for establishing and moving readily from field to field shall be provided. | Compliant |
| 5.17.19.2.6 | Keying edit commands. Where editing commands are made by keying into the display, the editing commands shall be readily distinguishable from the displayed textual material. | Not Applicable |
| 5.17.19.3 | Highlighted text. Where text has been specified to become the subject of control entries (e.g., for underlining, bolding, moving, copying, or deleting), the affected segment of text shall be highlighted to indicate its boundaries. | Compliant |
| 5.17.19.4 | String search. A string search capability shall be provided to allow the user to specify a string of text (words, phrases, or numbers) and request the computer to advance (or back up) the cursor automatically to the next (or previous) occurrence of that string. | Compliant |
| 5.17.19.5 | String search variance. The string search capability shall provide the flexibility to select search variance. | Not Applicable |
| 5.17.19.6 | Automatic word wrap. An automatic word wrap (carriage return) shall be provided when the text reaches the right margin for entry or editing of unformatted text. | Compliant |
| 5.17.19.7 | Override of word wrap. User override of automatic word wrap shall be provided. | Not Applicable |
| 5.17.19.8 | Format control. A means shall be provided for users to specify required format control features during text entry or editing (e.g., margins, tab settings, line spacing). | Not Applicable |
| 5.17.19.9 | Predefined formats. When text formats must follow predefined standards, the required format shall be provided automatically. | Compliant |
| 5.17.19.10 | Text formats as a user option. Where text formats are a user option, a convenient means shall be provided to allow the user to specify and store the formats that have been generated for particular applications for future use. | Not Applicable |
| 5.17.19.11 | Frequently used text. The capability to label and store frequently used text segments (e.g., signature blocks, organizational names, call signs, coordinates), and to later recall (copy into current text) stored segments identified by their assigned labels shall be provided. | Not Applicable |
| 5.17.19.12 | Head and foot of file. The means shall be provided to readily move the cursor to the head (beginning) or the foot (end) of the file. | Not Applicable |
| 5.17.20 | Organization of information. | |
| 5.17.20.1 | Labels. Every element on a display shall be labeled unless its purpose is intuitively obvious to the intended user population | Compliant |
| 5.17.20.1.1 | Use. User-requested element identification (e.g., tool tips) is acceptable where space constraints preclude the use of labels. | Non-Compliant |
| 5.17.20.1.2 | Label characteristics. Labels should adhere to the following requirements: | |
| 5.17.20.2 | Default values. Default values shall meet the following requirements. | |
| 5.17.20.2.1 | Use when feasible. To reduce user workload, default values shall be used where feasible. | Compliant |
| 5.17.20.2.2 | Display automatically. Currently defined default values shall be displayed automatically in their appropriate data fields with the initiation of a data entry transaction. | Compliant |
| 5.17.20.2.3 | Acceptance. The user shall be able to indicate acceptance of the default by a single keystroke. | Compliant |
| 5.17.20.2.4 | Replace default value. The user shall be able to replace any default value during a given transaction without changing the default definition. | Compliant |
| 5.17.20.2.5 | Generate default values. The user shall have the option of generating default values if the system has not provided them. | Not Applicable |
| 5.17.20.2.6 | Default options. Where a series of default values has been defined for a data entry sequence, the user shall be able to accept those default entries. | Not Applicable |
| 5.17.20.3 | Tabular data. Tabular data shall meet the following requirements. | |
| 5.17.20.3.1 | Use. Tabular data displays shall be used to present row-column data to aid detailed comparison of ordered sets of data. | Compliant |
| 5.17.20.3.2 | Standard formats. Location of recurring data shall be consistent among all tabular data displayed and common throughout the system. | Compliant |
| 5.17.20.3.3 | Arrangement. When tabular data are sorted within rows, it should be in increasing order from left to right. Tabular data sorted within columns should be in an order dictated by context. | Non-Compliant |
| 5.17.20.3.4 | Titles. When tabular data are divided into classifications, the classification titles shall be displayed. | Compliant |
| 5.17.20.3.5 | Vertical extension – titles. When tabular data extend over more than one page vertically, the columns shall be titled identically on each page. | Compliant |
| 5.17.20.3.6 | Horizontal extension. Tabular displays should not extend over more than one page horizontally. | Compliant |
| 5.17.20.3.7 | Horizontal extension – titles. If horizontal extension over more than one page is required, the rows shall be titled identically on each page. | Compliant |
| 5.17.20.3.8 | Distinctive and informative labels. Rows and columns shall be labeled distinctively to guide data entry. | Compliant |
| 5.17.20.3.9 | Layout of numeric entry. Users shall be allowed to make numeric entries in tables without concern for justification. The computer shall right-justify integers or justify with respect to a decimal point if present. | Not Applicable |
| 5.17.20.3.10 | Labeling units of measurement. The units of displayed data shall be consistently included in the displayed column and row labels. | Compliant |
| 5.17.20.3.11 | Consistent column spacing. The widths of columns containing the same data elements shall be uniform and consistent within a table and from one table to another. | Compliant |
| 5.17.20.3.12 | Consistent row spacing. The heights of rows containing the same data elements shall be uniform and consistent within a table and from one table to another. | Compliant |
| 5.17.20.3.13 | Column scanning cues. A column separation not less than three spaces shall be maintained. | Compliant |
| 5.17.20.3.14 | Row scanning cues. A group of rows shall be separated at regular intervals of not more than every five lines. | Compliant |
| 5.17.20.4 | Lists. | |
| 5.17.20.4.1 | List arrangement. Items in lists shall be arranged in a recognizable order, such as chronological, alphabetical, sequential, functional, or importance. | Compliant |
| 5.17.20.4.2 | List lines. Each item in a list shall start on a new line. | Non-Compliant |
| 5.17.20.4.3 | Vertical extension. Where lists extend over more than one display page, the last line of one page shall be the first line on the succeeding page. | Not Applicable |
| 5.17.20.4.4 | Marking multi-line items in a list. Where a single item in a list continues for more than one line, such items shall be marked in some way (e.g., blank line, indentation) so that the continuation of the item is obvious. | Non-Compliant |
| 5.17.20.4.5 | Vertical ordering in multiple columns. Where items in a list are displayed in multiple columns, items shall be ordered vertically within each column. | Compliant |
| 5.17.20.4.6 | Arabic numerals. When listed items will be numbered, Arabic numerals shall be used rather than Roman numerals. | Non-Compliant |
| 5.17.20.4.7 | Hierarchic structure for long lists. Where lists are long and must extend beyond a single displayed page, a hierarchic structure shall be used to permit the logical partitioning into related shorter lists. | Compliant |
| 5.17.21 | Graphic and representational displays. | |
| 5.17.21.1 | Graphical user interfaces. See ANSI/HFES 200 for additional graphical user interface guidance. | |
| 5.17.21.1.1 | Selecting from displayed attributes. During graphic data entry, users shall be allowed to specify attributes for displayed elements (e.g., text font, plotting symbol, line type). | Not Applicable |
| 5.17.21.1.2 | Examples. The capability to specify attributes for displayed elements should include examples that illustrate the available options. | Compliant |
| 5.17.21.1.3 | Selecting graphic elements. Users shall be provided some means for designating and selecting displayed graphic elements when manipulation of those elements is required. Normally this function is performed by a pointing device or cursor. | Compliant |
| 5.17.21.1.4 | Displaying current attributes. The attributes that will be affected by a change shall be highlighted. | Not Applicable |
| 5.17.21.1.5 | Easy storage and retrieval. The user shall be provided a means for saving and retrieving graphic data displays. | Not Applicable |
| 5.17.21.1.6 | Automatic data registration. The computer shall provide automatic registration or alignment of computer-generated graphic data so that variable data are shown properly with respect to fixed background or data map at any display scale. | Not Applicable |
| 5.17.21.1.7 | Predefined graphic formats. Where graphic data must be plotted in predefined standard formats (e.g., target areas on maps, flight plans), templates or skeletal displays shall be provided for those formats to aid data entry. | Not Applicable |
| 5.17.21.1.8 | Changing size. When editing graphic data, users shall be provided with the capability to change the size (scale) of any selected element on the display rather than delete and recreate the element in a different size. | Not Applicable |
| 5.17.21.1.9 | Highlighting critical data. When a user’s attention must be directed to a portion of a graphic display showing critical or abnormal data, that feature shall be highlighted with some distinctive means of data coding. | Compliant |
| 5.17.21.1.10 | Computer derivation of graphic data. Common or complex data computations, such as curve fitting or plotting a list of coordinates, should be performed by the system upon user request. | Compliant |
| 5.17.21.1.11 | Normal orientation for labels. The text on dynamic graphic displays shall remain upright when the displayed image rotates. | Compliant |
| 5.17.21.1.12 | Display of scale. If a map or other graphic display has zoom functionality, the current zoom level or scale shall be displayed. | Compliant |
| 5.17.21.1.13 | Display accuracy. If applicable, the current display accuracy shall be displayed. | Not Applicable |
| 5.17.21.1.14 | Interpolation. The system shall provide accurate numeric information for any point on the graphic display upon request from the user. | Compliant |
| 5.17.21.1.15 | Unobtrusive grids. Any displayed grid lines shall be unobtrusive. | Compliant |
| 5.17.21.1.16 | Obscuration of data elements. Displayed grid lines shall not obscure data elements. | Compliant |
| 5.17.21.1.17 | Grid line suppression. Users shall be provided the option to suppress or display gridlines. | Compliant |
| 5.17.21.2 | Graphs and charts. Graphs and charts shall be in accordance with the criteria in 5.17.21.2.1 through 5.17.21.2.6. | |
| 5.17.21.2.1 | Graph axes. The axes of graphs shall be labeled. | Compliant |
| 5.17.21.2.2 | Trend lines. When trend lines are to be compared, they should be displayed on a single graph. | Non-Compliant |
| 5.17.21.2.3 | Reference index. When a user must compare graphic data to some significant level or critical value, that level or value shall be included in the display. | Not Applicable |
| 5.17.21.2.4 | Data annotation. When precise reading of a graphic display may be required, the capability to supplement the graphic representation with the represented numeric values shall be provided. | Not Applicable |
| 5.17.21.2.5 | Consistent scaling. When users must compare graphic data across a series of charts, the same scale shall be used for each chart. | Not Applicable |
| 5.17.21.2.6 | Single scale only. Where graphs are presented, only a single scale shall be shown in each axis, rather than including different scales for different curves in the graph. | Not Applicable |
| 5.17.21.3 | Drawing shapes and lines. | Not Applicable |
| 5.17.21.3.1 | Drawing shapes. When shape drawing is required, users shall be provided with aids for drawing shapes. | Not Applicable |
| 5.17.21.3.2 | Drawing lines. When line drawing is required, users shall be provided with aids for drawing straight line segments. | Not Applicable |
| 5.17.21.3.3 | Drawing intersecting lines. When a user draws the end of a line segment in close proximity to a displayed element, the system should automatically connect between the line segment and displayed element. | Not Applicable |
| 5.17.21.3.4 | Override. The user shall be provided a means to override the automatic line segment connection feature. | Not Applicable |
| 5.17.21.3.5 | Drawing lines and figures with numeric coordinates. When lines or figures must be drawn to represent numeric coordinates, computer aids shall include methods for entering the coordinates and selecting the appropriate units for those coordinates. | Not Applicable |
| 5.17.22 | Specific purpose user interfaces. | |
| 5.17.22.1 | Dynamic displays. | |
| 5.17.22.1.1 | Changing values. Alphanumeric values that change in real time shall be updated according to the criteria in 5.17.22.1.1.1 through 5.17.22.1.1.2. | |
| 5.17.22.1.1.1 | Reliable reading. Values that the user must reliably read shall not be updated more often than once per second. | Not Applicable |
| 5.17.22.1.1.2 | Identify rate of change. Changing values that the user uses to identify rate of change or to read gross values shall be updated three to four times per second. | Not Applicable |
| 5.17.22.1.2 | Update rate. Update rate should be in accordance with programmatic-specific requirements. | Not Applicable |
| 5.17.22.1.2.1 | Display freeze. A display freeze mode shall be provided to allow viewing any selected frame that is updated or advanced automatically by the system. | Not Applicable |
| 5.17.22.1.2.2 | Resume from freeze. A single action option shall be provided to allow resumption at the freeze point or at the current real-time point. | Not Applicable |
| 5.17.22.1.2.3 | Display freeze prohibition. The user shall be prohibited from entering display freeze mode when doing so would have an adverse effect on the mission being performed by the system. | Not Applicable |
| 5.17.22.1.2.4 | Freeze feedback. A label shall be provided to remind the user when the display is in the freeze mode. | Not Applicable |
| 5.17.22.1.2.5 | Timeliness. Displays requiring refreshed information (e.g., head-up displays) shall be updated in a synchronous manner. | Not Applicable |
| 5.17.22.1.2.6 | Advisory and alerting. Devices displaying simultaneous and integrated information (e.g., multifunction displays) shall alert or cue operating personnel to information prior to it becoming critical within the display. | Not Applicable |
| 5.17.22.2 | Printing display. | |
| 5.17.22.2.1 | Hard copy. The system shall provide the capability for the user to obtain a paper copy of the exact contents of the alphanumeric or digital graphic display, where mass storage is restricted, mass stored data that can be lost by power interruption, or where record keeping is required or desirable. | Not Applicable |
| 5.17.22.2.2 | Display print. The system shall provide the capability for the user to print a display screen by simple request (e.g., PRINT-SCREEN). | Not Applicable |
| 5.17.22.2.3 | Print page. The system shall provide the capability for the user to request printing of a single page or sequence of pages by specifying the page numbers or printing all pages without specifying page numbers. | Not Applicable |
| 5.17.22.2.4 | Text displayed as printed. The system shall provide the capability for the user to display text as it will be printed, including underlining, boldface, subscript, superscript, special characters, special symbols, and different styles and sizes of type. | Compliant |
| 5.17.22.2.5 | Flexible printing options. In printing text, the system shall provide the capability for the user to select among available output formats (e.g., line spacing, character size, margin size, headers, footers) and to specify the pages of a document to be printed. | Not Applicable |
| 5.17.22.3 | Data and message transmission. | |
| 5.17.22.3.1 | Functional integration. Data transmission functions shall be integrated with other information handling functions within a system such that a user is able to transmit data using the same computer system and procedures used for general entry, display, and other processing of data. | Not Applicable |
| 5.17.22.3.2 | Consistent procedures. Procedures for preparing, sending, and receiving data and messages shall be consistent from one transaction to another and consistent with procedures for other information handling tasks. | Not Applicable |
| 5.17.22.3.3 | Minimal memory load on users. The system shall provide computer aids for automatic insertion of standard information, such as headers and distribution lists, in order to minimize memory load on the user. | Not Applicable |
| 5.17.22.3.4 | Messages. Messages shall be in accordance with the criteria in 5.17.22.3.4.1 through 5.17.22.3.4.8. 5.17.22.3.4.1 Stored message forms. Where message formats conform to a defined standard or are predictable in other ways, pre-stored forms shall be provided to aid users in message preparation. | Not Applicable |
| 5.17.22.3.4.2 | Incorporate existing files. Users shall be allowed to incorporate an existing data file in a message, combine several files into a single message for transmission, and combine stored data with new data when preparing messages for transmission. | Not Applicable |
| 5.17.22.3.4.3 | Reenter data. It shall not be necessary to reenter any data already entered for other purposes. | Not Applicable |
| 5.17.22.3.4.4 | Interrupt. Users shall be allowed to interrupt message preparation, review, or disposition and then resume any of those tasks from the point of interruption. | Not Applicable |
| 5.17.22.3.4.5 | Data group labels. Each individual data group or message shall contain a descriptive title, phrase, word, or similar device to designate the content of the group or message. | Not Applicable |
| 5.17.22.3.4.6 | Location of message labels. Labels shall be consistently located adjacent to (and preferably above or to the left of) the data group or message they describe. | Not Applicable |
| 5.17.22.3.4.7 | Emergency or critical messages. Labels shall use an accentuating technique different and easily distinguished from the method used to highlight or code emergency or critical messages. | Not Applicable |
| 5.17.22.3.4.8 | Originator identification. Except for broadcast communication systems, the transmitter of each message in inter-user communications shall be automatically identified, if possible. | Not Applicable |
| 5.17.22.3.5 | Addresses. When users must specify the address for messages, prompting shall be provided to guide the user in the process. | Not Applicable |
| 5.17.22.3.6 | Directories. Users shall be provided with a built-in directory showing all acceptable forms of message addressing for each destination in the system and for links to external systems. | Not Applicable |
| 5.17.22.3.6.1 | Computer aids. Computer aids shall be provided so that a user can search an address directory by specifying a complete or partial name. | Not Applicable |
| 5.17.22.3.6.2 | Extract addresses. Users shall be able to extract selected addresses from a directory for direct insertion into a header in order to specify the destination(s) for a message. | Not Applicable |
| 5.17.22.4 | Geospatial displays. | |
| 5.17.22.4.1 | Use. Geographic displays shall only be used for data that can be geo-referenced. | Compliant |
| 5.17.22.4.2 | Types. Editable geographic coordinate displays allow users to enter a specific geographic location in one of several coordinate systems, such as decimal degrees; military grid reference system (MGRS); or degrees, minutes, seconds (DMS). Non-editable displays are system-generated values that match system or user-selected geographic coordinate system format. | Compliant |
| 5.17.22.4.3 | Default geographic coordinate systems. Geospatial displays should have the option to save a default geographic coordinate system (e.g., decimal, MGRS, DMS). | Compliant |
| 5.17.22.4.4 | Geospatial display options. Geographic displays are normally composed of a base map, overlays, and individual drawings. To permit customization and decluttering functionality, a list of options of available visual elements should be available to the user. Functionality of these options may include, but is not limited to, the following elements: a. Toggle element visibility – the ability to show and hide individual visual elements. b. Opacity – the ability to control how many visual elements can be seen when overlapped with other visual elements. c. Precedence – the ability to set the order in which visual elements are layered over each other. d. Hierarchical grouping – the ability to apply the above functionality to both individual visual elements and logical groupings, as required. | Compliant |
| 5.17.22.4.5 | Geospatial display drawings. If the user is provided the capability to draw on the geospatial display, the following functionality should be provided: a. Manipulation – drawings should be able to be moved, resized, or deleted after being initially placed. Resizing should include the capability to keep the aspect ratio locked. b. Zooming and panning – the user should be able to zoom and pan the underlying base map while drawing. c. Editing – relevant drawing properties (e.g., color, opacity, labeling) should be editable before and after the drawing is made. | Compliant |
| 5.17.22.4.6 | Relative positioning. Drawings should be able to be aligned relative to other visual elements, such as other drawings or a grid overlay. | Compliant |
| 5.17.23 | Automated system displays. See 5.12.3. | |
| 5.17.24 | Coding of information. | |
| 5.17.24.1 | Use of coding. Coding shall be used to facilitate discriminating between individual views (e.g., different modes of operation); identifying functionally related displays; showing the relationships between displays; and identifying critical information, unusual values, changed items, items to be changed, high priority messages, special areas of the display, errors in entry, criticality of command entry, and targets. | Compliant |
| 5.17.24.2 | Meaningful coding. Meaningful codes shall be used. | Compliant |
| 5.17.24.3 | Common coding conventions. Commonly used coding conventions should be used. | Compliant |
| 5.17.24.4 | Impact on performance. Coding shall not reduce legibility or adversely impact user or system performance. | Compliant |
| 5.17.24.5 | Consistent coding. All coding within the system shall be consistent. | Compliant |
| 5.17.24.6 | Techniques. The following visual characteristics may be used for coding: color, brightness, flash, size, pattern, location, underlining, symbol, or shape. | Compliant |
| 5.17.24.7 | Air crew display symbology. Air crew display symbology shall be coded in accordance with JSSG-2010 and MIL-STD-1787. | Not Applicable |
| 5.17.25 | Color coding. Color coding shall be in accordance with the criteria in 5.17.25.1 through 5.17.25.16.4. | |
| 5.17.25.1 | Use. Color coding may be employed to differentiate between classes of information in complex, dense, or critical displays or to provide a means of indicating similarity among items (grouping items) along some meaningful dimension. | Compliant |
| 5.17.25.2 | Foveal view only. Color shall not be used for gaining attention outside the optimum visual field. | Compliant |
| 5.17.25.3 | Consistency. Color coding shall be used consistently within a display and, where appropriate, across displays of other systems used by the same users. | Compliant |
| 5.17.25.4 | Color customization. Color customization by users shall be allowed only for information that is not tactically significant. | Non-Compliant |
| 5.17.25.5 | Color recognition. When the user must recognize categories of information (e.g., represent different variables on a graph, different types of information on a map) a maximum of 11 nameable colors shall be used to represent and distinguish between categorically different information. | Compliant |
| 5.17.25.6 | Color differentiation. When using color to group elements of a display together (i.e., to show parts are related or different) and the color has no meaning beyond a grouping function, colors should be discriminable. | Compliant |
| 5.17.25.7 | Saturation coding. Hue saturation may be used to indicate relative intensity (e.g., best, hottest, wettest, safest, deepest). The following are standardized uses of saturation that should be followed: a. Hotter to cooler where saturation changes from red to blue. b. More dangerous to less dangerous – saturation of red increases as danger increases. | Compliant |
| 5.17.25.8 | Color meanings. Colors shall be associated with the common meanings presented in table XL. | Compliant |
| 5.17.25.8.1 | Cool colors. Cool colors (those with shorter wavelengths, such as blue or green) shall be used to display information used infrequently and to convey status of background information. | Compliant |
| 5.17.25.8.2 | Warm colors. Warm colors (those with longer wavelengths, such as red or orange) shall be used to convey action or the requirement for a response. | Compliant |
| 5.17.25.9 | Dark adaptation. When color coding is used, luminance shall be more than 10 cd/m2 (2.9 fL). | Non-Compliant |
| 5.17.25.10 | Color-blind users. If the user population includes color-blind users, every effort should be made for non-confusable colors to be used for coding. | Compliant |
| 5.17.25.11 | Redundant coding. If non-confusable colors cannot be used for coding for color-blind users, redundant coding shall be used. | Compliant |
| 5.17.25.12 | Induced color-blindness. Operational requirements occasionally result in the need to introduce protective eyewear, visors, or other filters in the optical path that are designed to absorb or reflect measurable and uniquely specifiable wavelengths of directed energy within the visible spectrum. This results in selectively induced color deficiencies or color blindness. As such, color coding in display design shall not be the only means of coding information for affected operational systems. | Compliant |
| 5.17.25.13 | Object size. When accurate color perception is required, the major dimension of isolated large symbols shall subtend not less than 8.7 milliradians (30 minutes) of visual angle and should subtend not less than 13.1 milliradians (45 minutes). | Not Applicable |
| 5.17.25.14 | Object height. When accurate color perception is required, the height of small symbols and characters should subtend at least 5.8 milliradians (20 minutes) of visual angle, as measured from the longest anticipated viewing distance. | Not Applicable |
| 5.17.25.15 | Fill symbols. To enhance detectability and discriminability, color-filled symbols shall be used instead of outlined symbols. | Compliant |
| 5.17.25.16 | Color contrast and differences. | |
| 5.17.25.16.1 | Color contrast. Colored symbols shall differ from their background by not less than 100 ΔE (color difference) (CIE Luv*) distances when calculated using the formula below. The elements required for the calculation are the luminance (Y), the UCS coordinates (u’, v’) for foreground and background colors, and the maximum luminance for the display (YM). As with the (CIE Luv*) distances, caution should be used in assessing legibility for characters in colors having small luminance differences. This caution applies not only to characters in color but also to small luminance differences in background colors and for very small luminance differences between characters in color and background in color. Unusually large or small characters may lead to erroneous estimates of legibility. The metric is as follows: | Non-Compliant |
| 5.17.25.16.2 | Color differences. Colors in a set shall differ from one another by not less than 20 ΔE (CIE Luv*) distances when calculated using the formula below. | Non-Compliant |
| 5.17.25.16.3 | Text and background pairings for daytime or artificial lighting. Text 14-point font or less should have a luminance contrast ratio of above 4.5:1. Text larger than 14-point font should have a contrast ratio of at least 3:1. Black or dark text should be on a light background. | Non-Compliant |
| 5.17.25.16.4 | Text and background pairings for dark conditions. White or light text should be on a dark background. | Non-Compliant |
| 5.17.26 | Brightness coding. | |
| 5.17.26.1 | Use. Brightness intensity coding should be employed only to differentiate between an item of information and adjacent information. | Compliant |
| 5.17.26.2 | Brightness intensity levels. No more than two levels of brightness shall be used, and each level shall be separated from the nearest other level by not less than a 2:1 ratio. | Compliant |
| 5.17.26.3 | Brightness inversion. When a capability for brightness inversion is available (so-called “reverse video” where dark characters on a bright background can be changed under computer control to bright on dark, or vice versa), it may be used for highlighting critical items that require user attention. When a capability for brightness inversion is available and when used for alerting purposes, brightness inversion shall be reserved for that purpose and not be used for general highlighting. | Compliant |
| 5.17.27 | Flash coding. | |
| 5.17.27.1 | Use. Flash coding should be employed to call the user’s attention to mission-critical events only. | Non-Compliant |
| 5.17.27.2 | Duty cycle. The percentage of “on” time shall be equal to but not less than the percentage of “off” time; a 50 percent duty cycle is preferred. | Not Applicable |
| 5.17.27.3 | Flash rate. No more than two flash rates shall be used. | Not Applicable |
| 5.17.27.3.1 | Flash rate differences. The two flash rates shall differ by not less than 2.0 hertz. | Not Applicable |
| 5.17.27.3.2 | Higher flash rate. The higher flash rate shall be not greater than 5.0 hertz. | Not Applicable |
| 5.17.27.3.3 | Slower flash rate. The slower flash rate shall be not less than 0.8 hertz. | Not Applicable |
| 5.17.27.3.4 | Critical information. The higher flash rate shall reflect more critical information. | Not Applicable |
| 5.17.27.4 | Flash rate synchronization. Items flashing at the same rate shall be synchronized. | Not Applicable |
| 5.17.27.5 | Flash rate text. Characters that must be read shall not flash; an adjacent flashing symbol, flashing background, or alternating brightness intensity may be used to add emphasis to text. | Not Applicable |
| 5.17.27.6 | Flash suppression. Event acknowledgment or flash suppression control shall be provided. | Not Applicable |
| 5.17.27.7 | Flashing area. Only a small area of a display should flash at any time. | Not Applicable |
| 5.17.28 | Size coding. No more than three size levels shall be used. The major dimensions of the larger size shall be not less than 150 percent of the major dimension of the smaller. | Compliant |
| 5.17.29 | Pattern and location coding. Pattern and location coding may be used to reduce user search time by restricting the area to be searched to prescribed segments. | Non-Compliant |
| 5.17.30 | Underlining coding. Underlining may be employed to indicate unusual values, errors in entry, changed items, or items to be changed. | Non-Compliant |
| 5.17.31 | Symbol coding. | |
| 5.17.31.1 | Use. Symbol coding may be used to enhance information assimilation from data displays. | Compliant |
| 5.17.31.2 | Symbol selection. Symbols shall be analogs of the event or system element they represent or be in general use and well known to the expected users. | Compliant |
| 5.17.31.3 | Special symbols. When special symbols are used to signal critical conditions, they shall be used for only that purpose. | Compliant |
| 5.17.31.4 | Markers close to words marked. When a special symbol is used to mark a word, the symbol shall be separated from the beginning of the word by one space. | Compliant |
| 5.17.32 | Shape coding. Shape coding may be used for search and identification tasks. When shape coding is used, the codes selected should be based on established standards or conventional meanings. | Not Applicable |
TABLE V. Acceptable system response times.
| System Interpretation | Response Time Definition | Time (Seconds) |
|---|---|---|
| Key response, including scroll wheels, optical wheels, mouse clicks | Key pressed until positive response (e.g., “click”) | 0.1 |
| Key print | Key pressed until appearance of character | 0.2 |
| Page turn | End of request until first few lines are visible | 1.0 |
| Page scan | End of request until text begins to scroll | 0.5 |
| XY entry | From selection of field until visual verification | 0.2 |
| Pointing | From input of point to display point | 0.2 |
| Sketching | From input of point to display of line | 0.2 |
| Local update | Change to image using local database (e.g., new menu list from display buffer) | 0.5 |
| Host update | Change where data is at host in readily accessible form (e.g., a scale change of existing image) | 2.0 |
| File update | Image update requires an access to a host file | 10 |
| Inquiry (simple) | From command until display of a commonly used message | 2.0 |
| Inquiry (complex) | Response message requires seldom used calculations in graphic form | 10 |
| Error feedback | From entry of input until error message appears | 0.2 |