CognaLearn | InteDashboard | Accessibility


In line with InteDashboard’s values of Purpose-driven, Collaborative, Innovative, Learning, Versatility, and Integrity:

We recognise that diversity is the heart of every team, and that every member should be respected.
We aim to empower users by removing barriers to access learning, and ensuring inclusivity for all users to learn and contribute, regardless of ability.
We design with accessibility in mind, and work towards attaining the highest possible compliance to international standards such as WCAG 2.1, Section 508 and EN 301 549, so as to minimize exclusion and improve outcomes for all.
We will review feedback and evaluate our product to ensure continued adherence to guidelines, and are committed to making accessibility a priority at CognaLearn.

 

Measures to Support Accessibility

CognaLearn takes the following steps in our accessibility journey

● Including accessibility in development process, and alignment to standards in WCAG 2.1 AA Level
● Accessibility goals and responsibilities are clearly assigned
● Product Team is knowledgeable in web accessibility principles
● Include accessibility in company’s mission
● Charted accessibility roadmap for continued adherence

Conformance Status

InteDashboard is partially compliant with the Web Content Accessibility Guidelines version 2.1 A and AA standard.

The criteria for Level AAA have not been evaluated.

Accessibility Limitations

We are aware and are making conscious efforts to improve.
The content listed below are non-accessible for the following reasons.

● Not all form controls are grouped or have accessible names. 
● Tab order and keyboard navigation are not fully intuitive in sections across the app.
● Page titles on some pages may not accurately reflect user location. 
● Some missing or incorrect button labels exist. 
● Some completed sections or input requirement hints use only colour to indicate meaning.
● Some numeric input controls lack keyboard-only functionality.
● While basic landmarks exist in pages, headers may not follow ideal hierarchy. 
● Bypass links are hence not currently supported.
● Activity time limits are currently not communicated to screen readers. 
● Ideal colour contrast standards are not supported across the app. 

We are rectifying these issues systematically and aim to be fully compliant in later releases.

In addition, our Help Guides and Website are progressively making changes to ensure that all users are able to access and benefit from our content.

As InteDashboard is an authoring software, Instructor users have the ability to upload their own content. It is the user’s responsibility to ensure the content they generate is accessible.

Feedback

We are working hard in our journey to full WCAG compliance.
We welcome feedback on accessibility matters in relation to InteDashboard. Do let us know if you have suggestions or encounter accessibility barriers.
You can reach us at support@intedashboard.com.
We will try to respond to feedback within 3 business days.

Compatibility with Browsers and Assistive Technologies

Screen Readers: NVDA, JAWS, VoiceOver, ChromeVox

Browsers: Google Chrome, Mozilla Firefox, Safari, Microsoft Edge

Technologies Used

HTML, WAI-ARIA, CSS, JavaScript

 


 

InteDashboard Accessibility Conformance Report 

 

Name of Product/Version: InteDashboard 
Product Description: Online TBL Software
Date: 13 July 2022
Contact information: support@intedashboard.com
Evaluation Methods Used: InteDashboard was reviewed manually and with automated tools. Screen Readers NVDA and ChromeVox with Google Chrome on Mac and Windows OS.

This report covers the degree of conformance for the following accessibility standard/guidelines:

Terms

The terms used in the Conformance Level information are defined as follows:
Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criterion.
Does Not Support: The majority of product functionality does not meet the criterion.
Not Applicable: The criterion is not relevant to the product.
Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.1 Level AAA.

 

WCAG 2.1 Report

Tables 1 and 2 also document conformance with:
● EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
● Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: Success Criteria, Level A

Criteria Conformance Level Remarks and Explanations

