dominKnow | ONE: Accessibility Conformance Report (ACR) (VPAT)

As pioneers in standards-based publishing and web accessibility for the last 20 years, our commitment has a proven track record. We've been innovating with accessibility before it was "required" and when doing so was particularly challenging (e.g., Pre-WCAG 2). We made this decision because we felt and still feel that it was and is the right thing to do for the learning community. 

dominKnow, the developers of dominKnow | ONE, wants everyone to be able to use eLearning courseware created with dominKnow | ONE. That means, for example, end-users of the courseware can:

  • Use browser extensions and settings to change contrast levels, fonts, and font sizes
  • Zoom in up to 300% without the text spilling off the screen
  • Navigate the courseware using a keyboard alone
  • Navigate the courseware and input text by voice command using Dragon speech recognition software
  • Listen to all of the relevant content in the courseware using a screen reader (including the most recent versions of JAWS, NVDA, VoiceOver, and TalkBack)

General Guidelines

Avoid using the following interactions and content design treatments:

  • Text colors defined by the author that lack sufficient color contrast
  • Toggle controls and other stock objects that lack sufficient color contrast
  • Interactions that require use of a mouse such as drag-and-drop
  • Interactions that rely on visual cues such as interactive “try-it” modes of software simulations

Be aware of the unique features and capabilities of assistive technologies that may interpret the HTML produced by dominKnow | ONE differently:

  • JAWS 2023 announces mutually exclusive radio buttons inconsistently. Mutually exclusive means that when the user selects a radio button, any previously selected radio button in the same group becomes deselected, making it so only one can be selected.
  • Most assistive technologies do not allow navigation of Sequencing or Sorting interactions.
  • Menu status indicators do not programmatically indicate current, not visited, visited page states.
    • Note: Targeting 7.4.5.0.0 release
  • Voice command using Dragon Desktop Professional 16 skips odd numbers on Slider interactions.

Resources for Authors

Authors using dominKnow | ONE to create accessible eLearning courseware can access relevant accessibility resources within the tool. dominKnow also offers training for authors on how to develop accessible courseware using the tool. For more information on the available resources, visit our Getting Started in dominKnow | ONE and WCAG Accessibility Resources.

Evaluation Process

In response to a commissioned request by dominKnow, this Accessibility Statement and associated Accessibility Audit Report were produced by Interactive Advantage Corporation (IAC). Testing was supported by IAC team members who are familiar with the dominKnow software and who teach classes on how to develop accessible courseware with the product. Testing was performed by qualified individuals who hold recognized accessibility testing certifications and who routinely use assistive technologies when testing web-based content. Code-based inspection was the primary means of testing with supplemental manual testing performed as appropriate. The principal tester was Mary Ann Richards, U.S. Department of Homeland Security Trusted Tester Certification #TT190900082.

Details

Name of Product: dominKnow | ONE (7.4.6.0)

Report Date: December 22, 2023

Product Description: Authoring Tool

Contact Information: dominKnow: info@dominKnow.com & Interactive Advantage: support@interactiveadvantage.com

 

Notes: The audited product is a web application, hence only those parts of the tables, relevant to web pages have been filled in.

Evaluation Methods Used: WCAG 2.2 audit based on VPAT version 2.5. Audit was an independent assessment conducted by Interactive Advantage. Interactive Advantage tested a dominKnow Flow published output with accessibility testing tools. These tests were conducted on desktop computers running Windows 10 and mobile devices running iPadOS 14.8.1 and Android 13. Web browsers used in this evaluation include Chrome 116 and Safari Version 14. Tools used in this evaluation include JAWS Version 2023, NVDA 2023, VoiceOver iOS Version 14, TalkBack Version 14, Windows Magnifier Windows 10 Version 22H2, Dragon Desktop Professional 16, ANDI, Colour Contrast Analyzer Version 2.5, and Microsoft Inspect Object Version 7.2. These tests were conducted and supervised by a DHS certified Trusted Tester in coordination with a skilled dominKnow Flow developer who teaches classes on how to create accessible courses with dominKnow Flow.

 

Applicable Standards/Guidelines

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

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0

Level A (Yes)

Level AA (Yes)

Level AAA (No )

Web Content Accessibility Guidelines 2.1

Level A (Yes)

Level AA (Yes)

Level AAA (No )

Web Content Accessibility Guidelines 2.2

Level A (Yes)

Level AA (Yes)

Level AAA (No )

 

Terms

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 2x Level AAA.

WCAG 2.2 Report

Note: When reporting on conformance with the WCAG 2.2 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

 

CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text Content (Level A)Partially Supports

