Accessibility

TasteBoard aims for:

• Alt text on images, so screen reader users know what each photo shows.
• Headings in order, so the structure of a page makes sense to people and to assistive technology.
• Contrast for text and buttons, so words are readable without strain.
• Touch targets at least 44 pixels high, so buttons and checkboxes are easy to tap on a phone.

Honesty time, because a page that claims perfect accessibility would not be true:

• The recipe checklists and the cook mode features need JavaScript. The core recipe text does not, so ingredients, steps, times, and temperatures are readable without it.
• Large recipe photos may load slowly on very slow connections.
• Print layouts may differ between browsers, so a printed recipe may not look the same everywhere.

The recipe itself, the part a cook needs at the stove, is plain readable text.

Accessibility problems can be reported through the contact page. These details help:

• The page address of the page where the problem happened.
• The device and browser you were using.
• What went wrong, and what you expected to happen.

Every report is checked, and fixes are made where possible.