Accessibility
ChatCME is committed to an inclusive, usable experience for everyone. We design, build, and test against the Web Content Accessibility Guidelines (WCAG) with a conformance target of WCAG 2.1 AA and ongoing work toward 2.2. Accessibility is a continuous process. We review new features, fix issues that are found in use, and welcome feedback.
Scope of this statement
This page covers the accessibility of the following ChatCME products and surfaces:
- •Embedded Assistant used by HCPs inside accredited CME activities. See assistant features
- •Admin Console used by accredited CME providers. See Admin Console
- •Analytics Dashboards for outcomes and insights. View analytics
- •Kiosk mode deployments for conferences and events
- •Public website content on chatcme.com
ChatCME frequently embeds inside customer websites and apps. While the ChatCME widget is built to be accessible, overall page accessibility also depends on the host site (structure, color contrast, focus order, and other factors that we do not control).
Standards and commitments
- •
WCAG: We design and test to WCAG 2.1 Level AA and track new 2.2 criteria.
- •
WAI-ARIA: We use ARIA roles, properties, and live regions only where needed to enhance native HTML semantics.
- •
Inclusive design: Keyboard-first navigation, screen reader support, color-contrast compliance, motion and flashing controls, and readable language.
- •
Localization: Interface and answers available in 50+ languages, with support for right-to-left scripts and locale-aware dates, numbers, and punctuation. See language support.
- •
Privacy and safety: Accessibility features never require personal health information.
A VPAT (Accessibility Conformance Report) is available on request.
What users can expect
Keyboard accessibility
- •Every interactive element is reachable by Tab and Shift+Tab, with visible focus indicators.
- •Enter activates buttons and primary actions.
- •Space toggles checkboxes, switches, and expandable controls.
- •Esc closes dialogs and popovers such as citation panels.
- •Multi-step workflows never trap focus.
- •Long pages and modals include skip links to jump to the main content.
Screen reader and semantics
- •Logical headings and landmarks for navigation.
- •ARIA live regions announce streaming responses and status messages without interrupting user tasks.
- •Dialogs and menus include correct roles, labels, and descriptions.
- •Form controls have programmatic labels, instructions, and error messages that are read aloud.
Color, contrast, and motion
- •Default themes meet contrast ratios of at least 4.5:1 for body text and 3:1 for large text and UI components.
- •ChatCME does not rely on color alone to convey meaning.
- •We honor user preferences for reduced motion and high contrast where supported by the OS or browser.
- •Touch targets are at least 44×44 px and layouts reflow cleanly down to mobile widths without loss of information.
Zoom, reflow, and orientation
- •Pages and components support zoom up to 400% without loss of content or functionality.
- •Layouts support both portrait and landscape orientation.
Product-specific notes
Embedded Assistant (HCP experience)
- •Semantic HTML with ARIA enhancement for streaming chat.
- •Citations open in accessible panels and include the referenced slide number or timestamp.
- •Keyboard-only users can open, read, copy, and follow citations.
- •Language support: content can be ingested in 50+ languages and answers can be presented in 50+ languages.
- •Cognitive support: concise responses, optional summaries, and consistent controls.
- •Error handling: clear messages and suggestions, announced to assistive technologies.
- •No time limits in normal use. If a session timeout is configured by the host site, users see a warning with a way to extend.
Admin Console (for accredited CME providers)
- •Cognitive support: concise responses, optional summaries, and consistent controls.
- •Error handling: clear messages and suggestions, announced to assistive technologies.
- •No time limits in normal use. If a session timeout is configured by the host site, users see a warning with a way to extend.
Admin Console (for accredited CME providers)
- •Forms have labels, instructions, inline validation, and accessible error summaries.
- •Tables and grids support keyboard navigation and screen reader announcements of column headers and sort state.
- •Editorial AI tools (Program Description and Seed Questions) include accessible preview panes.
- •Color is not the only way to show status or review states.
Analytics Dashboards
- •Charts include text alternatives and downloadable data tables (CSV/Excel).
- •Legends and filters are reachable by keyboard and announced by screen readers.
- •Large visualizations have accessible summaries that convey the key message.
Kiosk mode (conferences and events)
- •Large, high-contrast controls suitable for public spaces.
- •Screen reader and keyboard interaction work with supported browsers on managed devices.
- •Optional on-screen keyboard depends on device OS settings.
- •Staff should provide a headset or a quiet area for users who rely on audio feedback.
Media, documents, and third-party content
- •
Videos and audio
If source media includes captions, the ChatCME interface preserves and exposes them. When transcripts are available, the Assistant links to them. Captions for customer-supplied media are controlled by the customer; we encourage accredited providers to include captions for all instructional media.
- •
PDFs and downloads
Our generated PDFs (such as Outcomes Packs) are created with tagged structure, correct reading order, document titles, and alt text for informative images where feasible.
- •
Customer-provided slides and documents
Accessibility of third-party content (alt text, reading order, contrast, table headers) is the responsibility of the content owner. ChatCME provides guidance and validation tips to help providers meet accessibility standards.
Supported platforms and assistive technologies
We test on modern browsers and assistive technologies. Examples include:
- •Desktop: Chrome, Edge, Firefox, and Safari on current releases
- •Screen readers: NVDA, JAWS, VoiceOver
- •Mobile: iOS Safari with VoiceOver, Android Chrome with TalkBack
Not all combinations are exhaustively tested. If you encounter a conflict in your environment, let us know and we will investigate.
Implementation checklist for customers
When embedding ChatCME on your site, these practices help maintain accessibility:
- •Provide an accessible container: semantic landmarks, headings, and consistent navigation.
- •Keep color contrast and font sizes in line with WCAG.
- •Avoid keyboard traps in surrounding components such as sticky headers or custom modals.
- •Ensure any SSO flows are keyboard and screen-reader accessible.
- •For media, provide captions and descriptive text where applicable.
- •Use alt text for informative images in your pages and content.
We offer a short embed checklist and can review an example page on request.
Continuous testing and improvement
Our process includes:
- •Automated checks for common issues
- •Manual keyboard-only and screen reader passes
- •Zoom and reflow testing down to small mobile breakpoints
- •Contrast testing across light and dark themes
- •Localization QA in left-to-right and right-to-left languages
Accessibility issues found by users or internal audits are prioritized in our defect triage.
Feedback, requests, and contact
If you experience an accessibility barrier or need content in an alternative format, please contact us:
- •Email: support@erudio.com
- •Subject line: Accessibility
- •Include the page or feature, your browser and assistive tech (if applicable), and a brief description of the issue.
We review all reports and work to resolve confirmed issues. If you prefer, we can provide large-print, plain-text, or tagged PDF versions of key materials.
Known limitations
We are actively improving the following areas:
- •Additional keyboard shortcuts documentation within the Assistant
- •More descriptive summaries for complex charts
- •Expanded testing on older mobile devices
If any of these affect your use, please reach out so we can suggest a workaround.