Most elements added to a page provide for the option to include Screen Reader and/or alt text. For elements that cannot have alt text assigned, authors can use text-based alternatives, such as Screen Reader text to communicate meaning.

Screen Reader text is a dominKnow feature that allows an author to add additional text-based context to an element which is rendered as an ARIA label in the published output.

Components of the following elements have non-text content but do not support or have limited support for the addition of alt text or other text alternatives such as Screen Reader text: Icons, Guide Me Simulation, Scenario images, Thermometers, Flip Set images, Flash Card images, Match Card images, Drag and Drop style questions, Hotspot questions, and Menu status indicators. Note: for many of these, alternative options exist – IE a flip set, use text instead of an image.

Guides to writing Alt Text

 

NOTE: Release 7.4.5.0.0 will include enhancements for text alternatives for icons, flip sets, flash cards, match cards. It also will include status indicators for menus.

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

Authors can add text-based alternatives for audio-only and video-only content.

For audio-only content, authors can add a transcript to the audio file itself or use text-based alternatives.

For video-only content, authors can provide a text description using text-based alternatives.

Working with Transcripts for Audio Files, Video Files and Pages >> https://dki.io/b14d0f5f

1.2.2 Captions (Prerecorded) (Level A)Supports

For captioning, authors can import closed caption files into video players.

System supported closed caption files include: SRT, VTT, and SBV.

Easy Closed Captioning (CC) File Upload for Videos with Multi-language Support >> https://dki.io/98da8568

What is a Closed Caption File?

Guides and Tools for creating Closed Captions

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)SupportsAuthors can provide a description of the visual content in videos as an alternate video file or provide access to a transcript with descriptions of visual aspects of the synchronized media on the same page or via a link.
1.3.1 Info and Relationships (Level A)

 

Partially Supports

Most elements are programmatically formatted to communicate informational relationships.

Interactions that need additional descriptive text include: Input Toggle, Learner Progress Radial Gauge, and Carousel.

Interactions that are simply not compliant because of inherent reliance on visual cues only: Sorting, Matching, Fill in the Blanks, and Sequencing interactions.

Release 7.4.5.0.0 will include enhancements to carousels and form controls.

1.3.2 Meaningful Sequence (Level A)

Supports

Content built in dominKnow Flow follows a top-to-bottom, left-to-right reading order by default. 

Authors should be aware of breakpoints and how responsive flow drives reading order. The author can control the order of content presented by placing the elements in sequenced Rows, Groups, and Sections.

Content built with Claro uses layer order for flow/tab order. Authors should review their layer order to make sure content proceeds in the intended reading order.

Authors should limit inline Pulldowns and inline Fill-in-the-Blank questions to one answer, so the association between question text and answer choice is clear.

1.3.3 Sensory Characteristics  (Level A)SupportsAuthors can provide text-based descriptions for content that can otherwise only be understood by shape, size, visual location, orientation, or sound.
1.4.1 Use of Color (Level A)Supports

Authors should provide complementary alternatives to explain information when color is used to convey information or instructions. Use patterns, textures, or text labels to differentiate information. 

Some question interactions display correct/incorrect selections using color, such as Practice/Exam Multiple-Choice, Matching, and Sequencing questions and Question/Exercises Click the Word, Matching, and Sequencing. In these cases, authors should include text-based feedback that indicates the correct/incorrect selections.

 

Default colors for questions can be set with the Theme Designer.

1.4.2 Audio Control (Level A)Supports

Audio and video players include play/pause and mute controls by default.

Authors can enable a more extensive set of controls or build custom controls that offer greater control of media by the learner. 

 

Controlling audio files.

2.1.1 Keyboard (Level A)Partially Supports

Most elements in courses developed with dominKnow Flow support keyboard accessibility.

Exceptions include: Markers, Video Playlist, Image Hotspot, Guide Me Simulation Job Aid, Sorting, and Drag and Drop style interactions.

2.1.2 No Keyboard Trap (Level A)Supports

Content developed with native elements supports navigation of all content without keyboard traps.

For custom HTML Widgets, authors should provide learners with a way to utilize keyboard controls to exit the HTML Widget content.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)Supports

The built-in keyboard content controls meet this standard and are only active on focus.

Media elements have shortcut keys/interactions but are not active when those objects are not in focus.

2.2.1 Timing Adjustable (Level A)Supports

Authors can create actions/triggers that give the user the ability to manipulate or extend the time limit and reveal notifications based on the time limit.

Authors should avoid using system timer variables as actions/triggers cannot be set by the author to give the user the ability to manipulate or extend the time limit and reveal notifications based on the time limit.

2.2.2 Pause, Stop, Hide (Level A)Supports

