Accessibility Statement
Our commitment to making the Accessibility Audit Tool accessible to everyone, regardless of ability or technology.
Hey there 👋
I'm Geoffrey, the person behind CheckFox, the tool that helps people evaluate and improve digital accessibility. Since CheckFox was born to support accessibility, it only makes sense that I make it as accessible as possible too.
This page isn't a checkbox. It's my way of being transparent about what I've done, what I'm doing, and where I still have work to do. So let's talk about it, human to human.
My Commitment
Accessibility is at the heart of everything I do
Accessibility isn't a one-time project, it's a living thing that grows with the product (and with me). Every new design, feature, or line of code goes through the same simple test:
"Would this be annoying, confusing, or impossible for someone using assistive tech?"
If the answer's "maybe," I fix it. I'm continuously learning, improving, and testing to make CheckFox more inclusive for everyone. It's not perfect, but it's getting better all the time.
Standards and Guidelines
CheckFox aims to conform to the following accessibility standards and guidelines:
European Standard for digital accessibility requirements
Luxembourg Web Accessibility Guidelines
Accessibility Features
CheckFox includes a bunch of accessibility-friendly things by design, like:
Keyboard Navigation
- Full keyboard accessibility for all interactive elements
- Logical tab order throughout the interface
- Visible focus indicators with high contrast
- Skip links to main content areas
Screen Reader Support
- Semantic HTML markup and proper heading structure
- Descriptive alt text for all meaningful images
- ARIA labels and descriptions where appropriate
- Screen reader announcements for dynamic content
Visual Design
- High contrast color schemes (minimum 4.5:1 ratio)
- Information conveyed through multiple senses (not color alone)
- Scalable text up to 200% without horizontal scrolling
- Touch targets of at least 24x24 pixels
Forms and Interaction
- Clear labels associated with all form controls
- Error messages linked to relevant form fields
- Descriptive button and link text
- No timeout or time sensitive actions
It doesn't mean it's perfect, or I didn't miss any spot. So if you find anything that is disturbing, tell me and I'll do my best to fix it.
How I test things
I test accessibility in a few ways:
Automated Testing
Regular automated scans using industry-standard tools to identify potential accessibility issues.
Manual Testing
Comprehensive manual testing with assistive technologies including screen readers (MacOS Voiceover on Chrome), voice control, and keyboard-only navigation.
User Testing
Ponctual user testing with folks, but I don't ask there disabilities, so it's more random.
Expert Review
Periodic reviews by myself, accessibility expert, to ensure compliance with current standards and best practices.
Automation catches the easy stuff. People catch the important stuff.
But, know that this tool is also an experiment: it's made using 2 Artificial Intelligence to measure their limitations.
Known Limitations
Let's be honest: no product is perfect (especially one made by a single human). Here are a few things I'm aware of and improving: If you spot anything else, or hit a blocker, I really want to know.
PDF Report Generation
Generated PDF reports may not be fully accessible. I'm working on improving PDF accessibility features.
AI-Coding & randomness
The code is lead by Figma Make and Claude Code with really specific accessibility requirements. However, I know some parts of the code may need improvements. They are not blocking (supposedly) and I'll work on improving it.
I'm committed to addressing these limitations in future releases and warmly welcome your feedback.
Assistive tech I've tested with
So far, I've tested CheckFox with:
Screen Readers
- VoiceOver (macOS/iOS)
- TalkBack (Android)
Other Technologies
- Voice control software
- Switch navigation devices
- Magnification software
- Alternative keyboards
Next on my list: testing with NVDA, and Voiceover mobile. If you use one of these and feel like sharing feedback, I'd be super grateful!
Feedback & Support
Accessibility is a conversation, not a compliance checkbox. (that's why this tool is called CheckFox and not checkbox 🥹)
If you find a bug, a barrier, or just something that could feel smoother, please tell me!
How to Provide Feedback
- Email me at:
- Use the feedback form in your user settings
If you take the time, here is what to include:
- What you were trying to do
- What went wrong (or weird)
- What browser or assistive tech you use
I usually reply within 2 business days, and I'll let you know how or when I plan to fix the issue. Sometimes I even fix it the same day, perks of being a solo dev 😉
Continuous Improvement
Accessibility is an ongoing journey, not a destination. I'm committed to:
- Regular accessibility audits of my own platform
- Staying current with accessibility standards and best practices
- Engaging with the disability community for feedback and guidance
My Promise: I will continue to improve the accessibility of CheckFox with each release, ensuring that all users can effectively use this tool to create more accessible digital experiences.
Additional Resources
Learn more about digital accessibility and best practices: