Accessibility Statement

Making cooking better for everyone

Sharp Cooking is designed to work for everyone — including people who cook with assistive technology, limited vision, limited mobility, or just messy hands and a noisy kitchen. Accessibility isn't a feature we added later. It's how we build.

What does "accessible cooking" mean?

It means you can use the app while actually cooking — with messy hands, limited visibility, or assistive technology — without friction.

What does accessibility mean in a cooking app?

Most accessibility statements talk about compliance checkboxes. We think about accessibility in terms of real cooking situations:

  • You're standing three feet from your phone and can't read small text
  • Your hands are covered in dough and you can't touch the screen
  • You use a screen reader and need the recipe structure to make sense without seeing the page
  • You're in a loud kitchen and need visual alternatives to audio cues
  • You have limited mobility and navigate entirely with a keyboard

Sharp Cooking is built for these situations because these situations are cooking. We've written more about what accessible cooking actually means and why it matters beyond compliance.

How we build for accessibility

Readable at a distance

Body text throughout the app meets WCAG 2.2 contrast requirements (4.5:1 for body text, 3:1 for large text). The base font size is 16px with 1.5x line height. Text can be resized up to 200% without breaking the layout.

Full keyboard support

Every interactive element is accessible via keyboard. Logical tab order, visible focus indicators, skip links to bypass navigation.

Screen reader support

Semantic HTML5 throughout (nav, main, article, section). ARIA labels and landmarks where semantic HTML isn't sufficient. Properly associated form labels. Live regions for dynamic content updates. Alternative text for all meaningful images.

Touch and mobile

Touch targets meet the 44x44px minimum (WCAG 2.2 criterion 2.5.8). Responsive layouts for every screen size. No hover-only interactions. Portrait and landscape support.

Conformance status

Sharp Cooking aims to conform to WCAG 2.2 Level AA. Current status: partially conformant. We conduct regular audits with axe DevTools and Lighthouse.

Known limitations

We're aware of these barriers and working to address them:

  • Image upload drag-and-drop may be difficult for some users. Click-to-upload is available but could be more prominent. Expected improvement: Q2 2026.
  • Some error messages during recipe import lack sufficient context for screen reader users. Expected fix: Q2 2026.

Privacy and assistive technology

We don't collect data about your assistive technology usage. Whether you use a screen reader, voice control, switch access, or any other tool, that information stays private. Our analytics (Plausible) are cookieless — we see page views and device types, not individual behavior or technology choices.

Compatible technologies

Screen readers targeted: VoiceOver (macOS, iOS), NVDA (Windows), JAWS (Windows), TalkBack (Android)

Browsers supported: Safari, Chrome, Firefox, Edge — current and previous versions

User-generated content

Your recipes belong to you, and we can't control their content. We provide tools to make recipes accessible — structured formatting, alt text fields for images, clear ingredient and instruction sections — and we encourage users to write clearly and use proper measurements. Our guide on making recipes easier to read covers practical tips for writing accessible recipes.

Feedback

If you encounter an accessibility barrier, we want to know about it:

We respond to accessibility feedback promptly and will work with you to resolve the issue. If you need content in an alternative format, just ask.

Formal complaints

If you're not satisfied with our response:

Ongoing improvement

Cooking should be accessible to everyone. The tools around it should be too.

This statement was last reviewed on March 2, 2026. We review and update it at least twice per year.