Default media players provide pause and stop controls for media. Content produced in dominKnow Flow does not inherently include moving, blinking, scrolling, or auto-playing content natively.

If this media is included by the authors, they should provide the learner with custom pause, stop, or hide functions for moving, blinking, scrolling, or auto-updating content.

2.3.1 Three Flashes or Below Threshold (Level A)Supports

Content produced in dominKnow Flow does not inherently include anything that flashes or blinks more than three times a second.

When adding animations or videos, authors should refrain from using content that flashes or blinks more than three times a second.

 

Trace Research and Development Center: Learn more about photosensitivity and how to test for it with your video and animated content.

2.4.1 Bypass Blocks (Level A)Supports

Authors should select a WCAG accessible theme. These Themes are identified with a “WCAG” badge in the Theme Browser. These Themes include skip navigation controls by default.

2.4.2 Page Title (Level A)Supports

The course title will be automatically used as the page title that appears in the browser tab using the attribute.

Title refers to the content focus as a whole. To further enhance this capability, we are adding ARIA live regions in 7.4.5 enabling subtopics (pages etc.) to be announced.

2.4.3 Focus Order (Level A)Supports

Flow content follows a top-to-bottom, left-to-right focus order by default.

The author can control the order of content presented by placing the elements in sequenced Rows, Groups, and Sections.

Claro content follows a bottom-to-top layer order controlled by the author.

2.4.4 Link Purpose (In Context) (Level A)Supports

dominKnow | ONE enables authors to create links with descriptive link text.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)Supports

dominKnow Flow includes and supports creation of single point operations for all functions.

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)SupportsTouch events happen when the learner releases the touch or mouse button. Learners can move the mouse away from a given element before they release to cancel/not activate the target.
2.5.3 Label in Name (Level A 2.1 and 2.2)Supports

Stock functions, such as Theme navigation buttons, include the name that matches the text that is presented visually.

Authors can also achieve this with custom elements. Make sure that Alt/Screen reader text matches on-screen labels.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)Not ApplicableThese types of controls are not currently supported by dominKnow | ONE. Learners can not control courses by moving their tablets or smartphones.
3.1.1 Language of Page (Level A)Supports

Authors can select the language in the course’s Properties.

A language identifier is automatically added to the published output for screen readers. No further work is required by authors.

e.g., When the project language is selected the system adds the identifier (lang="fr-FR" for French (France))

3.2.1 On Focus (Level A)Supports

By default, content does not change context when focus is brought to the element.

When developing custom content that changes context on focus, authors should provide proper explanation.

3.2.2 On Input (Level A)Supports

By default, content does not change context on input.

When authors develop custom content that changes context on input, proper explanation should be provided beforehand.

3.2.6 Consistent Help (Level A 2.2 only)Supports

dominKnow | ONR provides a consistent framework that enables authors to develop content where Help is available in a consistent place.

Authors can use Themes and/or Master Headers/Footers to display content in a consistent place across pages.

3.3.1 Error Identification (Level A)Supports

dominKnow | ONE will automatically warn learners on practice and test questions if they do not make a response choice when submitting.

Authors can also use actions/triggers to provide custom validations and feedback for any actions or submissions created with form controls or other elements.

3.3.2 Labels or Instructions (Level A)SupportsAuthors should provide sufficient instruction for all content that requires input.
3.3.7 Redundant Entry (Level A 2.2 only)Supports

Authors can use variables to automate redundant entry.

4.1.1 Parsing (Level A)

WCAG 2.0 and 2.1 – Always answer ‘Supports’

WCAG 2.2 (obsolete and removed)

SupportsFor WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.
4.1.2 Name, Role, Value (Level A)Partially Supports

WCAG-compliant Themes provide distinct semantic groups, ARIA landmarks, and structured controls that follow a consistent order and hierarchy.

 

Video Playlists are not supported. When using a Hotspot add information to the Screen Reader Text field to make it active. Alt text field is not read.

 

Table 2: Success Criteria, Level AA

CriteriaConformance LevelRemarks and Explanations
1.2.4 Captions (Live) (Level AA)Not ApplicabledominKnow | ONE does not use live broadcasts/audio content.
1.2.5 Audio Description (Prerecorded) (Level AA)

Supports

As per G173: Providing a version of a movie with audio descriptions found in the Sufficient Techniques section of the criteria, the Author can add the additional audio information to synchronized media by providing a second version of the movie where the original soundtrack and additional audio description have been combined in a single track.
1.3.4 Orientation (Level AA 2.1 and 2.2)

Supports

Content automatically responds and adjusts to screen width and orientation.
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)Partially Supports

