Accessibility Statement
Our commitment
PreMD is built for every student on the path to medicine, including students with disabilities. We are committed to providing a platform that is perceivable, operable, understandable, and robust, and we treat accessibility as part of the engineering standard of the Service rather than an afterthought.
Conformance target
The Service is being designed toward the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. This is a target, not a claim that every page currently conforms. Conformance work and assistive-technology testing are ongoing; we prioritize fixes that affect core tasks such as study planning, record entry, contribution review, withdrawal, and data export.
Accessibility work currently in place
- These public policy pages provide a visible-on-focus skip link, semantic header/main/footer landmarks, a single page heading, and clear link focus indicators.
- The application provides keyboard access for core navigation and native form controls, including a keyboard command palette (Ctrl/⌘ K). Dialog, menu, and complex-widget focus behavior is part of the ongoing audit.
- Dedicated visible focus indicators are present on the public policy pages and core application controls; consistency across every custom widget is still being audited.
- Native buttons and form controls are preferred; label association, dialog semantics, menus, tabs, and route-heading focus are being audited component by component.
- Community-outcome maps have an equivalent state selector, and charts include nearby summaries or table alternatives. Equivalent keyboard and screen-reader exploration for every dense visualization remains an ongoing test area.
- Light and dark themes use text labels in addition to color for important status. Contrast and small chart labels remain part of automated and manual review.
- Respect for the operating system's reduced-motion preference; animation in the Service is minimal by design.
- Responsive layouts and heading hierarchy are tested as the interface evolves; zoom, reflow, and text-spacing checks are not yet complete for every screen.
Known limitations
Some data-dense charts still rely on adjacent summaries rather than complete non-visual interaction; some complex grids need more consistent arrow-key behavior; and third-party resources and security challenges are outside our direct control. We are continuing keyboard, screen-reader, contrast, zoom/reflow, and mobile-navigation testing. You never need to contribute community data or use an external AI provider to access PreMD's core planning features.
Accommodations and requests
If any part of the Service is difficult or impossible for you to use with assistive technology, or if you need your records or content in an alternative format, contact us at contact@premd.org with the subject line "Accessibility." Please describe the page or task and, only if you are comfortable doing so, the browser and assistive technology in use. We prioritize reports that block core tasks; we will publish a response-time commitment after the support role is formally staffed.
Feedback
Accessibility feedback can also be submitted from the Feedback section inside the platform. Reports of this kind are reviewed directly by the team responsible for the interface.