Legal
Accessibility
We want everyone to be able to read our menu and get in touch. Here is what we have done, and what we have not.
What we aim for
We build to WCAG 2.2 Level AA. Automated accessibility checks run against every page each time the site is updated, and a build that introduces a violation fails rather than going live.
Automated checks catch perhaps half of what matters, so they are a floor rather than a guarantee.
What we have done
Reading
- Body text is never smaller than 16 pixels
- Every text colour we use meets or exceeds AA contrast against its background
- Our brand gold fails contrast on cream at text size, so we use it only for decoration and a darkened version for anything you actually read
- Text reflows without a horizontal scrollbar down to a 320-pixel screen, and to 200% zoom
- Colour is never the only way information is conveyed
Navigating
- Everything works with a keyboard alone, in a sensible order
- The focused element is always clearly outlined
- A "skip to main content" link is the first thing you reach on every page
- Buttons and links are at least 44 by 44 pixels
- Headings are properly nested, so you can jump between sections
- Animation is minimal and respects "reduce motion" if your device asks for it
The menu
- It is real text, never a picture of a menu or a PDF. It can be read aloud, enlarged, translated, and searched
- The category filter works with a keyboard and needs no JavaScript at all
- With JavaScript switched off, every dish is still listed
The enquiry form
- Every field has a visible label — placeholder text is never used instead of one
- Errors are announced aloud, tied to the field they belong to, and focus moves to the first problem
- Required fields are marked in words, not by colour
- The submit button is never disabled before you press it, so there is always something to act on
What is not finished
Stated plainly, because a statement that claims everything is perfect is not credible.
- The form needs JavaScript. Our spam protection requires it. With JavaScript off, the form is replaced by our email address — a working alternative, but not the same experience
- Dietary and allergen labels are not yet published for 13 of 13 dishes. Those dishes say "ask us about allergens" instead. We would rather show nothing than show something our kitchen has not confirmed, but we know an unlabelled menu is harder to use
- We have not commissioned a formal independent audit. Our testing is automated checks plus manual keyboard and screen-reader passes
- Photography is still being added. Every image will carry a description — our system refuses to publish one without
If something does not work
Please tell us. Emailcatering@bellpepperscuisine.com with the page and what went wrong, and we will fix it. We aim to reply within five business days.
If a page is blocking you and you need something from it now — the menu, a price, to place a catering enquiry — say so and we will simply give you the information directly rather than making you wait for a fix.
Assistive technology
We test with VoiceOver on iOS and macOS, and with keyboard-only navigation on desktop. We have not tested with every combination of screen reader and browser in existence. If you use something we have not tried and it does not work, that is useful for us to know.