Accessibility Statement
Making cooking better for everyone
Sharp Cooking is committed to ensuring digital accessibility for everyone, regardless of ability or assistive technology. We believe accessibility isn't accommodation — it's good design.
We're continuously improving the user experience for all our users and applying the relevant accessibility standards to ensure we provide equal access to everyone.
Conformance Status
Sharp Cooking aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 Level AA conformance means our website meets all Level A and Level AA success criteria.
Current Status: Partially conformant. We're actively working toward full compliance and conduct regular accessibility audits to identify and fix barriers.
Accessibility Features
Keyboard Navigation
- All interactive elements are keyboard accessible
- Logical tab order throughout the application
- Skip links to bypass repetitive navigation
- Visible focus indicators on all interactive elements
- Keyboard shortcuts in Cooking Mode (arrow keys, spacebar, etc.)
Screen Reader Support
- Semantic HTML5 elements (nav, main, article, section, etc.)
- ARIA labels and landmarks where semantic HTML isn't sufficient
- Alternative text for all meaningful images
- Form labels and instructions properly associated
- Live regions for dynamic content updates
Visual Design
- Text meets WCAG 2.2 contrast requirements (4.5:1 for body text, 3:1 for large text)
- Minimum 16px base font size for body text
- 1.5x line height for improved readability
- Color is never the only means of conveying information
- Text can be resized up to 200% without loss of functionality
Mobile & Touch
- Touch targets meet 44x44px minimum size (WCAG 2.2 criterion 2.5.8)
- Responsive design works across screen sizes
- Mobile-optimized layouts for portrait and landscape
- No reliance on hover-only interactions
Cooking Mode
- Extra-large serif text (1.75-2.75rem) for countertop distance reading
- High contrast color scheme for visibility in kitchen lighting
- Voice control for hands-free navigation (experimental)
- Simple, focused interface with minimal cognitive load
- One action at a time to reduce working memory demands
Compatible Technologies
Sharp Cooking is designed to be compatible with the following assistive technologies:
Screen Readers (Tested)
- VoiceOver (macOS, iOS)
- NVDA (Windows)
- JAWS (Windows)
- TalkBack (Android)
Browsers (Supported)
- Safari (macOS, iOS) - current and previous version
- Chrome (Windows, macOS, Android) - current and previous version
- Firefox (Windows, macOS) - current and previous version
- Edge (Windows) - current and previous version
Known Limitations
We're aware of the following accessibility barriers and are working to address them:
- Voice Control (Cooking Mode): Currently experimental and only supports Chrome/Edge browsers with Web Speech API. We're exploring more robust alternatives for cross-browser voice navigation.
- Image Upload Flow: Drag-and-drop interface may be difficult for some users. Alternative click-to-upload method is available but could be more prominent. Expected fix: Q2 2026
- Recipe Import: Some error messages lack sufficient context for screen reader users. Expected fix: Q2 2026
If you encounter accessibility barriers not listed here, please let us know using the contact information below.
User-Generated Content
Sharp Cooking is your cooking assistant. Your recipes belong to you, and we don't control their content. While we provide tools to make recipes accessible (structured formatting, semantic HTML, alt text fields for images), we can't guarantee that all user-created content meets accessibility standards.
We encourage users to:
- Write clear, specific recipe instructions (see our guide on writing accessible recipes)
- Add descriptive alt text to recipe images
- Use proper units and measurements rather than vague terms
- Structure recipes with clear sections (ingredients, instructions, notes)
Privacy & Assistive Technology
We don't collect data about your assistive technology usage. Whether you use a screen reader, voice control, switch control, or any other assistive technology, we treat that information the same way we treat all your data: it's yours, and it stays private.
We don't track, analyze, or monetize accessibility features. Our analytics (via Plausible) are cookieless and privacy-first — we see page views and device types, not individual user behavior or assistive technology usage.
Feedback & Contact
We welcome feedback on the accessibility of Sharp Cooking. If you encounter accessibility barriers or have suggestions for improvement, please contact us:
- Email: info@sharpcooking.com
- Feedback Form: Contact page
- In-App Feedback: Click "Send Feedback" in the app header
We aim to respond to accessibility feedback quickly and will work with you to provide the information or resolve the issue.
If you need assistance accessing any content or using any features, we're happy to provide alternative formats or assistance. Just ask.
Assessment Approach
Sharp Cooking's accessibility is assessed through:
- Self-evaluation: Internal testing against WCAG 2.2 Level AA criteria
- Automated testing: Regular scans with axe DevTools and Lighthouse
- Manual testing: Keyboard navigation, screen reader testing, and real-world usage scenarios
- User feedback: Continuous improvement based on user-reported issues
Formal Complaints Process (EU)
If you're not satisfied with our response to your accessibility concern, you have the right to file a formal complaint:
- First step: Contact us at info@sharpcooking.com with details of the barrier
- If unresolved: EU users may file a complaint with their national enforcement body under the European Accessibility Act
- US users: May file a complaint under the Americans with Disabilities Act (ADA) with the U.S. Department of Justice
Ongoing Improvement
This statement was last reviewed on March 2, 2026. We review and update this statement at least twice per year or whenever significant changes are made to the platform.
Accessibility is an ongoing commitment. We're continuously testing, learning, and improving to ensure Sharp Cooking works for everyone. If you have ideas for how we can do better, we want to hear them.