This checklist clarifies how SuperWEB2 conforms with the WCAG 2.1 guidelines. SuperWEB2 confirms at the AA level.
Guideline 1: Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
|1.1 Text Alternatives||Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.|
|1.1.1 Non-text Content||All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.|
SuperWEB2 is predominately text based. Where there are icons and buttons that use images, these now have alternative descriptive text.
Alternative descriptive text has also been added to the screenshot images in the supplied user guide.
|1.2 Time-based Media||Provide alternatives for time-based media.||Not Applicable. SuperWEB2 does not contain time-based media (video/audio).|
|1.3 Adaptable||Create content that can be presented in different ways (for example simpler layout) without losing information or structure.|
|1.3.1 Info and Relationships||Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.|
ARIA tags have been implemented across the product so that the roles of user interface elements can be programmatically determined.
|1.3.2 Meaningful Sequence||When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.||The underlying code across the SuperWEB2 solution has been organised so that the reading order of the content makes sense.|
|1.3.3 Sensory Characteristics||Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, colour, size, visual location, orientation, or sound.||SuperWEB2 does not contain content that solely relies on sensory characteristics.|
|1.3.4 Orientation||Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.||SuperWEB2 functions in both portrait and landscape orientations.|
|1.3.5 Identify Input Purpose||The purpose of each input field collecting information about the user can be programmatically determined.||The only area of SuperWEB2 where information about the user is collected is the user registration process. By default, only name, email and password are collected, and all of these fields use standard HTML labels that allow the fields to be programmatically determined.|
|1.4 Distinguishable||Make it easier for users to see and hear content including separating foreground from background.|
|1.4.1 Use of Colour||Colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.||SuperWEB2 does not use colour as the only means of conveying information.|
|1.4.2 Audio Control||If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.||Not Applicable. SuperWEB2 does not have audio features.|
|1.4.3 Contrast (Minimum)||The visual presentation of text and images of text has a contrast ratio of at least 4.5:1.||SuperWEB2 supports the specified contrast ratio.|
|1.4.4 Resize Text||Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.||SuperWEB2 supports resizing of text up to 200 percent.|
|1.4.5 Images of Text||If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text.||SuperWEB2 does not use images of text.|
|1.4.6 Contrast (Enhanced)||The visual presentation of text and images of text has a contrast ratio of at least 7:1.||Not Applicable (AAA level).|
|1.4.7 Low or No Background Audio||Prerecorded audio-only content does not contain background sounds, can be turned off, or is at least 20 db lower than foreground speech.||Not Applicable (AAA level, and SuperWEB2 does not have audio features).|
|1.4.8 Visual Presentation||For the visual presentation of blocks of text, a mechanism is available to allow users to select foreground/background colours, width is no more than 80 characters, text is not justified, line spacing is at least space and a half, and text can be resized without assistive technology.||Not Applicable (AAA level).|
|1.4.9 Images of Text||Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.||Not Applicable (AAA level).|
|1.4.10 Reflow||Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions.||SuperWEB2 supports reflow of contents without requiring scrolling in two dimensions.|
|1.4.11 Non-text Contrast||The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent colour(s).||SuperWEB2 supports the specified contrast ratio.|
|1.4.12 Text Spacing|
In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting line height, spacing, letter spacing or word spacing.
|SuperWEB2 allows text spacing overrides.|
|1.4.13 Content on Hover or Focus|
This item relates to content that becomes visible when an element receives pointer hover or keyboard focus.
|SuperWEB2 does not contain this type of content.|
Guideline 2: Operable
Make all functionality available from a keyboard.
|2.1 Keyboard Accessible||Make all functionality available from a keyboard.|
|2.1.1 Keyboard||All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.||SuperWEB2 can be operated using the keyboard. See Keyboard Navigation for more details.|
|2.1.2 No Keyboard Trap||If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.||You can use the Tab key to navigate through the interactive elements and links within SuperWEB2. In addition, ARIA landmarks have been added to SuperWEB2 enabling users of screen readers to use their screen reader's shortcuts to skip to defined areas of the product, such as the header, footer and the main body area.|
|2.1.3 Keyboard (No Exception)||All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.||Not Applicable (AAA level).|
|2.1.4 Character Key Shortcuts||If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then either a mechanism is available to turn the shortcut off, a mechanism is available to remap the shortcut or the shortcut is only active when the component has focus.||Not applicable, as SuperWEB2 does not use this type of shortcut.|
|2.2 Enough Time||Provide users enough time to read and use content.|
|2.2.1 Timing Adjustable|
Relates to time limits set by content.
|Not Applicable. SuperWEB2 does not have time-limited content.|
|2.2.2 Pause, Stop, Hide||Relates to moving, blinking, scrolling, or auto-updating information.||Not Applicable. SuperWEB2 does not have this type of content.|
|2.2.3 No Timing||Timing is not an essential part of the event or activity presented by the content.||Not Applicable. SuperWEB2 does not have this type of content.|
|2.2.4 Interruptions||Interruptions can be postponed or suppressed by the user.||Not Applicable (AAA level).|
|2.2.5 Re-authenticating||When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.||Not Applicable (AAA level).|
|2.2.6 Timeouts||Users are warned of the duration of any user inactivity that could cause data loss.||Not Applicable (AAA level).|
|2.3 Seizures and Physical Reactions||Do not design content in a way that is known to cause seizures or physical reactions.||The items in this section do not apply to SuperWEB2 as it does not contain any flashing or animated content.|
|2.3.1 Three Flashes or Below Threshold||Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.||Not Applicable. SuperWEB2 does not have this type of content.|
|2.3.2 Three Flashes||Web pages do not contain anything that flashes more than three times in any one second period.||Not Applicable (AAA level).|
|2.3.3 Animation from Interactions||Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.||Not Applicable (AAA level).|
|2.4 Navigable||Provide ways to help users navigate, find content, and determine where they are.|
|2.4.1 Bypass Blocks||A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.||Use the Tab key to navigate through the interactive elements and links within SuperWEB2. In addition, ARIA landmarks have been added to SuperWEB2 enabling users of screen readers to use their screen reader's shortcuts to skip to defined areas of the product, such as the header, footer and the main body area.|
|2.4.2 Page Titled||Web pages have titles that describe topic or purpose.||All pages of SuperWEB2 have a descriptive title.|
|2.4.3 Focus Order||If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.||SuperWEB2 uses a logical top-to-bottom and left-to-right order for navigating through the elements on the page with the Tab key.|
|2.4.4 Link Purpose (In Context)||The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.||Links in SuperWEB2 use text or tags (or both) to describe the purpose of the link.|
|2.4.5 Multiple Ways||More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.||There are multiple ways to navigate through the pages of SuperWEB2, including|
|2.4.6 Headings and Labels||Headings and labels describe topic or purpose.||Headings in SuperWEB2 correctly identify the section they relate to.|
|2.4.7 Focus Visible||Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.||When the keyboard is used to navigate through SuperWEB2, the web browser highlights the element that currently has focus.|
|2.4.8 Location||Information about the user's location within a set of Web pages is available.||Not Applicable (AAA level).|
|2.4.9 Link Purpose (Link Only)||A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.||Not Applicable (AAA level).|
|2.4.10 Section Headings||Section headings are used to organize the content.||Not Applicable (AAA level).|
|2.5 Input Modalities||Make it easier for users to operate functionality through various inputs beyond keyboard.|
|2.5.1 Pointer Gestures||All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.||Not Applicable. SuperWEB2 does not use multipoint or path-based gestures.|
|2.5.2 Pointer Cancellation|
For functionality that can be operated using a single pointer, at least one of the following is true:
|The only operation in SuperWEB2 where this item applies is the drag and drop capability in Table View. This operation can be cancelled by releasing the item outside of the drop target.|
|2.5.3 Label in Name||For user interface components with labels that include text or images of text, the name contains the text that is presented visually.||SuperWEB2 does not use images of text. Elements such as buttons are rendered using standard HTML code and can be properly interpreted by sceen readers and other assistive technology.|
|2.5.4 Motion Actuation||Functionality that can be operated by device motion or user motion can also be operated by user interface components.||Not Applicable. SuperWEB2 does not use device or user motion.|
|2.5.5 Target Size||The size of the target for pointer inputs is at least 44 by 44 CSS pixels.||Not Applicable (AAA level).|
|2.5.6 Concurrent Input Mechanisms||Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.||Not Applicable (AAA level).|
Guideline 3: Understandable
Information and the operation of user interface must be understandable.
|3.1 Readable||Make text content readable and understandable.|
|3.1.1 Language of Page||The default human language of each Web page can be programmatically determined.||All pages in SuperWEB2 have a |
|3.1.2 Language of Parts||The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.||All pages in SuperWEB2 have a |
|3.1.3 Unusual Words||A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.||Not Applicable (AAA level).|
|3.1.4 Abbreviations||A mechanism for identifying the expanded form or meaning of abbreviations is available.||Not Applicable (AAA level).|
|3.1.5 Reading Level||When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.||Not Applicable (AAA level).|
|3.1.6 Pronunciation||A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.||Not Applicable (AAA level).|
|3.2 Predictable||Make Web pages appear and operate in predictable ways.|
|3.2.1 On Focus||When any user interface component receives focus, it does not initiate a change of context.||Changes of context do not occur when an element receives focus.|
|3.2.2 On Input||Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behaviour before using the component.||Changing settings on interface components does not cause a change of context. For example forms such as the search forms will not submit until the user submits the form using the relevant button (either via the mouse or the keyboard).|
|3.2.3 Consistent Navigation||Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.||The main navigation components appear on the same order on each page of SuperWEB2.|
|3.2.4 Consistent Identification||Components that have the same functionality within a set of Web pages are identified consistently.||Controls across SuperWEB2 are displayed and behave consistently.|
|3.2.5 Change on Request||Changes of context are initiated only by user request or a mechanism is available to turn off such changes.||Not Applicable (AAA level).|
|3.3 Input Assistance||Help users avoid and correct mistakes.|
|3.3.1 Error Identification||If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.||SuperWEB2 displays error messages where appropriate.|
|3.3.2 Labels or Instructions||Labels or instructions are provided when content requires user input.||SuperWEB2 provides labels or instructions for all user interface fields.|
|3.3.3 Error Suggestion||If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.||SuperWEB2 displays error messages where appropriate.|
|3.3.4 Error Prevention (Legal, Financial, Data)|
For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, submissions must either be reversible, checked for errors or allow the user to confirm before submitting.
|Not Applicable. SuperWEB2 does not have operations that cause legal commitments or financial transactions to occur, and it is not possible for users to make changes to the data (user access to data is read-only).|
|3.3.5 Help||Context-sensitive help is available.||Not Applicable (AAA level).|
|3.3.6 Error Prevention (All)||For Web pages that require the user to submit information, submissions must either be reversible, checked for errors or allow the user to confirm before submitting.||Not Applicable (AAA level).|
Guideline 4: Robust
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
|4.1 Compatible||Maximize compatibility with current and future user agents, including assistive technologies.|
|4.1.1 Parsing||In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.||All pages have been validated to confirm that SuperWEB2 uses valid HTML across the product.|
|4.1.2 Name, Role, Value||For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.|
ARIA tags have been implemented across the product so that the roles of user interface elements can be programmatically determined.
|4.1.3 Status Messages||In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.||Status messages have role attributes with the value of |