MyDesign Accessibility Conformance Report - Section 508 Edition
Download this report as a PDF.
Based on VPAT® 2.5Rev
- Name of Product: MyDesign® Learning Management System
- Report Date: August 18, 2026
- Product Description: MyDesign® is a web-based Learning Management System supporting the Engineering for US All (e4usa). It is used by Teachers, Students, and Administrators to manage classes, projects, grading, portfolios, and scoring administration. MyDesign® can integrate with other learning management systems such as Canvas, Schoology, and Blackboard.
- Contact information: info@e4usa.org
- Notes:
- This evaluation refers only to the MyDesign® Learning Management System and does not include any associated websites or documentation.
- This report evaluates the accessibility conformance of the latest release of MyDesign®, as we are always testing with the most current version.
- Table 3: Success Criteria, Level AAA has been removed because the MyDesign® product has not been evaluated for WCAG 2.1 Level AAA conformance.
- Chapter 4: Hardware has been removed because MyDesign® is a web application and is not subject to the requirements of this section.
- MyDesign® supports all modern browsers (e.g., Chrome, Firefox, Safari, Edge).
- MyDesign® does not support running with JavaScript disabled in the browser because the front-end is built exclusively using modern JavaScript frameworks.
- Any device with an internet browser and at least 1024 x 768 screen resolution should be capable of accessing and using MyDesign®.
- Known accessibility issues are detailed in the tables below.
- Evaluation Methods Used: Conformance to the listed accessibility standards has been evaluated by Engineering for US All using a combination of automated analysis tools and manual testing. These tools include, but are not limited to: Chrome DevTools, WAVE, and VoiceOver.
Applicable Standards/Guidelines
| Standard/Guideline | Included 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) |
| Revised Section 508 standards - published January 18, 2017 and corrected January 22, 2018 | (Yes) |
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.x Level AAA, or in the not-required parts of a report.
WCAG 2.1 Report
Tables 1 and 2 also document conformance with Revised Section 508:
- Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
- Chapter 6 – 602.3 Electronic Support Documentation
Section 508 incorporates WCAG 2.0 Level A/AA by reference. This report evaluates against WCAG 2.1, a superset that includes all WCAG 2.0 criteria unchanged, so conformance with WCAG 2.1 also satisfies the WCAG 2.0 requirement referenced by Section 508. 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.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | A few icon-only buttons and images could benefit from added accessible names. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Supports | No default audio-only or video-only content; user-uploaded content is the user's responsibility. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No default prerecorded audio or video content. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No default prerecorded video content. |
| 1.3.1 Info and Relationships | Partially Supports | Testing identified a few opportunities for improvement, including some ARIA references, empty table headers, and a skipped heading level. |
| 1.3.2 Meaningful Sequence | Partially Supports | In a few dialogs, the Submit/Cancel buttons appear before the form fields, and some filter panels are positioned later in the page structure than their trigger button. |
| 1.3.3 Sensory Characteristics | Supports | Does not rely on shape, size, position, or sound alone to convey information. |
| 1.4.1 Use of Color | Supports | Color is not the only means of conveying information. |
| 1.4.2 Audio Control | Not Applicable | No default auto-playing audio. |
| 2.1.1 Keyboard | Does Not Support | Four controls are not operable via keyboard alone: Class Home/Project sidebar navigation, the Manage Projects card-expand control, file-type resources in My Resources, and the My Portfolio download icon. A fix is planned for an upcoming release, and an interim URL-based workaround is available in the meantime. A few other keyboard interactions (e.g., the element-selection rubric wheel, filter-clear icons) have room for improvement but do not prevent the underlying task from being completed. VoiceOver Note: VoiceOver users can work around all of these using VoiceOver's own commands; keyboard-only users without a screen reader cannot, with one exception: the download icon issue is not reachable with VoiceOver. |
| 2.1.2 No Keyboard Trap | Partially Supports | This applies to a single, isolated third-party component (the Google Drive file picker), which does not yet exit via standard keyboard methods (Tab/Esc). It can be avoided by using local file upload instead, and refreshing the page provides a way out. VoiceOver Note: This can be closed using VoiceOver's own commands. |
| 2.1.4 Character Key Shortcuts | Supports | The only reserved single-character shortcut is Esc, used for its standard function. |
| 2.2.1 Timing Adjustable | Supports | No default timeouts; user-set time limits (e.g., due dates) are adjustable by teachers. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | No moving, blinking, or auto-updating content by default. |
| 2.3.1 Three Flashes or Below Threshold | Not Applicable | No flashing content. |
| 2.4.1 Bypass Blocks | Does Not Support | A skip-navigation link and a way to bypass long tables or lists (Grading Overview, User Management, Assign Students) are not available. |
| 2.4.2 Page Titled | Supports | All pages have descriptive titles. |
| 2.4.3 Focus Order | Partially Supports | In several dialogs and filter panels (Grading Overview, User Management, Class Roster), focus order could be more intuitive; users can still reach the intended control using Shift+Tab or continued tabbing. |
| 2.4.4 Link Purpose (In Context) | Partially Supports | A few icon-only buttons and links have no accessible names. |
| 2.5.1 Pointer Gestures | Supports | No multipoint or path-based gesture functionality. |
| 2.5.2 Pointer Cancellation | Supports | Interactive elements trigger on the up-event. |
| 2.5.3 Label in Name | Supports | Accessible names match visible labels. |
| 2.5.4 Motion Actuation | Not Applicable | No motion-operated functionality. |
| 3.1.1 Language of Page | Supports | Primary language is English, and it is defined programmatically. |
| 3.2.1 On Focus | Supports | Focus does not trigger unexpected changes of context. |
| 3.2.2 On Input | Supports | Changing an input's value does not trigger unexpected changes of context. |
| 3.3.1 Error Identification | Supports | Form errors are identified and described; submission is blocked until resolved. |
| 3.3.2 Labels or Instructions | Partially Supports | Testing identified missing or orphaned form labels in a few dialogs. |
| 4.1.1 Parsing | Supports | The framework produces well-formed markup; this criterion is effectively obsolete per the WCAG 2.1 errata. |
| 4.1.2 Name, Role, Value | Partially Supports | Testing identified a few broken ARIA references and empty buttons. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No default live audio or video content. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No default prerecorded audio content. |
| 1.3.4 Orientation | Supports | Not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose | Supports | Input field purposes can be programmatically determined. |
| 1.4.3 Contrast (Minimum) | Partially Supports | A few text instances have low contrast. VoiceOver Note: Separately, the currently focused element is displayed with VoiceOver's own high-contrast indicator, regardless of the page's styling. |
| 1.4.4 Resize text | Supports | Text resizes to 200% without loss of content or functionality. |
| 1.4.5 Images of Text | Supports | Plain text is used rather than images of text. |
| 1.4.10 Reflow | Supports | Responsive design supports 320px width / 400% zoom without loss of content or two-dimensional scrolling. |
| 1.4.11 Non-text Contrast | Partially Supports | Focus indicators on the top navigation bar and the Manage Teams button have low contrast against their background. VoiceOver Note: VoiceOver draws its own high-contrast focus indicator on top of the page, so VoiceOver users can clearly see focus despite this contrast issue. |
| 1.4.12 Text Spacing | Supports | Text spacing can be adjusted without loss of content or functionality. |
| 1.4.13 Content on Hover or Focus | Supports | Hover/focus-triggered content is dismissible, hoverable, and persistent. |
| 2.4.5 Multiple Ways | Does Not Support | Currently, sequential navigation is the primary way to move through the product; additional options such as search or a sitemap are not available. |
| 2.4.6 Headings and Labels | Partially Supports | A few labels are not clearly associated with their fields, and one heading level was skipped. |
| 2.4.7 Focus Visible | Partially Supports | Focus indicators on navigation and a few other components are missing or low-contrast. VoiceOver Note: VoiceOver draws its own focus indicator regardless of the page's styling, so VoiceOver users are not affected by this issue. |
| 3.1.2 Language of Parts | Supports | Content is in English; user-uploaded or linked content is the user's responsibility. |
| 3.2.3 Consistent Navigation | Supports | Navigation patterns are consistent throughout. |
| 3.2.4 Consistent Identification | Supports | Components with the same function are labeled and behave consistently. |
| 3.3.3 Error Suggestion | Supports | Suggestions are provided for certain inputs (e.g., password, email). |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | No legal or financial data is collected. |
| 4.1.3 Status Messages | Supports | Visual confirmation messages appear for successful or failed submissions. |
Table 3: Success Criteria, Level AAA
Level AAA Success Criteria were not evaluated as part of this assessment.
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | Most content is compatible with screen readers; however, testing identified interactive elements and images not fully accessible via keyboard (see WCAG 2.1 Report, 2.1.1 Keyboard and 1.1.1 Non-text Content). |
| 302.2 With Limited Vision | Partially Supports | Text resizes without loss of function, but testing identified contrast issues on some text and on certain focus indicators (see WCAG 2.1 Report, 1.4.3 Contrast (Minimum) and 1.4.11 Non-text Contrast). |
| 302.3 Without Perception of Color | Supports | MyDesign® does not require color perception for operation. |
| 302.4 Without Hearing | Supports | MyDesign® does not use audio for its operation. Users are responsible for ensuring accessibility of content they upload or link to. |
| 302.5 With Limited Hearing | Supports | MyDesign® does not use audio for its operation. Users are responsible for ensuring accessibility of content they upload or link to. |
| 302.6 Without Speech | Supports | MyDesign® does not require speech for its operation. |
| 302.7 With Limited Manipulation | Partially Supports | MyDesign® does not require fine motor control or simultaneous actions; however, testing identified several controls not operable via keyboard alone (see WCAG 2.1 Report, 2.1.1 Keyboard). |
| 302.8 With Limited Reach and Strength | Partially Supports | MyDesign® does not require sustained physical input or force; however, testing identified several controls not operable via keyboard alone (see WCAG 2.1 Report, 2.1.1 Keyboard). |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | MyDesign® uses simple, clear, consistent language and navigation, and provides clear error messages and correction suggestions. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope — Incorporation of WCAG 2.1 AA | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502 Interoperability with Assistive Technology | Heading cell — no response required | Heading cell — no response required |
| 502.2.1 User Control of Accessibility Features | Not Applicable | This criterion is not relevant because the product is not platform software. |
| 502.2.2 No Disruption of Accessibility Features | Supports | The product is compatible with operating system and browser accessibility features configured by the user. |
| 502.3 Accessibility Services | Heading cell — no response required | Heading cell — no response required |
| 502.3.1 Object Information | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.2 Modification of Object Information | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.3 Row, Column, and Headers | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.4 Values | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.5 Modification of Values | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.6 Label Relationships | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.7 Hierarchical Relationships | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.8 Text | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.9 Modification of Text | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.10 List of Actions | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.11 Actions on Objects | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.12 Focus Cursor | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.13 Modification of Focus Cursor | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.3.14 Event Notification | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 502.4 Platform Accessibility Features | Not Applicable | This criterion is not relevant because the product is not a platform. |
| 503 Applications | Heading cell — no response required | Heading cell — no response required |
| 503.2 User Preferences | Not Applicable | This criterion is not relevant because the product is isolated from the underlying platform. |
| 503.3 Alternative User Interfaces | Not Applicable | This criterion is not relevant because the product does not have assistive technology features. |
| 503.4 User Controls for Captions and Audio Description | Heading cell — no response required | Heading cell — no response required |
| 503.4.1 Caption Controls | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 503.4.2 Audio Description Controls | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 504 Authoring Tools | Heading cell — no response required | Heading cell — no response required |
| 504.2 Content Creation or Editing | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not Applicable | This criterion is not relevant because the product does not support file conversion or saving to multiple formats. |
| 504.2.2 PDF Export | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 504.3 Prompts | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 504.4 Templates | Not Applicable | This criterion is not relevant because the product does not support templates. |
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 | Supports | The product documentation describes shortcut keys and workarounds. |
| 602.3 Electronic Support Documentation | See WCAG 2.1 tables | See information in the WCAG 2.1 Report earlier in this document. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | This criterion is not applicable because the product documentation is in electronic format. |
| 603 Support Services | Heading cell — no response required | Heading cell — no response required |
| 603.2 Information on Accessibility and Compatibility Features | Supports | MyDesign® Support can provide information about accessibility features of the product. |
| 603.3 Accommodation of Communication Needs | Supports | MyDesign® customers have access to electronic support. Engineering for US All will provide support in any manner to accommodate the needs of users with disabilities. |
Engineering for US All Legal Disclaimer
This document is provided for information purposes only and the contents hereof are subject to change without notice. Engineering for US All does not warrant that this document is error-free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Engineering for US All specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Engineering for US All further makes no representation concerning the ability of assistive technologies or other products to interoperate with Engineering for US All products. This document addresses the named product(s) only.