Course Merchant
Accessibility Conformance Report published by D2L
Partial extraction. We read 30 of 31 Level A and 24 of 24 Level AA criteria from this document (98% coverage). The remainder are missing from our extraction, not necessarily from D2L's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 30 criteria
- Supports
- 19
- Partially supports
- 5
- Does not support
- 0
- Not applicable
- 6
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 15
- Partially supports
- 5
- Does not support
- 0
- Not applicable
- 4
- Not evaluated
- 0
Level AAA — 31 criteria
- Supports
- 24
- Partially supports
- 2
- Does not support
- 0
- Not applicable
- 5
- Not evaluated
- 0
Source: View the original report published by D2L.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (99)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | Test methods: TBT; SRT; UBT Features • Images and icons are provided with text alternative to inform users with visual impairments, in audio or braille, of the intent and purpose of such non-text elements through their screen readers or similar assistive technologies. • Controls and input fields have descriptive, contextual labels or title attributes. • Infographics and other large image files are included inside an HTML file with appropriate alternative description. • Screen reader users can view the source code editor to get information about text styles applied in Course Merchant. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Test Methods: MAT Features • Time-based media are not a part of Course Merchant • No other relevant media files. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | • Time-based media are not a part of Course Merchant • No other relevant media files. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Test methods: TBT; SRT; MAT; UBT Features • Assistive technologies can programmatically determine the information, structure and relationships conveyed through presentation. • Headings and ARIA landmarks are used to help convey presentation. • Links and images are unique and contextual making it easy for users to navigate options. • Tables mostly use row and column headers. Table headers use scope attribute where appropriate. • ARIA expanded/collapsed markup is not used to indicate menu states. This state is communicated through link names instead. • Image maps are not used. Exceptions • Search result structure requires more obvious formatting for screen readers, including the number of results & better spacing. • Order numbers should be included on the ‘Manage License’ page for ease of use. |
| 1.3.2 | Meaningful Sequence | A | Supports | Test Methods: SRT; UBT Features • Headings and ARIA landmarks are used to help convey relationships between content. • Pages are linear and read clearly without style sheets. |
| 1.3.3 | Sensory Characteristics | A | Supports | Test Methods: MAT; UBT Features • Any concepts suggested through shape, size, visual location, orientation, or sound is also communicated using text. • Textual equivalents may be visible or hidden (alt text, titles, ARIA alerts, etc.). |
| 1.4.1 | Use of Color | A | Supports | Test Methods: TBT; CCT: Grayscale bookmarklet Features |
| 1.4.2 | Audio Control | A | Not Applicable | • Course Merchant does not use audio controls/alerts. |
| 2.1.1 | Keyboard | A | Partially Supports | Test Methods: MAT: Keyboard + visual focus; SRT; UBT Features • Forms are accessible by keyboard and assistive technologies. Some forms use a combination of fields, buttons, inline help, and links. |
| 2.1.2 | No Keyboard Trap | A | Supports | Test Methods: MAT: Keyboard; SRT; UBT Features • No keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Test Methods: MAT; UBT Features • Single character shortcut keys are not used, and shortcut keys are active only on focus. • Users activating controls using speech input are able to speak single input characters without accidentally activating some control. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Course Merchant does not contain any timing controls. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | Course Merchant does not use any spinners or timing indicators. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | Test Methods: MAT |
| 2.4.1 | Bypass Blocks | A | Supports | Test Methods: MAT: Keyboard; SRT; TBT: Landmarks bookmarklet; UBT Features • ‘Skip to main content’ links, headings and ARIA landmarks help users avoid repetitive and non-essential content. • The expanded/collapsed state of secondary form content is clearly indicated, and the fields are accessible. |
| 2.4.2 | Page Titled | A | Supports | Test Methods: MAT; TBT: Landmarks bookmarklet Features |
| 2.4.3 | Focus Order | A | Supports | Test Methods: MAT: Keyboard & visual focus; SRT; UBT Features • Each page has a logical tab order and visible tab stops. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Test Methods: MAT; SRT Features • Links are unique and contextual, usually in the format [action] [applicable item]. |
| 2.5.1 | Pointer Gestures | A | Supports | Test Methods: TBT; MAT; UBT Features • Single-point actions can be used to operate any functionality that can be operated with a pointer. • Path-based or multi-point gestures are not required to operate any functionality, except for gestures that are standard to the operating system. |
| 2.5.2 | Pointer Cancellation | A | Not Applicable | No drag & drop functionality in Course Merchant |
| 2.5.3 | Label in Name | A | Partially Supports | Test Methods: TBT; MAT; SRT; UBT Features • Programmatic labels provided to user interface components include all or part of the text that is presented as visual label (or the meaning represented by the icon) at the start to work well with voice input tools. Exception • Some links unresponsive to voice commands. |
| 2.5.4 | Motion Actuation | A | Supports | Test Methods: TBT; MAT; UBT Features • No function of our mobile apps relies on motion for actuation. |
| 3.1.1 | Language of Page | A | Supports | Test Methods: TBT; SRT Features • Language of content is notified at start of page and when changed within page. |
| 3.2.1 | On Focus | A | Supports | Test Methods: MAT; SRT; UBT Features • We have visible on-focus states that use a combination of colour and border effect to highlight the focused elements. These are built into our controls and defined into our design patterns. |
| 3.2.2 | On Input | A | Supports | Test Methods: MAT; SRT; UBT Features • Changing the setting of any UI component does not cause an unexpected change in the context automatically. |
| 3.2.6 | Consistent Help | A | Not Applicable | There are no consistent help links in Course Merchant by default. |
| 3.3.1 | Error Identification | A | Partially Supports | Test Methods: TBT; SRT Features • Error messages are communicated using a combination of ARIA alerts, ARIA landmarks, headings and links. • Where possible, error messages describe each error Exception • Links to the erroring fields missing in some places. |
| 3.3.2 | Labels or Instructions | A | Supports | Test Methods: TBT; SRT; UBT Features • Forms have clear headings, labels, field sets, and buttons. Inline help is provided as needed. • The expanded/collapsed state of secondary form content is clearly indicated, and the fields are accessible. |
| 3.3.7 | Redundant Entry | A | Supports | Test Methods: MAT Inspection Features: • System does not require re-entry of redundant information. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Test Methods: TBT; SRT Features • Controls are developed and validated against HTML specifications and standards, including ARIA. Exception • Some elements require more explicit labelling (tabs/accordions). |
| 1.2.4 | Captions (Live) | AA | Not Applicable | • Time-based media are not a part of Course Merchant |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | • No videos on Course Merchant |
| 1.3.4 | Orientation | AA | Supports | Test Methods: TBT; MAT Features • When a page or app is opened on a mobile device, it is presented in the device’s current display orientation. • When the device is rotated, the content adjusts to the new display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Supports | • The purpose of each input field collecting information about the user can be programmatically determined |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Test Methods: TBT; CCT; SMT; UBT Features • Foreground to background contrast adheres to standards Exception • License enrolment confirmation message does not meet the required contrast. |
| 1.4.4 | Resize text | AA | Supports | Test Methods: TBT; SMT; UBT Features • Icons and text resize with scaling/zooming options of browser (and other technology) up to 200%. |
| 1.4.5 | Images of Text | AA | Supports | Test Methods: MAT; SRT Features • Images of text are not used. |
| 1.4.10 | Reflow | AA | Supports | Test Methods: TBT; MAT; UBT Features • Course Merchant is built with responsive design and reflow in mind based on our design system. • Pages mostly reflow when the viewport is set to smaller phone sizes. |
| 1.4.11 | Non-text Contrast | AA | Supports | Test Methods: TBT; MAT; UBT Features • Active user interface components have a contrast ratio of 3:1 with the background. |
| 1.4.12 | Text Spacing | AA | Supports | Test Methods: TBT; MAT; UBT Features • Course Merchant is built with responsive design and reflow in mind based on our design system to accommodate changes in content size due to text spacing changes made by the user. • When text spacing is adjusted, content does not get cut off or overlap on most pages. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Test Methods: TBT; MAT; UBT Features • No content changes are applied on hover or focus in Course Merchant |
| 2.4.5 | Multiple Ways | AA | Supports | Test Methods: MAT: Inspection; UBT Features • Headings, ARIA landmarks (such as navigation landmarks) and unique link and button names help users navigate pages quickly. • Pages have consistent navigation areas. • Many pages contain search fields with ARIA search landmarks. • The system works well with search and find features built into assistive technologies. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Test Methods: MAT: Inspection; UBT Features • Pages have descriptive headings and labels. Labels are unique and contextual. Exception • Accordion needs specific labelling. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Test Methods: MAT: Keyboard + visual focus Features • Each page has a logical tab order and visible tab stops. • Links and fields have extra highlighting, beyond browser defaults. Exception • Following page refresh, focus is not visible within the magnified viewport. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Supports | Test Methods: Inspection Features: • Focus indicators are not obscured. |
| 2.5.7 | Dragging Movements | AA | Not Applicable | Course Merchant doesn’t support drag-and-drop. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | Test Methods: Inspection Features: • All targets meet the minimum size requirements. |
| 3.1.2 | Language of Parts | AA | Not Applicable | Although this version of Course Merchant does support additional languages, these are not in scope for the purposes of this document as the template is only configured in English. |
| 3.2.3 | Consistent Navigation | AA | Supports | Test Methods: TBT; MAT: Inspection; SRT; SMT Features • Navigation models are consistent across tools and use headings and ARIA navigation landmarks to help orient users. |
| 3.2.4 | Consistent Identification | AA | Supports | Test Methods: SRT; SMT Features |
| 3.3.3 | Error Suggestion | AA | Partially Supports | Test Methods: MAT: Inspection; SRT; SMT Features • Error messages are communicated using a combination of ARIA alerts, ARIA landmarks, headings and links. • Where possible, error messages describe each error Exception • Forms don’t link to the erroneous field. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | • Course Merchant allows users to confirm, correct, or reverse terms & conditions of sale. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Test Methods: MAT: Inspection Features • Course Merchant does not use biometric technologies for authentication. |
| 4.1.3 | Status Messages | AA | Partially Supports | Test Methods: TBT; MAT; UBT Features • Screen reader users get audio alerts. Exception • The number of courses returned by search results is updated on the screen but is not read by assistive technology. |
| 1.2.6 | Sign Language (Prerecorded) | AAA | Not Applicable | • Time-based media are not a part of Course Merchant |
| 1.2.7 | Extended Audio Description (Prerecorded) | AAA | Not Applicable | • Time-based media are not a part of Course Merchant |
| 1.2.8 | Media Alternative (Prerecorded) | AAA | Not Applicable | • Time-based media are not a part of Course Merchant |
| 1.2.9 | Audio-only (Live) | AAA | Not Applicable | • Time-based media are not a part of Course Merchant |
| 1.3.6 | Identify Purpose | AAA | Supports | Test Methods: MAT: Inspection Features • Icons are labeled so that users can perceive the functionality of each icon. • ARIA landmarks are used to mark different regions in a page. This information is available to screen readers for conveying to users who cannot see the screen. |
| 1.4.6 | Contrast (Enhanced) | AAA | Supports | Test Methods: CCT Features • Our standard text elements in the design system have a contrast greater than 7:1 on a white background. |
| 1.4.7 | Low or No Background Audio | AAA | Supports | • Course Merchant does not use any audio background. |
| 1.4.8 | Visual Presentation | AAA | Supports | Test Methods: MAT: Inspection Features • Course Merchant is compatible with most popular browser extensions to allow users to set their choice of foreground/background colors and text spacing. • Icons and text resize with the scaling/zooming options of browser (and other technology up to 200%.) • Most pages have relative column widths. • System text does not use full justification. • System font sizes are adjustable. |
| 1.4.9 | Images of Text (No Exception) | AAA | Supports | Test Methods: MAT: Inspection Features • Images of text are not used. |
| 2.1.3 | Keyboard (No Exception) | AAA | Supports | • All controls are reachable using the keyboard. Alternative ways are provided to accomplish tasks in situations where a tool is not optimal for one modality. |
| 2.2.3 | No Timing | AAA | Partially Supports | Test Methods: MAT: Inspection Features • The store follows the browser-controlled timeout period. Exception |
| 2.2.4 | Interruptions | AAA | Supports | Test Methods: MAT: Inspection Features • No interruptions are used in Course Merchant |
| 2.2.5 | Re-authenticating | AAA | Supports | Test Methods: MAT: Inspection Features • Users are prompted to reauthenticate after a session expires. Upon logging back in, the user lands at the same spot and can or cannot access what was previously available depending on the context and type of data. |
| 2.2.6 | Timeouts | AAA | Partially Supports | Test Methods: MAT: Inspection Features • Unsaved data is mostly retrievable after session expiry but there could be exceptions depending on the system. • The store follows the browser-controlled timeout period. Exception • Cart and user sessions have a time out, but there is no warning on when a session will time out. |
| 2.3.2 | Three Flashes | AAA | Supports | Test Methods: MAT: Inspection Features • No flashing content in the system. |
| 2.3.3 | Animation from Interactions | AAA | Supports | Test Methods: MAT: Inspection Features • If a user sets ‘reduced motion’ accessibility setting at the operating system level, then the software respects it. • No non-essential animation is used. • Nonvisual cues such as ARIA alerts are also available. |
| 2.4.8 | Location | AAA | Supports | Test Methods: MAT: Inspection Features • Breadcrumb trails are used to inform users of their current location. |
| 2.4.9 | Link Purpose (Link Only) | AAA | Supports | Test Methods: MAT: Inspection Features • All links have associated text that is unique and contextual, usually in the format [action] [applicable item]. |
| 2.4.10 | Section Headings | AAA | Supports | Test Methods: MAT: Inspection Features • Content and sections in a page are organized by a hierarchy of headings to enable screen reader users to meaningfully navigate and understand the content. • Titles, headings, ARIA landmarks and labels are used to organize system content. |
| 2.4.12 | Focus Not Obscured (Enhanced) | AAA | Supports | Test Methods: MAT: Inspection Features • No part of any focus indicator is obscured. |
| 2.4.13 | Focus Appearance | AAA | Supports | Test Methods: MAT: Inspection Features |
| 2.5.5 | Target Size | AAA | Supports | Test Methods: MAT: Inspection; UBT Features • Targets in key workflows are accessible to users with fine motor challenges. |
| 2.5.6 | Concurrent Input Mechanisms | AAA | Supports | Test Methods: MAT: Inspection Features • On account of meticulous alignment with the WCAG accessibility standards, our system interoperates well with standards-conforming assistive technologies. Further, our pages are designed to be responsive, meaning they adjust to the view port size of different devices used to access Course Merchant. Hence users can switch between interaction technologies and use content across devices seamlessly. |
| 3.1.3 | Unusual Words | AAA | Not Applicable | Test Methods: MAT: Inspection Features • No inline help is provided in Course Merchant |
| 3.1.4 | Abbreviations | AAA | Supports | Test Methods: MAT: Inspection Features • Abbreviations are avoided where possible and explained through inline help. |
| 3.1.5 | Reading Level | AAA | Supports | Test Methods: MAT: Inspection Features • Language in the system is aimed at lower secondary education level, |
| 3.1.6 | Pronunciation | AAA | Supports | Test Methods: MAT: Inspection Features • Users create their own content and related pronunciation symbols. |
| 3.2.5 | Change on Request | AAA | Supports | Test Methods: MAT: Inspection Features • No changes such as new content displaying in response to an action, or focus shifts, happen outside the control of the user. |
| 3.3.5 | Help | AAA | Supports | Test Methods: MAT: Inspection Features • Help links can be added to the navigation bar by request. |
| 3.3.6 | Error Prevention (All) | AAA | Supports | Test Methods: MAT: Inspection Features • Error prevention is implemented as meaningful in the context of Course Merchant • Submissions are checked for input error, and errors and opportunities for correction are clearly communicated to the user. |
| 3.3.9 | Accessible Authentication (Enhanced) | AAA | Supports | Test Methods: MAT: Inspection Features • Our platform does not use biometric technologies for authentication. |
| 4.2.1 | Usage without vision | - | Partially Supports | Supports when combined with Compatible Assistive Technology. Features • All interfaces are designed according to HTML5 standards. • Images and icons are assigned contextual and meaningful text alternatives that can be announced by a screen reader. • Images of text are not used in place of text. • Controls such as buttons are labeled to indicate their function. • Form fields are labeled to perceive their intent. • Links are assigned meaningful texts that clearly indicate the link destination. • Controls are assigned appropriate labels that allow perception of their function. • ARIA attributes are used to make alert messages and states of dynamic elements such as radio buttons perceivable. • Standard interface elements are made evident through proper HTML mark up. Exception • The number of courses returned by search results is updated on the screen but is not read by assistive technology. |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Supports when combined with Compatible Assistive Technology. Features |
| 4.2.3 | Usage without perception of colour | - | Supports | Features • Colour alone is not used to convey information. |
| 4.2.4 | Usage without hearing | - | Supports | Features • The platform does not use any auditory alerts. |
| 4.2.5 | Usage with limited hearing | - | Supports | Features • The platform does not use any auditory alerts. |
| 4.2.6 | Usage with no or limited vocal capability | - | Supports | Features • The platform does not require any vocal alerts. |
| 4.2.7 | Usage with limited manipulation or strength | - | Supports | Supports when combined with Compatible Assistive Technology. Features • Users with limited manipulation primarily use alternatives to pointing devices such as onscreen keyboards, voice recognition software, visual trackers or adaptive keyboards. For these users, access through keyboard, visibility of current tab location, large target size and longer time limits are important accessibility criteria. • Users can make their click target size larger if needed by controlling icon sizes through browser zoom preferences. |
| 4.2.8 | Usage with limited reach | - | Supports | Features • Large target sizes, adequate timeout times, and error-tolerant routines help reduce unintended or incomplete interactions. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | • No flashing content in the system. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Supports | Features • Simple language is used for text content. • Visual illustrations are used along with text. |
| 4.2.11 | Privacy | - | Supports | • Our platform does not use biometric technologies for authentication. • In the use of platform features, we maintain the privacy of users of assistive technologies at the same level as other users. • Examples: • Spoken version is not provided for characters being masked. • Users have control of their personal data. |
| 12.1.1 | Accessibility and compatibility features | - | Supports | • D2L provides extensive documentation including accessibility features on the accessible D2L Brightspace Community website https://community.d2l.com/brightspace. |
| 12.2.2 | Information on accessibility and compatibility features | - | Supports | • A statement of D2L’s accessibility is made prominently at https://www.d2l.com/accessibility/. All information about D2L’s accessibility support, which includes information on the accessibility and compatibility features that are built-in and accessibility features that provide compatibility with assistive technology supporting our products, is available on D2L’s |
| 12.2.3 | Effective communication | - | Supports | • Accessible support services are provided via phone, email and through accessible documentation, as required. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated January 1, 2026. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.