Loyola Marymount University and the CORA team are committed to ensuring digital accessibility for people with disabilities. We are continually working to improve the user experience for everyone and to apply relevant accessibility standards as part of our ongoing platform upgrade.
Measures to support accessibility
CORA takes the following measures to support accessibility:
- We treat accessibility as a core consideration in our platform redesign.
- We include accessible design elements and aim to align with recognized accessibility standards (WCAG 2.2 Level AA).
- We include accessible elements in the design and development of new features.
- We provide contributors with accessibility best-practice guidance, including an instructional design rubric that incorporates Universal Design for Learning principles.
Conformance status
The Web Content Accessibility Guidelines (WCAG) define requirements for improving accessibility for people with disabilities, across three levels of conformance: Level A, Level AA, and Level AAA.
As part of our ongoing platform upgrade, we are working to align CORA with WCAG 2.2 Level AA standards across the site's core features. We plan to conduct a comprehensive accessibility audit during the final stages of the upgrade, and we will update this statement to reflect a realistic conformance level once that audit is complete. While we strive to meet these standards, we cannot guarantee that every part of the site or all user-contributed content will fully conform at all times.
Compatibility with browsers and assistive technology
CORA is designed to be compatible with modern versions of major web browsers, including Chrome, Firefox, Safari, and Edge, on Windows, macOS, iOS, and Android.
It is designed to work with common assistive technologies. These include Narrator, the screen reader built into Windows, as well as third-party screen readers such as NVDA and JAWS, and VoiceOver on macOS and iOS.
CORA may not display or function optimally in older or unsupported browsers.
Technical specifications
Accessibility of CORA relies on the following technologies to work with your particular combination of web browser and any assistive technologies installed on your device:
- HTML
- CSS
- JavaScript
- WAI-ARIA
These technologies are relied upon for conformance. If any is not supported or is turned off (for example, if JavaScript is disabled in your browser), some parts of CORA may not be accessible or function as intended.
Known limitations
Despite our efforts, there may be some limitations. Below is a description of known limitations. Please contact us if you observe an issue not listed here.
User-contributed lesson plans and files.
Lesson plans and files uploaded by contributors (PDFs, Word documents, presentations, and similar) may not fully meet accessibility standards—for example, a PDF may lack proper tags or text alternatives. This occurs because CORA hosts materials created by a community of contributors using varying tools and practices, and we cannot guarantee the accessibility of every individual file. We provide contributors with best-practice guidance to encourage accessible submissions. If you encounter an inaccessible file, please contact us and we will work to provide an accessible alternative or help you access the content.
User comments and community contributions.
Comments and other text submitted by users may occasionally contain formatting or content that is not fully accessible, because this content is created by community members. We review community content where we can. Please report any barriers using the contact information below.
Feedback
We welcome your feedback on the accessibility of CORA. If you encounter accessibility barriers, please let us know:
Email: susan.archambault@lmu.edu
We aim to respond to accessibility feedback within 5 business days.
Assessment approach
CORA assesses accessibility through a combination of self-evaluation and testing. As part of the platform upgrade, we plan to test the site using the WAVE Web Accessibility Evaluation Tool for automated and manual checks, along with manual testing using screen readers including NVDA, Narrator, and VoiceOver. We will update this statement to reflect the results once testing is complete.
Date
This statement was last updated on August 29, 2026. It follows the W3C Web Accessibility Initiative's recommended format.