Accessibility Statement

This statement describes how Sharp Cooking is built for accessibility, our current conformance status, and how to reach us if you encounter a barrier.

How we build for accessibility

Readability and navigation

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, Lighthouse, and manual keyboard and screen reader testing.

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 June 5, 2026. We review and update it regularly.