Our Commitment to Accessibility
ChopChopGo is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards. We recognize that accessibility is an ongoing effort and are dedicated to making our recipe management application usable by the widest possible audience.
Standards & Guidelines
This accessibility statement applies to the ChopChopGo mobile and web applications. We aim to conform to the following standards:
- Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA
- EN 301 549 (European Standard for accessibility requirements)
- European Accessibility Act requirements for digital services
- Americans with Disabilities Act (ADA) Title III
- Section 508 of the Rehabilitation Act
- Accessibility for Ontarians with Disabilities Act (AODA)
- Apple Human Interface Guidelines – Accessibility section
- Google Material Design Accessibility Guidelines
Conformance Status
"Partially conformant" means that some parts of the application do not fully conform to WCAG 2.2 Level AA. ChopChopGo currently meets some but not all accessibility requirements. We have identified multiple barriers that prevent full conformance and are actively working to remediate these issues.
Estimated Current WCAG 2.2 AA Conformance: 45-55%
Scope of Coverage
Supported Platforms
- iOS: Minimum iOS 13+ (based on Flutter 3.8.1 requirements)
- Android: Minimum Android 5.0 Lollipop / API 21+
- Web: Chrome 90+, Firefox 88+, Safari 14+, Edge 90+
Included in This Statement
- Native mobile application (iOS & Android)
- Progressive Web Application (PWA)
- Marketing website and subdomains
- In-app dialogs, forms, and interactive components
Accessibility Features Currently Implemented
Platform Support
- Font Scaling (Android): System-level font size adjustments supported
- Keyboard Navigation (Partial): Form fields use appropriate input actions and types
- Minimum Touch Targets: 44×44pt enforced on dialog buttons
- Theme Support: Light and dark color schemes defined
- Semantic Labeling (Limited): Some buttons include Semantics widgets
- Responsive Design: Supports multiple screen sizes and orientations
- Web Accessibility: Proper HTML lang attributes, some alt text on images
- Color Palette: High-contrast Material Design 3 colors
Known Accessibility Limitations
We have identified the following accessibility barriers during our December 2025 audit:
Critical Severity Issues
1. Missing Semantic Labels on Interactive Elements
Issue: Most buttons, cards, icons, and interactive widgets lack semantic labels.
WCAG: 4.1.2 Name, Role, Value (Level A), 1.3.1 Info and Relationships (Level A)
Impact: Screen reader users cannot identify or understand interactive elements.
Affected: ~100+ Dart UI files
Remediation: Version 0.2.0 (Q1 2026)
2. Images Without Alternative Text
Issue: Recipe images and visual content lack semantic labels or alt text.
WCAG: 1.1.1 Non-text Content (Level A)
Impact: Screen reader users cannot access essential recipe image content.
Affected: blurhash_image.dart, recipe_image_display.dart, all recipe cards
Remediation: Version 0.2.0 (Q1 2026)
3. Gesture-Only Interactive Elements
Issue: Custom gesture detectors lack keyboard alternatives.
WCAG: 2.1.1 Keyboard (Level A)
Impact: Keyboard-only users cannot activate interactive elements.
Affected: recipe_card.dart, tap gestures throughout app
Remediation: Version 0.3.0 (Q2 2026)
High Severity Issues
4. Hard-Coded Font Sizes
Issue: Text sizes are fixed and don't scale with user preferences.
WCAG: 1.4.4 Resize Text (Level AA)
Impact: Users with low vision cannot benefit from accessibility settings.
Remediation: Version 0.3.0 (Q2 2026)
5. Missing Focus Management
Issue: No FocusNode implementation or keyboard focus strategy.
WCAG: 2.4.7 Focus Visible (Level AA), 2.4.3 Focus Order (Level A)
Impact: Keyboard users cannot navigate efficiently.
Remediation: Version 0.3.0 (Q2 2026)
6. Insufficient Color Contrast
Issue: Color combinations not verified against WCAG AA ratios.
WCAG: 1.4.3 Contrast (Minimum) (Level AA)
Impact: Users with low vision may not be able to read text.
Remediation: Version 0.2.0 (Q1 2026)
Moderate Severity Issues
- Animations Without Reduced Motion: No motion preference checks (WCAG 2.3.3) - Q3 2026
- Dialog Accessibility Gaps: Missing focus trapping (WCAG 2.4.3, 2.1.2) - Q2 2026
- Forced Light Theme: Ignores system dark mode preference (WCAG 1.4.8) - Q1 2026
- Form Field Gaps: Error messages not announced to screen readers (WCAG 3.3.1, 4.1.3) - Q2 2026
- Missing ARIA on Web: Marketing pages lack ARIA labels (WCAG 4.1.2) - Q1 2026
Minor Severity Issues
- Skip-to-Content Links: Missing on marketing pages (WCAG 2.4.1) - Q3 2026
- Widget Documentation: Custom components lack accessibility guidance - Q2 2026
- Navigation Announcements: No screen reader context (WCAG 2.4.2) - Q2 2026
Accessibility Audit Summary
| Severity | Count |
|---|---|
| Critical | 3 issues |
| High | 6 issues |
| Moderate | 5 issues |
| Minor | 3 issues |
| TOTAL | 17 issue categories |
Top 5 Priority Fixes
- Add semantic labels to all interactive elements - WCAG 4.1.2, 1.3.1
- Implement image alternative text - WCAG 1.1.1
- Add keyboard navigation support - WCAG 2.1.1, 2.4.3, 2.4.7
- Implement responsive text sizing - WCAG 1.4.4
- Verify and fix color contrast - WCAG 1.4.3
Future Accessibility Roadmap
Q1 2026 (Version 0.2.0)
- Add semantic labels to all interactive elements
- Implement image alt text
- Fix color contrast issues
- Respect system dark mode preference
- Add ARIA labels to marketing pages
Q2 2026 (Version 0.3.0)
- Implement keyboard navigation
- Add focus management
- Replace hard-coded font sizes
- Improve form accessibility
- Add screen reader navigation announcements
Q3 2026 (Version 0.4.0)
- Implement reduced-motion support
- Add skip-to-content links
- Conduct full WCAG 2.2 AA compliance audit
- Publish accessibility testing guide
Ongoing
- Monthly accessibility reviews
- Automated testing in CI/CD
- User research with people with disabilities
- Staff training on accessible development
Feedback and Contact Information
We welcome feedback on the accessibility of ChopChopGo. If you encounter barriers, please contact us:
Email: accessibility@chopchopgo.app
Alternative Contact: support@chopchopgo.app
Expected Response Time: 7 business days. Complex issues receive status updates every 10 business days.
Feedback Methods:
- Email (preferred for detailed technical reports)
- In-app feedback form (Settings → Help & Feedback)
Enforcement Procedure (EU Users)
For users in the European Union: If you are not satisfied with our response to your accessibility concern, you have the right to lodge a complaint with the relevant national enforcement body under the European Accessibility Act. We are committed to working cooperatively with regulatory authorities to resolve accessibility issues.
Technical Specifications
Assistive Technologies Tested
- iOS VoiceOver (iOS 16, 17)
- Android TalkBack (Android 12, 13, 14)
- NVDA Screen Reader (Windows, version 2023.3)
- Safari with VoiceOver (macOS Ventura, Sonoma)
Testing Browsers
- Chrome 120+ (Windows, macOS, Android)
- Safari 17+ (iOS, macOS)
- Firefox 121+ (Windows, macOS)
- Edge 120+ (Windows)
Automated Testing Tools
- Flutter Accessibility Scanner
- axe DevTools
- WAVE Web Accessibility Evaluation Tool
Conclusion
ChopChopGo has made foundational accessibility investments but significant work remains to achieve WCAG 2.2 Level AA conformance. The development team is committed to systematic improvement, with clear remediation timelines for all identified issues.
This statement will be updated quarterly as accessibility improvements are implemented and new features are audited.