Our Commitment
ChartScribe is committed to making our websites (chartscribe.io and chartscribe.care) accessible to everyone, including people with disabilities. We have implemented WCAG 2.2 AA standards, including skip links, strong focus indicators, and high-contrast mode support. We follow NHS digital service guidance and aim for full AA + selected AAA conformance by Q4 2026.
Recent Improvements
- Skip-to-main-content link for keyboard users (WCAG 2.4.1)
- Clear focus styles on all interactive elements — 4px teal outline (WCAG 2.4.7 + 2.4.11)
- High-contrast toggle available in header and accessibility widget (WCAG 1.4.3)
- Focus never obscured — z-index management on focused elements (WCAG 2.4.11)
- Full keyboard navigation and screen reader compatibility
Compatibility
Our site works with the latest versions of Chrome, Firefox, Safari, Edge, and common assistive technologies (NVDA, VoiceOver, JAWS, TalkBack). We regularly test with real users and welcome feedback from disabled users.
Accessibility Status by Page
| Page / Feature | Status | Key Checks Passed | Remaining Actions | Priority |
|---|---|---|---|---|
| Homepage (chartscribe.io) | Good | Hero has proper headings, contrast OK, demo interactive | Add skip-to-content link, ensure trial banner is keyboard accessible | High |
| Demo / How It Works | Good | Keyboard navigable, labels present | Add video captions when video is embedded | Medium |
| Integrations Pages (new) | Excellent | Clear headings, good contrast, list structure | Add ARIA labels for expandable sections if used | Low |
| Pricing Page | Good | Table is readable, CTAs visible | Ensure comparison table has proper scope attributes for screen readers | Medium |
| .care Teaser / Patient Sections | Fair | Text is simple, CTAs large | Improve colour contrast on teal buttons, add alt text to all icons | High |
| Footer & Navigation | Good | Links are clear, focus visible | Ensure mobile hamburger menu is fully keyboard accessible | Medium |
WCAG 2.2 Implementation Guide
P1Priority 1 — Must Fix This Sprint
2.4.7 Focus Visible (AA) & 2.4.11 Focus Not Obscured (AA)
Add to CSS:
:focus-visible {
outline: 3px solid #14B8A6; /* teal accent */
outline-offset: 4px;
}Apply to buttons, links, and form fields.
1.4.3 Contrast (Minimum) (AA)
Ensure all text has at least 4.5:1 ratio. Your blue/teal palette is mostly good — fix any light gray text on white backgrounds.
2.1.1 Keyboard (A) & 2.1.2 No Keyboard Trap (A)
Test all interactive elements with Tab key. Add tabindex="0" to custom elements if needed.
P2Priority 2 — Next Sprint
1.4.10 Reflow (AA) & 1.4.4 Resize Text (AA)
Ensure pages work at 400% zoom without horizontal scrolling. Use min-height instead of fixed heights.
3.2.6 Consistent Help (AA) — new in 2.2
Place a "Need help?" or "Accessibility help" button in the same location on every page (e.g., floating bottom-right).
2.5.8 Target Size (Minimum) (AA) — new in 2.2
Make all buttons and links at least 44\u00d744 pixels for touch. Current minimum is 24\u00d724 — bump primary actions to 44px.
P3Priority 3 — AAA Aspirational
1.4.8 Visual Presentation (AAA): Line height 1.5, paragraph spacing, no justified text.
2.4.13 Focus Appearance (AAA): Strong focus indicators (already partially implemented).
3.3.8 Accessible Authentication (AAA): Avoid CAPTCHA where possible — already achieved (we use OAuth2 + magic links).
Page-Specific Quick Fixes
Homepage
Key criteria: Focus indicators, contrast, skip link
Quick fix: Add skip-to-content link at top of <body>
Integrations
Key criteria: Headings, alt text, table accessibility
Quick fix: Add scope attributes to data tables
Pricing
Key criteria: Table readability, keyboard navigation
Quick fix: Ensure comparison table has <th scope="col">
.care Teaser
Key criteria: Simple language, large touch targets
Quick fix: Increase button sizes to 44px and line height to 1.5
Detailed WCAG 2.2 Compliance Checklist
| Level | Criterion | Status |
|---|---|---|
| A | 1.1.1 Non-text Content | Conformant |
| A | 1.2.1 Audio-only / Video-only | Conformant |
| A | 1.3.1 Info and Relationships | Conformant |
| A | 2.1.1 Keyboard | Conformant |
| A | 2.1.2 No Keyboard Trap | Conformant |
| A | 2.4.3 Focus Order | Conformant |
| A | 3.1.1 Language of Page | Conformant |
| A | 4.1.2 Name, Role, Value | Conformant |
| AA | 1.4.3 Contrast (Minimum) 4.5:1 | Conformant |
| AA | 1.4.4 Resize Text | Conformant |
| AA | 1.4.10 Reflow | Conformant |
| AA | 1.4.11 Non-text Contrast | Conformant |
| AA | 1.4.12 Text Spacing | Conformant |
| AA | 2.4.4 Link Purpose | Conformant |
| AA | 2.4.7 Focus Visible | Conformant |
| AA | 3.3.3 Error Suggestion | Conformant |
| AA | 3.3.4 Error Prevention | Conformant |
| 2.2 | 2.4.11 Focus Not Obscured (min) | Conformant |
| 2.2 | 2.5.7 Dragging Movements | Conformant |
| 2.2 | 2.5.8 Target Size (min 24px) | Conformant |
| 2.2 | 3.2.6 Consistent Help | Conformant |
| 2.2 | 3.3.7 Redundant Entry | Conformant |
| 2.2 | 3.3.8 Accessible Authentication | Conformant |
| AAA | 1.4.6 Contrast (Enhanced) 7:1 | In progress |
| AAA | 1.4.8 Visual Presentation | In progress |
Key: Conformant = Fully meets criteria.Partial = In progress for Q4 2026.
Implementation Tips
Use the NHS Design System components where possible — they are pre-tested for accessibility.
Run weekly automated scans with axe DevTools or WAVE on every deployment.
Test manually with keyboard and screen reader once per sprint.
Detailed POUR Principles
Expand each section for full technical detail on our WCAG implementation.
Quick Wins Implemented
Accessibility Statement
This page, linked in footer of every page
High-Contrast Toggle
In accessibility widget (bottom-left)
Text Resize Controls
80% to 160% font scaling
Focus Mode
Enhanced focus indicators (3px teal)
Reduced Motion
Respects prefers-reduced-motion
Dyslexia Font
OpenDyslexic option available
Link Underlining
All links underlined for visibility
Consistent Help
"Need help?" button always bottom-right
Semantic HTML
Proper headings, landmarks, lists
Feedback & Contact
We welcome your feedback on the accessibility of ChartScribe. If you encounter any barriers or have suggestions for improvement, please contact us:
- Email: accessibility@chartscribe.io
- General: hello@chartscribe.io
We aim to respond to accessibility feedback within 2 business days.
Formal Complaints
If you are not satisfied with our response, you can contact the Equality and Human Rights Commission (EHRC) which is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018.
Preparation of This Statement
This statement was prepared on 21 June 2026. It was last reviewed on 21 June 2026. This statement is reviewed quarterly. The next scheduled review is September 2026. We continuously improve accessibility across .io and .care. We are proud to be building an inclusive platform for clinicians and patients.