tag indicates that the user is navigating within sidebar content. The id="main-content" tag indicates that the user is navigating within the main section of the user interface. The tag indicates that the user is navigating within the page’s header.

RadiantOne sequences page content in a meaningful way and uses HTML tags to allow reading sequences to be programmatically determined. Tables use HTML table elements. Lists use HTML UL and LI tags.

Instructions for understanding and operating the RadiantOne service do not rely solely on visual location, shape, size, or orientation. Text messages and audio cues are also provided using text-to-speech-narration tools. Focus is not removed from the element the user is currently on.

RadiantOne’s display orientation does not change.

RadiantOne text fields, check boxes, radio buttons, and other input fields are clearly identified so that their purpose can easily be determined.

Guideline 1.4 – Distinguishable

RadiantOne offers accessible alternative cues that convey information, prompt the user for a response, and distinguish visual elements.

RadiantOne does not use any elements that require audio control.

On each screen, RadiantOne’s foreground and background colors contrast each other sufficiently for all content, including text and screen elements.

RadiantOne users can resize fonts without any loss of content or functionality.

RadiantOne uses text to convey information, rather than images of text, unless the text is part of a graphic.

RadiantOne’s Control Panel UI screens reflow automatically to accommodate web browser zooming. Content reflows without overlapping or text being cut off.

RadiantOne user interface components and graphical objects uses borders to achieve a 3:1 or greater contrast ratio of adjacent colors.

RadiantOne’s HTML supports word, line, and paragraph formatting properties that help prevent the loss of content and functionality. Furthermore, RadiantOne uses flex-styled CSS containers, not fixed containers. Content reflows without overlap or text being cut off.

RadiantOne contains content that is triggered by hovering the pointer. The pointer can be moved over this content without obscuring the content.

Guideline 2.1 – Keyboard Accessible

All functionality should be available from the keyboard.

RadiantOne makes each screen fully keyboard navigable and operable by making sure that all screen elements that can be accessed with the mouse can be reached using the keyboard alone.

All RadiantOne functionality is operable through the keyboard. Keyboard focus can be moved to and from components using the keyboard only.

RadiantOne does not use keyboard shortcuts.

Guideline 2.2 – Enough Time

RadiantOne UI session timeouts can be adjusted using the Control Panel Session Timeout function.

RadiantOne does not contain information that moves or blinks. Windows are scrolled through manually by the user.

Guideline 2.3 – Seizures and Physical Reactions

RadiantOne does not contain blinking content.

Guideline 2.4 – Navigable

This guideline ensures users can navigate, find content and determine where they are.

RadiantOne offers keyboard users an option to bypass blocks of content that are repeated on multiple pages. When the users navigates past the main tabs using the keyboard’s Tab key, RadiantOne displays a “Press enter to skip to settings content” button.

RadiantOne’s HTML head section says, “Radiant Logic, Inc. | Cluster Control Panel”.

Most RadiantOne page contents are not sequential. RadiantOne wizards are sequential and are navigated accordingly.

RadiantOne links have meaningful names that can be understood when read alone or in the context of surrounding content.

RadiantOne’s Main Control Panel uses a single URL. Each wizard, however, uses several URLs. These wizards include configuration steps that are part of a process.

RadiantOne code is marked up where text is styled and/or formatted to organize content into sections and subsections.

Pressing the keyboard Tab key cycles through fields in the RadiantOne UI, with the active field highlighted.

Guideline 2.5 – Input Modalities

This guideline ensures users can operate functionality through various inputs beyond the keyboard.

RadiantOne does not contain multi-point or path-based gestures for operation.

With the exception of opening drop-down lists, the pointer’s down-event does not execute functions in RadiantOne.

RadiantOne fields, including text fields, drop-down lists, buttons, have labels that describe the corresponding field.

RadiantOne does not contain functionality that can be operated by device motion or user motion.

Guideline 3.1 – Readable

This guideline ensures content is readable and understandable.

RadiantOne’s default human language is specified in its HTML.

RadiantOne’s code does not contain any non-English language sentences or phrases.

Guideline 3.2 – Predictable

This guideline ensures the web page appears and operates in predictable ways.

In RadiantOne, when the user tabs through user interface components, this does not initiate the change of context.

When a user interacts with content on a page, RadiantOne’s behavior is predictable. When focus changes, it happens in a predictable way.

RadiantOne screen navigation and repetitive screen content are accessible by positioning and structuring repetitive screen navigation consistently. RadiantOne includes a way to skip over repetitive content.

RadiantOne components that have the same functionality, such as Add, Edit, and Delete buttons, wizard configuration buttons,

Guideline 3.3 – Input Assistance

This guideline helps users avoid and correct mistakes.

RadiantOne detects input errors automatically. When an improper value is entered, the error is identified and described with a text in a popup box.

RadiantOne labels for user input are meaningful and unique. This includes text boxes, radio buttons, check boxes, drop-down lists, and list boxes.

RadiantOne input errors are automatically detected and corrected. The user interface then displays a message informing the user of the incorrect input value and the value that RadiantOne replaced it with.

RadiantOne does not contain web pages that cause legal commitments or financial transactions to occur.

Guideline 4.1 – Compatible

This guidelines maximizes compatibility with current and future user agents, including assistive technologies.

RadiantOne screen element structures and relationships in the code are marked up. The code on each page in the UI parses correctly.

RadiantOne user interface component accessible names and roles can be programmatically determined. Roles, states, and properties that can be set by the user can be set in a methodical manner.

RadiantOne status messages present information to users using assistive technologies.