Criteria
Conformance Level
Remarks and Explanations
The Web UI and Documentation were tested for:
- Images that convey information have meaningful alternative text using ALT
- Images that are decorative are marked up using ALT=”” or CSS background images
- Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
- Titles for Objects and Applets are provided
- Controls have an associated name
- Text summary or alternative is provided for time-based media
- Client-side image maps specify the ALT attribute on each AREA element.
- CAPTCHAs are not used
The Web UI and Documentation were tested for:
- User interface component labels are associated with the fields they are labeling
- Headings are encoded with HTML heading tags
- List markup is used for marking up lists
- Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
- Data tables specify SUMMARY or CAPTION
- Layout tables use appropriate markup
- Groups of components are marked up with their description
- Style sheets are used only to change the layout and presentation on the screen
The Web UI and Documentation were tested for:
- The sequence of elements in the DOM matches a logical reading sequence
The Web UI and documentation were tested for:
- Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
- Instructions provided which refer to graphics included a reference to the text alternative of the graphic
The Web UI and documentation were tested for:
- The application pages can be displayed in both portrait and landscape mode.
- The pages are adjusted for size based on the orientation automatically.
The Web UI and documentation were tested for:
- The input fields where the user input in requested follow the guidelines specified athttps://www.w3.org/TR/WCAG21/#input-purposes
- The form input data fileds have meaningful text to make it clear the meaning of the input.
The Web UI and documentation were tested for:
- Information is not conveyed using color
The Web UI and documentation were tested for:
- Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
- Other text and images of text have a contrast ratio of at least 4.5:1
The Web UI and documentation were tested for:
See Also
Reactor Physics | Definition & Applications | nuclear-power.comERDDAP - Sea Surface Salinity, Miras SMOS, Near Real-Time, Global 0.25°, 2010-present, 3 Day Composite, Lon0360Oracle Big Data Spatial and Graph 3Materials Science - Materials Engineering- Text can be resized up to 200% without loss of content or functionality
The Web UI and documentation were tested for:
- Images of text are not used
The Web UI and documentation were tested for:
- The page size automatically adjusts so that no scrolling is required.
The Web UI and documentation were tested for:
- User interface components like buttons and menus have a contrast ratio of at least 3:1 against adjacent colors (cololrs for text, buttons, etc)
- Graphical object (symbols, images)have a contrast ratio of at least 3:1 against adjacent colors
The Web UI and documentation were tested for:
- When the following attributes and no others are modified there is no loss in functionality or content:
- Line height (line spacing) to at least 1.5 times the font size
- Spacing following paragraphs to at least 2 times the font size
- Letter spacing (tracking) to at least 0.12 times the font size
- Word spacing to at least 0.16 times the font size
The Web UI and documentation were tested for:
- Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing
- Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
- Information appears on hover or focus using default browser behavior, such as the title attribute of components.
The Web UI and documentation were tested for:
- Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
- Ability to use the product with OS keyboard aids StickyKeys, FilterKeys and ToggleKeys
- Proper operation of unique keystrokes and access keys, including those listed in the product documentation
The Web UI and documentation were tested for:
- Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
The WebUI and Documentation were tested for:
- Keyboard shortcuts are not used.
The Web UI and documentation were tested for:
- Time limits are not used in this product.
The Web UI and documentation were tested for:
- There is no moving, blinking or scrolling content
- There is no content that is auto-updating
The Web UI and documentation were tested for:
- No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
The Web UI and documentation were tested for:
- A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
- Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
The Web UI and documentation were tested for:
- Pages have a meaningful title specified in the TITLE element
The Web UI and documentation were tested for:
- Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
The Web UI and documentation were tested for:
- The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose
The Web UI was tested for:
- Pages are fully inter-linked to each other
- Page contains controls that enable reaching all pages
The documentation wastested for:
- Pages are contained in a "site map"
- Pages can be found using the provided "search" function
- Pages are in a site table of contents
- Pages are fully inter-linked to each other
- Page contains controls that enable reaching all pages
The Web UI and documentation were tested for:
- Headers describe the topic or purpose of the content below them
- Labels describe the purpose of the associated field
The Web UI and documentation were tested for:
- Visual indication of the location of the focus
The WebUI and Documentation were tested for:
- Multipoint or path-based gestures are not used.
The WebUI and Documentation were tested for:
- When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion.
The WebUI wastested for:
- User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.
The WebUI and Documentation were tested for:
- Application does not have any functionality that can be operated by device motion.
The Web UI and the documentation were tested for:
- Properly setlangattribute for each page
The Web UI and documentation were tested for:
- Proper use oflangattribute for text passages that are in a different language than that of the page
The Web UI and documentation were tested for:
- When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
The Web UI and documentation were tested for:
- Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
- In circ*mstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components
The Web UI and documentation were tested for:
- Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time
The Web UI and documentation were tested for:
- Images and controls are used and identified consistently throughout the product
The Web UI and documentation were tested for:
- When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
The Web UI and documentation were tested for:
- Labels or instructions are provided when the product requires user input
The Web UI and documentation were tested for:
- Where suggestions for fixing an input error are known, they are provided to the user
The Web UI and documentation were tested for:
- Submissions can be reversed by the user
- Data is checked for input errors with an opportunity for the user to correct them
- Data can be reviewed, corrected, and confirmed by the user before they are finalized
The Web UI and documentation were tested for:
- Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
- Pages validate to the HTML specification
The Web UI and documentation were tested for:
- HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.
- Custom controls have a meaningful programmatically exposed name
- Frames have a meaningful title specified in the title attribute
The WebUI wastested for:
- Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.
