Commitment
Accessibility Statement
Diabetes touches people with a huge range of abilities, including low vision from retinopathy, limited dexterity, and cognitive load from managing a chronic condition every day. Building an accessible platform isn't optional for us — it's part of the mission.
Last updated: June 1, 2024
In plain language
- We're targeting WCAG 2.1 Level AA across the platform.
- Keyboard navigation, focus indicators, and screen-reader labeling are built into our core components.
- We know we have gaps — this page names them honestly, not just the parts that are finished.
- You can report an issue directly and we'll respond and prioritize a fix.
1. Our standard
We're working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the widely accepted standard for web accessibility and a common benchmark under the Americans with Disabilities Act (ADA). This is an ongoing target, not a one-time checkbox — we test and improve continuously as we ship new features.
2. What we've done
- Semantic HTML and a consistent heading hierarchy so screen readers can navigate pages logically.
- Visible focus states on every interactive element, tuned to meet contrast requirements.
- Keyboard support for navigation, forms, dialogs, and the AI copilot panel.
- Color combinations checked against WCAG AA contrast ratios for text and UI components.
- Descriptive alt text and ARIA labeling on product images, icons, and interactive controls.
- Skip links and landmark regions so keyboard and screen-reader users can jump past repeated navigation.
- Support for browser text resizing and zoom without loss of content or function.
3. Known gaps
We'd rather tell you what's incomplete than pretend it isn't. As of this update:
- Some vendor-uploaded product images may be missing descriptive alt text, since vendors control their own listing content.
- A few data-dense tables in the vendor dashboard are still being optimized for screen-reader table navigation.
- Some older community forum content predates our current accessibility review process.
- Third-party embedded content (like payment provider widgets) is only as accessible as the provider makes it.
We track these as active work and prioritize fixes based on impact.
4. Assistive technology we test with
We test regularly with keyboard-only navigation, and periodically with screen readers including VoiceOver and NVDA, across current versions of major browsers. If something doesn't work well with the specific combination of browser and assistive technology you use, please tell us — that detail helps us reproduce and fix it faster.
5. How to report an issue
If you hit a barrier anywhere on Diabetes Collective, email accessibility@diabetescollective.com with the page, what you were trying to do, and the browser or assistive technology you were using. We aim to acknowledge reports within 3 business days and will follow up with a plan or fix timeline.
Questions about this page
Accessibility is a moving target we take seriously — thank you for helping us close the gaps.
Diabetes Collective provides product information and general education only. It does not provide medical advice, diagnosis or treatment. See our Terms of Service for details.