Lumi Pro For Brightspace
Accessibility Conformance Report published by D2L
Partial extraction. We read 0 of 31 Level A and 24 of 24 Level AA criteria from this document (44% 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 AA — 24 criteria
- Supports
- 17
- Partially supports
- 3
- Does not support
- 0
- Not applicable
- 4
- Not evaluated
- 0
Level AAA — 31 criteria
- Supports
- 27
- Partially supports
- 0
- Does not support
- 0
- Not applicable
- 4
- 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 (69)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.2.4 | Captions (Live) | AA | Not Applicable | • Time-based media are not a part of D2L Lumi Pro. • Users control the content they produce. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | • Time-based media are not a part of D2L Lumi Pro for Brightspace. • Users control the content they produce. |
| 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 | Not Applicable | • Users’ personal information is not collected by nor used by D2L Lumi Pro for Brightspace. |
| 1.4.3 | Contrast (Minimum) | AA | Supports | Test Methods: TBT; CCT; SMT; UBT Features • Foreground to background contrast adheres to standards including with the AI banner and its gradient • Users control their own content. |
| 1.4.4 | Resize text | AA | Supports | Test Methods: TBT; SMT; UBT Features • User account settings are available for adjusting font face and size. • Icons and text resize with scaling/zooming options of browser (and other technology) up to 200%. • All product functionalities perform well at this zoom level. • Users control their own content. |
| 1.4.5 | Images of Text | AA | Supports | Test Methods: MAT; SRT Features • Images of text are not used. • Equations authored in D2L’s Equation Editor are stored as MathML and output as MathML in browsers where supported. • Users control their own content. |
| 1.4.10 | Reflow | AA | Partially Supports | Test Methods: TBT; MAT; UBT Features • D2L Lumi Pro for Brightspace is built with responsive design and reflow in mind based on our Daylight Design System. • Pages mostly reflow when the viewport is set to smaller phone sizes. Exception • When using D2L Lumi Content, the dialog “What Does the AI Do with My Content” isn’t fully responsive at certain browser screen widths. |
| 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 • D2L Lumi Pro for Brightspace is built with responsive design and reflow in mind based on our Daylight 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 • Custom tooltips and edit nav bar links that appear on hover or focus are visible until dismissed and can be dismissed without moving pointer hover or keyboard focus. |
| 2.4.5 | Multiple Ways | AA | Supports | Test Methods: MAT: Inspection; UBT Features |
| 2.4.6 | Headings and Labels | AA | Supports | Test Methods: MAT: Inspection; UBT Features • Pages have descriptive headings and labels. Labels are unique and contextual. • Users control their own content. |
| 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. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Supports | Test Methods: Inspection Features: • Focus indicators are not obscured. |
| 2.5.7 | Dragging Movements | AA | Supports | Test Methods: SRT; UBT Features: • Workflows that require drag-and-drop with a mouse can also be completed using a keyboard. |
| 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 | Supports | Test Methods: TBT: Language bookmarklet Features • While the WSYIWYG editor does not include a button or prompt users to indicate a “lang” attribute for language changes, users can insert a “lang” attribute using the HTML source editor. • Users control their own content. |
| 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 • Icons use an icon grammar to facilitate learning. • The same icon is used for the same action across all tools. • Users may combine concepts they already understand to interpret new icons. |
| 3.3.3 | Error Suggestion | AA | 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 and link to the appropriate field for resolving the error. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | • D2L Lumi Pro for Brightspace does not involve legal commitments or financial transactions for the user. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Test Methods: MAT: Inspection Features: • D2L Lumi Pro for Brightspace does not use biometric technologies for authentication. |
| 4.1.3 | Status Messages | AA | Partially Supports | Test Methods: TBT; MAT; UBT Features • Users are made aware of important changes in content that are not given focus through inline or toast alerts. These alerts do not interrupt users’ work. • Screen reader users get audio alerts. Exception • Status messages are not relayed during Lumi Content generation workflows. |
| 1.2.6 | Sign Language (Prerecorded) | AAA | Not Applicable | • Time-based media are not a part of D2L Lumi Pro for Brightspace. • Users control the content they produce. |
| 1.2.7 | Extended Audio Description (Prerecorded) | AAA | Not Applicable | • Time-based media are not a part of D2L Lumi Pro for Brightspace. • Users control the content they produce. |
| 1.2.8 | Media Alternative (Prerecorded) | AAA | Not Applicable | • Time-based media are not a part of D2L Lumi Pro for Brightspace. • Users control the content they produce. |
| 1.2.9 | Audio-only (Live) | AAA | Not Applicable | • Time-based media are not a part of D2L Lumi Pro for Brightspace. • Users control the content they produce. |
| 1.3.6 | Identify Purpose | AAA | Supports | Test Methods: MAT: Inspection Features: • All icons are labeled so that users can perceive the functionality of each icon. Example: The envelope icon is labeled “Message alerts” (and not Envelope). • 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 Brightspace Daylight design system have a contrast greater than 7:1 on a white background. • Users control their own content. |
| 1.4.7 | Low or No Background Audio | AAA | Supports | • Brightspace does not use any audio background. • Users control the content they produce. |
| 1.4.8 | Visual Presentation | AAA | Supports | Test Methods: MAT: Inspection Features: |
| 1.4.9 | Images of Text (No Exception) | AAA | Supports | Test Methods: MAT: Inspection Features: • Images of text are not used. • Users control their own content. |
| 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 | Supports | Test Methods: MAT: Inspection Features: • The Quizzes tool supports time-based assessments with the ability to define alternative access, such as alternative timing or no time, for users as needed. • Institutions have an option to set a time-out period. Users are warned before their session times-out. |
| 2.2.4 | Interruptions | AAA | Supports | Test Methods: MAT: Inspection Features: • Interruptions are designed only if and when applicable and meaningful to the activity in hand. • The system uses ARIA alerts to indicate dynamic page changes so that users can choose the level of interruption they want. • Users control their own content. |
| 2.2.5 | Re-authenticating | AAA | Supports | Test Methods: MAT: Inspection Features: • Users are prompted to reauthenticate before 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 | Supports | Test Methods: MAT: Inspection Features: • Controlled timeouts are implemented for timed assessments which allow auto-submission of quiz data at pre-determined time limits. • Time limits are communicated to learners at the start of the assessment. • Unsaved data is mostly retrievable after session expiry but there could be exceptions depending on the system. |
| 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. • Essential animations are used sparingly in contexts where it would be helpful to some users. For example, subtle communication about the state of the page (such as loading indicators) or to help indicate where an item was placed on or removed from a page (such as an animation showing items reordering or being added to the bottom of a page. • Nonvisual cues such as ARIA alerts are also available. |
| 2.4.8 | Location | AAA | Supports | Test Methods: MAT: Inspection Features: • Breadcrumb trails or ‘Back to’ buttons are used to inform users of their current location. • Users control their own content. |
| 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: |
| 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: • Focus indicator is at least equal to 2 CSS pixel thick perimeter. |
| 2.5.5 | Target Size | AAA | Supports | Test Methods: MAT: Inspection; UBT Features: • While not all our targets are 44x44 CSS pixels in size, we have ensured through user testing that 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 |
| 3.1.3 | Unusual Words | AAA | Supports | Test Methods: MAT: Inspection Features: • Inline help is provided as needed. • All D2L Lumi Pro for Brightspace capabilities allow institutions to override terms and use their own words. |
| 3.1.4 | Abbreviations | AAA | Supports | Test Methods: MAT: Inspection Features: • Abbreviations are avoided where possible and explained through inline help. • All D2L Lumi Pro for Brightspace capabilities allow institutions to override terms and use their own words. |
| 3.1.5 | Reading Level | AAA | Supports | Test Methods: MAT: Inspection Features: • Language in the system is aimed at lower secondary education level, especially for participant focused tools. • Inline help is provided as necessary. • Institutions may build their own language pack. |
| 3.1.6 | Pronunciation | AAA | Supports | Test Methods: MAT: Inspection Features • Users create their own content and related pronunciation symbols. • All D2L Lumi Pro for Brightspace capabilities allow institutions to override terms and use their own words. |
| 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, |
| 3.3.5 | Help | AAA | Supports | Test Methods: MAT: Inspection Features: • Tooltips and descriptions are provided as needed for submitting information. • Inline help is provided as needed. • Additional context about what the AI is doing and how it works is provided in the AI banner that appears at the top of each workflow. |
| 3.3.6 | Error Prevention (All) | AAA | Supports | Test Methods: MAT: Inspection Features: • Error prevention is implemented as meaningful in the context of an LMS. • Submissions are checked for input error, and errors and opportunities for correction are clearly communicated to the user. • Where error prevention is critical, such as when submitting answer to a quiz question, the user is given an option to confirm. This provision is used sparingly and only where required, so as to maintain an agile user experience. Not all actions are reversible. |
| 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. • Math equation coded in MathML can be read by the screen reader subject to browser compatibility. Exceptions • Focus is placed at top of screen instead of the next logical element in D2L Lumi Outcomes, D2L Lumi Content, and D2L Lumi Insights. |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Supports when combined with Compatible Assistive Technology. Features • All product functionalities perform well at 200% zoom level. • All pages are designed to wrap well when zoomed to 200%. • User account settings are available for adjusting font size. • Icons and text resize with browser (and other technology) scaling/zooming options. • Most pages have relative column widths. • System text does not use full justification. • Colour contrast of foreground text with background is maintained according to standard specifications. • SVG images are used to prevent pixelation upon magnification. Exceptions • When using D2L Lumi Content, the dialog “What Does the AI Do with My Content” isn’t fully responsive at certain browser screen widths. |
| 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 | - | Partially Supports | Supports when combined with Compatible Assistive Technology. Features |
| 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. • Users control their own content. |
| 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. • Interface navigation is made simple through use of hierarchical headings. |
| 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 public website https://community.d2l.com/brightspace. |
| 12.2.3 | Effective communication | - | Supports | • Accessible support services are provided via phone, email and through accessible documentation, as required. We support end user TTY Relay service. The direct number is |
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.