Using this site
Accessibility
What we have done, what we know is unfinished, and how to tell us when something does not work.
Where we stand
We have not carried out a formal audit, so this page claims no conformance level. Saying otherwise would be easy and would not be true. We aim at WCAG 2.2 AA as a working target and fix what we find.
What is in place
- A skip link to the main content, as the first thing a keyboard or screen-reader user reaches.
- Text colours chosen against their actual backgrounds rather than by eye — the muted grey used for secondary text was darkened after it measured about 3.2:1, below the 4.5:1 needed for body text.
- Light and dark themes that follow your system setting, both with their contrast checked.
- Headings, lists and landmarks used for what they are, so the page can be navigated by structure instead of by scrolling.
- Recipes as real structured data — ingredients are a list, steps are a list — rather than one block of prose.
- Menus that close on Escape and return focus, and controls that are reachable and operable by keyboard.
Known gaps
Listing these is more useful than a conformance badge:
- Image descriptions vary. Recipe photographs are contributed, and alt text is only as good as what the contributor wrote. Some will be thin or missing.
- No screen-reader testing has been done with real assistive technology across browsers. Automated checks are not the same thing and we are not claiming they are.
- The sign-in state appears after the page loads. The header briefly shows a signed-out state before catching up, which can be confusing if you are listening rather than looking.
If something does not work
Tell us at support@yarkii.com. The page you were on and what you were trying to do is enough; you do not need to know why it failed. An accessibility problem is a bug, and we would rather hear about it than not.