Form Controls are labelled in a way that can be determined programmatically. dominKnow | ONE does not support auto-filling forms.

1.4.3 Contrast (Minimum) (Level AA)Supports

Authors can select colors for their Theme and content that meet a contrast ratio of 4.5:1 or higher.

The default coloration of some elements may not pass these criteria, such as the Toggles that use red, green, and grey colors. For these, high-contrast alternatives are provided. 

Themes also support additional color editing using CSS or JavaScript. 

 

See Color Contrast and Visual Impairment Tools for additional information and tools. 

1.4.4 Resize text (Level AA)SupportsLearners can use the built-in zoom controls in browsers and pinch-to-zoom gestures on mobile devices.
1.4.5 Images of Text (Level AA)Supports

Authors can develop content that does not include any images of text.

Authors can use onscreen text to represent textual elements instead of images of text.

1.4.10 Reflow (Level AA 2.1 and 2.2)SupportsContent automatically resizes and responds to meet these requirements when using dominKnow | ONE - Flow. dominKnow | ONE - Claro uses fixed aspect rations. They are designed to zoom in and out, but they can't reflow without losing design. Learners, when consuming this option, may see a vertical and or horizontal scroll bar at the highest zoom levels. 
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)Supports

Authors can design the Theme and page content using a contrast ratio of 3:1 or higher for images and background elements to enable learners with visual impairments to consume the content.

 

See Color Contrast and Visual Impairment Tools for additional information and tools. 

1.4.12 Text Spacing (Level AA 2.1 and 2.2)Supports

Content responds to custom styling applied by the learner.

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)SupportsWhen hover or focus causes content changes, the content is dismissible, hoverable, and persistent.
2.4.5 Multiple Ways (Level AA)SupportsdominKnow | ONE enables authors to provides multiple themes with multiple options with  navigation to direct learners to a specific page, including Theme menus, search, and navigation buttons. Authors may also utilize Master Headers and Footers to create their own navigation options.
2.4.6 Headings and Labels (Level AA)Supports

Theme-based player controls are labeled and identified by default.

Authors should create headings and labels that are clear and descriptive.

2.4.7 Focus Visible (Level AA)Supports

A visible Focus indicator is turned on by default in all courses such that all user interface components have a keyboard focus indicator that is visible. The focus defaults to a blue rectangle. The type of line (e.g., dashed, solid, dotted), color and width can all be set at the Theme level and reused across multiple projects.

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)Supports

The responsive nature of the dominKnow | ONE: Flow allows for all focused elements to be visible on screen.

For custom interactions, authors should use a “scroll to” action, to ensure all revealed content will be visible on screen.

2.5.7 Dragging Movements (Level AA 2.2 only)Partially Supports

The dominKnow | ONE’s native drag-type interactions cannot be completed by a single pointer without dragging.

Authors can use alternative types of interactions that do not require the learner to complete a dragging movement.

7.4.5.0.0 release will target updating drag and drop interactions to allow for click-click.

2.5.8 Target Size (Minimum) (Level AA 2.2 only)Supports

The size of all targets for pointer inputs tested were at least 24 by 24 CSS pixels.

Authors can customize the size and spacing of buttons, hyperlink text, and selectable elements as necessary to comply with the criteria.

Themes also support additional color editing using CSS or JavaScript.   

3.1.2 Language of Parts (Level AA)

Does Not Support

The language is defined in the project Properties and is inherited by all content in the project. dominKnow | ONE does not sure different screen reader languages for different objects within the same project.
3.2.3 Consistent Navigation (Level AA)

Supports

Navigational elements within built-in Themes are consistent.

For custom content, authors should create navigation in a consistent location and focus order globally.

3.2.4 Consistent Identification (Level AA)

Supports

Courses developed using built-in Themes have consistently identified components.

When creating a custom Theme or user controls/icons/buttons, authors should use the same design and identification for elements or interactions that are used more than once.

3.3.3 Error Suggestion (Level AA)

Supports

Courses include generic runtime system prompts by default. An example of this is the message that appears when the learner selects the Submit button before selecting an answer to a question.

Authors can use actions/triggers to provide custom suggestions for any actions or submissions created with form controls or other elements.

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

Supports

When creating elements that result in a commitment, authors should use popups or other message types and actions/triggers to provide the learner with an option to confirm the action after selecting their choice or cancel and reselect the choice.

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

Supports

Courses developed in dominKnow | ONE do not typically require authentication. Authors who choose to add authentication should provide alternatives.
4.1.3 Status Messages (Level AA 2.1 and 2.2)Not ApplicabledominKnow | ONE does not use status messages to convey information.

 

  0     0

Similar Projects

Questions  ( 0 )