1.1.1 Non-text Content (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.1.1 (Web)

●     10.1.1.1 (Non-web document)

●     11.1.1.1.1 (Open Functionality Software)

●     11.1.1.1.2 (Closed Functionality Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

 

Images have an alt attribute and most non-text elements have ARIA labels for screen readers.

 

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.2.1 (Web)

●     10.1.2.1 (Non-web document)

●     11.1.2.1.1 (Open Functionality Software)

●     11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

 

InteDashboard does not have built in pre-recorded audio or video content.

 

InteDashboard does not currently support the uploading of audio or video content by Instructors. Instructors can link to external content.

1.2.2 Captions (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.2.2 (Web)

●     10.1.2.2 (Non-web document)

●     11.1.2.2 (Open Functionality Software)

●     11.1.2.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

 

InteDashboard does not contain pre-recorded audio-only or video-only media, however instructor users have the ability to upload their own media that can be audio-only or video-only. It is the responsibility of users to provide closed captioning for any pre-recorded audio content in synchronized media.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.2.3 (Web)

●     10.1.2.3 (Non-web document)

●     11.1.2.3.1 (Open Functionality Software)

●     11.1.2.3.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

 

InteDashboard does not contain pre-recorded audio media, however instructor users have the ability to upload their own media. It is the user’s responsibility to select an accessible media player for their content

1.3.1 Info and Relationships (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.3.1 (Web)

●     10.1.3.1 (Non-web document)

●     11.1.3.1.1 (Open Functionality Software)

●     11.1.3.1.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Partially Supports

 

This is partially available due to the use of layout tables in both the instructor and learner app. We aim to be fully compliant in later releases of the learner app in 2023.

 

We use nested HTML lists to describe parent/child relationships between information such as courses > modules > activities.

 

Heading tags are used but some lack proper hierarchy.

1.3.2 Meaningful Sequence (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.3.2 (Web)

●     10.1.3.2 (Non-web document)

●     11.1.3.2.1 (Open Functionality Software)

●     11.1.3.2.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Partially Supports

 

For the learner experience only, the tab button can be used to cycle actionable buttons and links. On some screens, the arrow keys are also available. The use of tabindex in the app is also being reviewed.

 

Some sections in the Instructor app, particularly for tables, may be skipped in the Tab order. We aim to be fully compliant in later releases in 2023.

1.3.3 Sensory Characteristics (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.3.3 (Web)

●     10.1.3.3 (Non-web document)

●     11.1.3.3 (Open Functionality Software)

●     11.1.3.3 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

 

 

Supports

 

Instructions in InteDashboard do not solely rely on sensory characteristics. A textual representation is provided alongside.

 

Occasionally icons may be used for aesthetic purposes but all buttons and links are available with text labels that are clear in user navigation.

 

1.4.1 Use of Color (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.4.1 (Web)

●     10.1.4.1 (Non-web document)

●     11.1.4.1 (Open Functionality Software)

●     11.1.4.1 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Partially Supports

 

Available on both Instructor and Learner experiences.

 

Accommodated for color-blindness and color is used to achieve aesthetic consistency but is not the primary representation for meaning.

Some exceptions include form input requirements that use colour to indicate completion.

Some charts in the Instructor app also use coloured lines and legends to display student data analysis.
We aim to be fully compliant in later releases in 2023.

1.4.2 Audio Control (Level A)

Also applies to:

EN 301 549 Criteria

●     9.1.4.2 (Web)

●     10.1.4.2 (Non-web document)

●     11.1.4.2 (Open Functionality Software)

●     11.1.4.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

InteDashboard does not have built in audio content.

 

InteDashboard does not currently support the uploading of audio content by Instructors. Instructors can link to external content.

2.1.1 Keyboard (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.1.1 (Web)

●     10.2.1.1 (Non-web document)

●     11.2.1.1.1 (Open Functionality Software)

●     11.2.1.1.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Partially Supports

Most interactive components can be navigated by keyboard in the learner app using either the tab key or the arrow keys. However input to numeric text boxes in certain sections may be limited with keyboard-only navigation.

It is partially available in the instructor app, due to skipped focus for some UI elements. This is slated to be rectified by Q3 2022.

2.1.2 No Keyboard Trap (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.1.2 (Web)

●     10.2.1.2 (Non-web document)

●     11.2.1.2 (Open Functionality Software)

●     11.2.1.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

The Tab button can be used to cycle through the entire range of UI elements infinitely.

This is fully available on the learner facing application.

 

We aim to be fully compliant in later releases in 2023.

2.1.4 Character Key Shortcuts (Level A 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.2.1.4 (Web)

●     10.2.1.4 (Non-web document)

●     11.2.1.4.1 (Open Functionality Software)

●     11.2.1.4.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Not Applicable

InteDashboard currently does not support Character shortcut keys.

2.2.1 Timing Adjustable (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.2.1 (Web)

●     10.2.2.1 (Non-web document)

●     11.2.2.1 (Open Functionality Software)

●     11.2.2.1 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

Due to the nature of the use of InteDashboard in an online-class, only the Instructor-type user has the ability to: Preset time limits, Pause time limits, Extend time limits.

We are deploying a feature to allow custom time extensions in Q3 2022.

2.2.2 Pause, Stop, Hide (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.2.2 (Web)

●     10.2.2.2 (Non-web document)

●     11.2.2.2 (Open Functionality Software)

●     11.2.2.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

InteDashboard does not support moving, blinking or auto-scrolling content.

2.3.1 Three Flashes or Below Threshold (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.3.1 (Web)

●     10.2.3.1 (Non-web document)

●     11.2.3.1 (Open Functionality Software)

●     11.2.3.1 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

InteDashboard does not support flashing or blinking content.

2.4.1 Bypass Blocks (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.4.1 (Web)

●     10.2.4.1 (Non-web document) – Does not apply

●     11.2.4.1 (Open Functionality Software) – Does not apply

●     11.2.4.1 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software) – Does not apply to non-web software

●     504.2 (Authoring Tool)

●     602.3 (Support Docs) – Does not apply to non-web docs

Does Not Support

Landmarks and proper page heading elements are slated in later releases in 2023.

2.4.2 Page Titled (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.4.2 (Web)

●     10.2.4.2 (Non-web document)

●     11.2.4.2 (Open Functionality Software) - Does not apply

●     11.2.4.2 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

All pages will update the HTML’s title attribute when content changes.

2.4.3 Focus Order (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.4.3 (Web)

●     10.2.4.3 (Non-web document)

●     11.2.4.3 (Open Functionality Software)

●     11.2.4.3 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Partially Supports

Focus order via the tab button is partly consistent with how a user may navigate that content, however some errors exist in the Instructor app that sections may be skipped such as ‘Question Type’ and ‘Freeze last option’ toggle button. Modal dialogs may also not receive focus in proper sequence.

 

We aim to progressively fix these issues and be fully compliant in later releases.

2.4.4 Link Purpose (In Context) (Level A)

Also applies to:

EN 301 549 Criteria

●     9.2.4.4 (Web)

●     10.2.4.4 (Non-web document)

●     11.2.4.4 (Open Functionality Software)

●     11.2.4.4 (Closed Software

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

Most links are labeled appropriately with their intended action.

However, links to user-uploaded content such as attachments are at users’ discretion.

2.5.1 Pointer Gestures (Level A 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.2.5.1 (Web)

●     10.2.5.1 (Non-web document)

●     11.2.5.1 (Open Functionality Software)

●     11.2.5.1 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Does Not Support

InteDashboard does not use multi-point and path based gestures in the learner app.

However, the instructor app requires path-based gestures such as dragging movement for allocating learners into teams. An accessible pointer alternative will be included in later releases.

2.5.2 Pointer Cancellation (Level A 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.2.5.2 (Web)

●     10.2.5.2 (Non-web document)

●     11.2.5.2 (Open Functionality Software)

●     11.2.5.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Functions in InteDashboard are only activated on up-event, and cancellation is supported.

2.5.3 Label in Name (Level A 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.2.5.3 (Web)

●     10.2.5.3 (Non-web document)

●     11.2.5.3.1 (Open Functionality Software)

●     11.2.5.3.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially Supports

Where an input field, button or link has a visible text label, the label also matches the programmatic name for most components. Errors have been slated for rectification by Q3 2022.

2.5.4 Motion Actuation (Level A 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.2.5.4 (Web)

●     10.2.5.4 (Non-web document)

●     11.2.5.4 (Open Functionality Software)

●     11.2.5.4 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Not Applicable

InteDashboard currently does not contain functions operated by device motion or user motion.

3.1.1 Language of Page (Level A)

Also applies to:

EN 301 549 Criteria

●     9.3.1.1 (Web)

●     10.3.1.1 (Non-web document)

●     11.3.1.1.1 (Open Functionality Software)

●     11.3.1.1.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

InteDashboard is currently only available in English so the language attribute is hard-coded in.

 

This means that while course content could be uploaded in another language, the language attribute is not automatically updated.

3.2.1 On Focus (Level A)

Also applies to:

EN 301 549 Criteria

●     9.3.2.1 (Web)

●     10.3.2.1 (Non-web document)

●     11.3.2.1 (Open Functionality Software)

●     11.3.2.1 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

When any component receives focus, it does not initiate a change of context.

3.2.2 On Input (Level A)

Also applies to:

EN 301 549 Criteria

●     9.3.2.2 (Web)

●     10.3.2.2 (Non-web document)

●     11.3.2.2 (Open Functionality Software)

●     11.3.2.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.


An exception for this is in the (Instructor) Courses > Add Student where a new table row is added upon user input.
We are aiming to improve user experience by adding a status message notification.

3.3.1 Error Identification (Level A)

Also applies to:

EN 301 549 Criteria

●     9.3.3.1 (Web)

●     10.3.3.1 (Non-web document)

●     11.3.3.1.1 (Open Functionality Software)

●     11.3.3.1.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

If an input error is automatically detected, the item that is in error is identified and the error is described to the user.

3.3.2 Labels or Instructions (Level A)

Also applies to:

EN 301 549 Criteria

●     9.3.3.2 (Web)

●     10.3.3.2 (Non-web document)

●     11.3.3.2 (Open Functionality Software)

●     11.3.3.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

Visual labels or instructions are provided for UI elements when content requires user input. 

4.1.1 Parsing (Level A)

Also applies to:

EN 301 549 Criteria

●     9.4.1.1 (Web)

●     10.4.1.1 (Non-web document)

●     11.4.1.1.1 (Open Functionality Software)

●     11.4.1.1.2 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

HTML is code-checked with ESLINT. All start-tags will have an end-tag and no repeat of attributes.

4.1.2 Name, Role, Value (Level A)

Also applies to:

EN 301 549 Criteria

●     9.4.1.2 (Web)

●     10.4.1.2 (Non-web document)

●     11.4.1.2.1 (Open Functionality Software)

●     11.4.1.2.2 (Closed Software) – Not required

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Partially Supports

Most buttons, form inputs and links use ARIA tags and CSS classes to indicate their current states.

 

Some buttons lack programmatic association with the visual label, or checkbox states not indicated and these have been slated for rectification by Q3 2022.

Table 2: Success Criteria, Level AA

Criteria Conformance Level Remarks and Explanations

1.2.4 Captions (Live) (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.1.2.4 (Web)

●     10.1.2.4 (Non-web document)

●     11.1.2.4 (Open Functionality Software)

●     11.1.2.4 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

InteDashboard does not contain live media, however instructor users have the ability to upload their own media that can be audio-only or video-only. It is the responsibility of users to provide closed captioning for any audio content in synchronized media.

1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.1.2.5 (Web)

●     10.1.2.5 (Non-web document)

●     11.1.2.5 (Open Functionality Software)

●     11.1.2.5 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

InteDashboard does not contain pre-recorded audio media, however instructor users have the ability to upload their own media. It is the user’s responsibility to select an accessible media player for their content

1.3.4 Orientation (Level AA 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.1.3.4 (Web)

●     10.1.3.4 (Non-web document)

●     11.1.3.4 (Open Functionality Software)

●     11.1.3.4 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Both portrait and landscape mode are supported.

1.3.5 Identify Input Purpose (Level AA 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.1.3.5 (Web)

●     10.1.3.5 (Non-web document)

●     11.1.3.5.1 (Open Functionality Software)

●     11.1.3.5.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially Supports

Most form inputs have either a visual or are programmatically associated. However some only contain placeholder text and lack a label.

 

These have been slated for rectification by Q3 2022.

 

1.4.3 Contrast (Minimum) (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.1.4.3 (Web)

●     10.1.4.3 (Non-web document)

●     11.1.4.3 (Open Functionality Software)

●     11.1.4.3 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Does Not Support

Expected in releases by 2023.

1.4.4 Resize text (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.1.4.4 (Web)

●     10.1.4.4 (Non-web document)

●     11.1.4.4.1 (Open Functionality Software)

●     11.1.4.4.2 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

Resize text functionality is provided for both learner and instructor users. 

1.4.5 Images of Text (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.1.4.5 (Web)

●     10.1.4.5 (Non-web document)

●     11.1.4.5.1 (Open Functionality Software)

●     11.1.4.5.2 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

 

By default, there are no images of text in InteDashboard. 

Instructor users have the ability to upload their own content. It is the user’s responsibility to make sure the content they generate is accessible.

1.4.10 Reflow (Level AA 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.1.4.10 (Web)

●     10.1.4.10 (Non-web document)

●     11.1.4.10 (Open Functionality Software)

●     11.1.4.10 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially Supports

InteDashboard supports screen expansion to 200%, however some components may become inaccessible with the keyboard.

 

We aim to progressively fix these issues and be fully compliant in later releases.

1.4.11 Non-text Contrast (Level AA 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.1.4.11 (Web)

●     10.1.4.11 (Non-web document)

●     11.1.4.11 (Open Functionality Software)

●     11.1.4.11 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Not Applicable

InteDashboard does not contain non-text content that affects text contrast.

1.4.12 Text Spacing (Level AA 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.1.4.12 (Web)

●     10.1.4.12 (Non-web document)

●     11.1.4.12 (Open Functionality Software)

●     11.1.4.12 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Basic text resizing is available.

1.4.13 Content on Hover or Focus (Level AA 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.1.4.13 (Web)

●     10.1.4.13 (Non-web document)

●     11.1.4.13 (Open Functionality Software)

●     11.1.4.13 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially supports

Drop boxes or combo boxes are persistent upon selection, however most lack the mechanism to be dismissed using Esc key.

2.4.5 Multiple Ways (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.2.4.5 (Web)

●     10.2.4.5 (Non-web document) – Does not apply

●     11.2.4.5 (Open Functionality Software) – Does not apply

●     11.2.4.5 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software) – Does not apply to non-web software

●     504.2 (Authoring Tool)

●     602.3 (Support Docs) – Does not apply to non-web docs

Supports

Yes, multiple ways to access content exist. They are designed for intuitiveness, not just to conform to this standard.

 

For instance, in order to view/edit a question you can either go to the questions bank or to a course > module > activity > question. Upcoming features include multiple tabs which allow Instructor users to navigate between activities in a course.

2.4.6 Headings and Labels (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.2.4.6 (Web)

●     10.2.4.6 (Non-web document)

●     11.2.4.6 (Open Functionality Software)

●     11.2.4.6 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

Headings and labels sufficiently describe topic or purpose of each section.

2.4.7 Focus Visible (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.2.4.7 (Web)

●     10.2.4.7 (Non-web document)

●     11.2.4.7 (Open Functionality Software)

●     11.2.4.7 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

When using the keyboard for navigation, either via the Tab key or the arrow keys, focused elements on the screen will have an obvious border.

3.1.2 Language of Parts (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.3.1.2 (Web)

●     10.3.1.2 (Non-web document)

●     11.3.1.2 (Open Functionality Software) – Does not apply

●     11.3.1.2 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Not Applicable

InteDashboard is currently only available in English.

3.2.3 Consistent Navigation (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.3.2.3 (Web)

●     10.3.2.3 (Non-web document) – Does not apply

●     11.3.2.3 (Open Functionality Software) – Does not apply

●     11.3.2.3 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software) – Does not apply to non-web software

●     504.2 (Authoring Tool)

●     602.3 (Support Docs) – Does not apply to non-web docs

Supports

Navigation is consistent across UI elements, and a navigation bar allows users a standard way to move across sections.

3.2.4 Consistent Identification (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.3.2.4 (Web)

●     10.3.2.4 (Non-web document) – Does not apply

●     11.3.2.4 (Open Functionality Software) – Does not apply

●     11.3.2.4 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software) – Does not apply to non-web software

●     504.2 (Authoring Tool)

●     602.3 (Support Docs) – Does not apply to non-web docs

Supports

Components that have the same functionality within a set of Web pages are identified consistently. 

3.3.3 Error Suggestion (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.3.3.3 (Web)

●     10.3.3.3 (Non-web document)

●     11.3.3.3 (Open Functionality Software)

●     11.3.3.3 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

When errors occur, the user is directed through text instruction on how to correct the error.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Also applies to:

EN 301 549 Criteria

●     9.3.3.4 (Web)

●     10.3.3.4 (Non-web document)

●     11.3.3.4 (Open Functionality Software)

●     11.3.3.4 (Closed Software)

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508

●     501 (Web)(Software)

●     504.2 (Authoring Tool)

●     602.3 (Support Docs)

Supports

For deletion of data, a warning is always presented to the user before they commit the action. In the backend, we “soft” delete data so they can be restored.

4.1.3 Status Messages (Level AA 2.1 only)

Also applies to:

EN 301 549 Criteria

●     9.4.1.3 (Web)

●     10.4.1.3 (Non-web document)

●     11.4.1.3 (Open Functionality Software)

●     11.4.1.3 (Closed Software) – Does not apply

●     11.8.2 (Authoring Tool)

●     12.1.2 (Product Docs)

●     12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially Supports

Status message notifications exist in InteDashboard, and announce alerts or changes to the user. Deletion or submission confirmation dialogs are available.

Table 3: Success Criteria, Level AAA

The product has not been evaluated for WCAG 2.1 Level AAA conformance.

 

Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria Conformance Level Remarks and Explanations

302.1 Without Vision

Does not Support

Most buttons, form inputs and links use ARIA tags and CSS classes to indicate their current states.

However, not all components have accessible names or are programmatically linked. Hence the app is not fully compatible with screen readers.

302.2 With Limited Vision

Partially Supports

Text is resizable, and screen magnification is supported.
However, the app is not fully compatible with screen readers for reasons as stated above.

302.3 Without Perception of Color

Partially Supports

Accommodated for color-blindness and color is used to achieve aesthetic consistency but is not the primary representation for meaning.

Some exceptions include form input requirements that use colour to indicate completion.

Some charts in the Instructor app also use coloured lines and legends to display student data analysis.

We aim to be fully compliant in later releases in 2023.

302.4 Without Hearing

Supports

InteDashboard does not use any audio for its default operation. Users can upload their own content and are responsible for ensuring the accessibility of the uploaded content.

302.5 With Limited Hearing

Supports

InteDashboard does not use any audio for its default operation. Users can upload their own content and are responsible for ensuring the accessibility of the uploaded content.

302.6 Without Speech

Not Applicable

InteDashboard does not require speech input for operation.

302.7 With Limited Manipulation

Partially Supports

Most interactive components can be navigated by keyboard in the learner app using either the tab key or the arrow keys. However input to numeric text boxes in certain sections may be limited with keyboard-only navigation.

 

It is partially available in the instructor app, due to skipped focus for some UI elements due to layout tables. We aim to be fully compliant in later releases.

302.8 With Limited Reach and Strength

Partially Supports

Assistive technologies which employ standard keyboard navigation are partially supported.

302.9 With Limited Language, Cognitive, and Learning Abilities

Does Not Support

We aim to be fully compliant in later releases.

Chapter 4: Hardware

InteDashboard is not a Hardware Product, hence Chapter 4 does not apply.

Chapter 5: Software

InteDashboard is a web based application and not a software product. Hence Chapter 5 does not apply.
However, relevant criteria are briefly discussed regarding authoring tools.

Criteria Conformance Level Remarks and Explanations

504 Authoring Tools

Heading cell – no response required

Heading cell – no response required

504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”)

See WCAG 2.1 section

See information in WCAG 2.1 section

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not Applicable

 

504.2.2 PDF Export

Does Not Support

 

504.3 Prompts

Does Not Support

Currently there are no prompts for users to improve the accessibility of their content. However, such functionality is slated to be provided in later releases of the Instructor app.

504.4 Templates

Not Applicable

 

 

Chapter 6: Support Documentation and Services

Criteria Conformance Level Remarks and Explanations

601.1 Scope

Heading cell – no response required

Heading cell – no response required

602 Support Documentation

Heading cell – no response required

Heading cell – no response required

602.2 Accessibility and Compatibility Features

Does Not Support

InteDashboard's user guides are in process of being updated to include accessibility features.

602.3 Electronic Support Documentation

See WCAG 2.1 section

See information in WCAG 2.x section

602.4 Alternate Formats for Non-Electronic Support Documentation

Not Applicable

All necessary documentation for InteDashboard is provided electronically.

603 Support Services

Heading cell – no response required

Heading cell – no response required

603.2 Information on Accessibility and Compatibility Features

Supports

The support team at InteDashboard can provide information about accessibility features of the product.

603.3 Accommodation of Communication Needs

Supports

All communication is available via electronic means such as email.

 

EN 301 549 Report

Chapter 4: Functional Performance Statements (FPS)

Criteria Conformance Level Remarks and Explanations

4.2.1 Usage without vision

Does Not Support

Most buttons, form inputs and links use ARIA tags and CSS classes to indicate their current states.

However, not all components have accessible names or are programmatically linked. Hence the app is not fully compatible with screen readers.

4.2.2 Usage with limited vision

Partially Supports

Text is resizable, and screen magnification is supported.
However, the app is not fully compatible with screen readers for reasons as stated above.

4.2.3 Usage without perception of colour

Partially Supports

Accommodated for color-blindness and color is used to achieve aesthetic consistency but is not the primary representation for meaning.

Some exceptions include form input requirements that use colour to indicate completion.

Some charts in the Instructor app also use coloured lines and legends to display student data analysis.

We aim to be fully compliant in later releases in 2023.

4.2.4 Usage without hearing

Supports

InteDashboard does not use any audio for its default operation. Users can upload their own content and are responsible for ensuring the accessibility of the uploaded content.

4.2.5 Usage with limited hearing

Supports

InteDashboard does not use any audio for its default operation. Users can upload their own content and are responsible for ensuring the accessibility of the uploaded content.

4.2.6 Usage with no or limited vocal capability

Not Applicable

InteDashboard does not require speech input for operation.

4.2.7 Usage with limited manipulation or strength

Partially Supports

Most interactive components can be navigated by keyboard in the learner app using either the tab key or the arrow keys. However input to numeric text boxes in certain sections may be limited with keyboard-only navigation.

 

It is partially available in the instructor app, due to skipped focus for some UI elements due to layout tables. We aim to be fully compliant in later releases.

4.2.8 Usage with limited reach

Partially Supports

Assistive technologies which employ standard keyboard navigation are partially supported.

4.2.9 Minimize photosensitive seizure triggers

Supports

InteDashboard by default, does not contain any flashing or seizure triggering content.

4.2.10 Usage with limited cognition, language or learning

Does Not Support

We aim to be fully compliant in later releases.

4.2.11 Privacy

Supports

InteDashboard does not affect nor restrict usage of standard privacy controls alongside assistive technologies. For example, users can connect a headset for private listening to screen reader announcements.

Chapter 5: Generic Requirements

InteDashboard supports standard assistive technologies and hence is not subject to the Closed Functionality criteria described in this Chapter.

Chapter 6: ICT with Two-Way Voice Communication

InteDashboard does not offer two-way voice communication and hence, is not subject to the requirements of this section.

Chapter 7: ICT with Video Capabilities

InteDashboard, by default, does not contain video content, however instructor users have the ability to upload their own video content. It is the user’s responsibility to make sure the content they generate is accessible.

Chapter 8: Hardware

InteDashboard is not a Hardware Product, hence this Chapter does not apply.

Chapter 9: Web (see WCAG 2.1 section)

InteDashboard partially supports WCAG 2.0 at Conformance Level A and AA.

Chapter 10: Non-Web Software

InteDashboard does not include non-web documents, hence this Chapter does not apply.

Chapter 11: Software

Criteria Conformance Level Remarks and Explanations

11.0 General (informative)

Heading cell – no response required

Heading cell – no response required

11.1.1.1 through 11.4.1.3

See WCAG 2.1 section

See information in WCAG 2.x section

11.5 Interoperability with assistive technology

Heading cell – no response required

Heading cell – no response required

11.5.1 Closed functionality

Heading cell – no response required

Heading cell – no response required

11.5.2 Accessibility services

Heading cell – no response required

Heading cell – no response required

11.5.2.1 Platform accessibility service support for software that provides a user interface

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.2 Platform accessibility service support for assistive technologies

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.3 Use of accessibility services

Supports

InteDashboard uses standard platform accessibility services.

11.5.2.4 Assistive technology

Not Applicable

InteDashboard is not an assistive technology.

11.5.2.5 Object information

Partially Supports

Some components have accessible names, roles and values

11.5.2.6 Row, column, and headers

Partially Supports

Layout tables are currently used in InteDashboard to organize content. This will be rectified to HTML best practices in later releases of the app.

11.5.2.7 Values

Does Not Support

Error and warning values have visual indication but are not supported with screen readers

11.5.2.8 Label relationships

Partially Supports

Most components have ARIA labels

11.5.2.9 Parent-child relationships

Supports

Nested HTML relationships are used

11.5.2.10 Text

Supports

 

11.5.2.11 List of available actions

Supports

 

11.5.2.12 Execution of available actions

Supports

 

11.5.2.13 Tracking of focus and selection attributes

Partially Supports

Layout tables are currently used in InteDashboard to organize content. This will be rectified to HTML best practices in later releases of the app.

11.5.2.14 Modification of focus and selection attributes

Does Not Support

 

11.5.2.15 Change notification

Partially Supports

Status Message notifications announce changes or alerts

11.5.2.16 Modifications of states and properties

Does Not Support

 

11.5.2.17 Modifications of values and text

Does Not Support

 

11.6 Documented accessibility usage

Heading cell – no response required

Heading cell – no response required

11.6.1 User control of accessibility features

Not Applicable

InteDashboard is not considered platform software as defined by EN 301 549.

11.6.2 No disruption of accessibility features

Supports

 

11.7 User preferences

Supports

The product respects user preferences from platform or OS settings.

11.8 Authoring tools

Heading cell – no response required

Heading cell – no response required

11.8.1 Content technology

Heading cell – no response required

Heading cell – no response required

11.8.2 Accessible content creation

See WCAG 2.1 section

(If not authoring tool, enter “Not Applicable”)

See information in WCAG 2.x section

11.8.3 Preservation of accessibility information in transformations

See WCAG 2.1 section

See information in WCAG 2.1 section

11.8.4 Repair assistance

See WCAG 2.1 section

See information in WCAG 2.1 section

11.8.5 Templates

See WCAG 2.1 section

See information in WCAG 2.1 section

 

Chapter 12: Documentation and Support Services

Criteria Conformance Level Remarks and Explanations

12.1 Product documentation

Heading cell – no response required

Heading cell – no response required

12.1.1 Accessibility and compatibility features

Does Not Support

InteDashboard's user guides are in process of being updated to include accessibility features. They can be found here: https://guides.intedashboard.com

12.1.2 Accessible documentation

See WCAG 2.1 section

See information in WCAG 2.1 section

12.2 Support Services

Heading cell – no response required

Heading cell – no response required

12.2.2 Information on accessibility and compatibility features

Supports

The support team at InteDashboard can provide more information about accessibility features of the product.

12.2.3 Effective communication

Partially Supports

InteDashboard's user guides are in process of being updated to include accessibility features.

12.2.4 Accessible documentation

See WCAG 2.1 section

See information in WCAG 2.1 section

 

Chapter 13: ICT Providing Relay or Emergency Service Access

InteDashboard does not provide relay or emergency services and hence, is not subject to the requirements of this section.