We want every recipe on 24cocktails.com to be readable by everyone, including people who use a screen
reader, a keyboard alone, a magnifier or a phone with large text. This statement says where the Site stands against the
Web Content Accessibility Guidelines (WCAG) 2.2, level AA, and what still falls short.
What the Site does
- Every page is plain HTML that works without scripts: the recipe, its measures, method and picture are in the page as
the server sends it, with headings, lists and a language attribute that screen readers use.
- Every picture has an alternative text that names the drink and says it is an illustration; decorative drawings are hidden from assistive technology.
- The header, the drawer menu, the search, the language list and the cookie banner can be operated from the keyboard;
buttons and links have visible focus and accessible names.
- Text and background meet the AA contrast ratio in both the dark and the light theme; the theme can be switched; by default
it follows the time of day (light by day, dark at night), and your choice is remembered.
- Pages reflow to a phone width and to text enlarged to 200% without horizontal scrolling.
- Measures can be shown in ounces or millilitres, and the finder, quizzes and calculators work with the keyboard.
What still falls short
- The free printable PDFs are laid out for paper and are not tagged for screen readers. The same recipes are on the
Site as HTML; the PDF's page names which ones.
- Recipes in the 34 languages other than English and Russian are machine translation, published without being
read by a person, so a screen reader may meet an awkward phrase or an English word in a translated sentence. The
English and Russian pages carry the same recipes, written by hand.
- A few third-party embeds (the Pinterest "Save" button, Telegram previews) come with their own accessibility.
Tell us about a barrier
If something on the Site is hard to use, write to
[email protected] with the page address and what happened. We answer within
three business days and fix what we can; a barrier that blocks a recipe is treated as a bug.
How this was assessed
By our own review of the templates and of sample pages with a screen reader, keyboard-only use and automated checks.
This statement is reviewed when the Site's templates change.