Accessibility Statement

What this covers, and the standard we build to

This statement covers the Bude Tandoori website: the menu, your order list, the booking page, and every page around them. It does not cover the restaurant itself. For anything about getting into the building or moving around inside it, ring 01288 359994 and ask, and we will tell you straight.

Ordering and booking are by phone or email. The website does not take an order or a booking itself: it keeps your list of dishes, adds up the total, and writes the email for you in your own email app, which you then send.

We build to the Web Content Accessibility Guidelines 2.2, Level AA. The Equality Act 2010 also requires us to make adjustments so that a disabled customer is not put at a substantial disadvantage compared with anybody else, and that duty is wider than any technical standard.

We are not claiming full conformance. Nobody has yet driven this site end to end with a screen reader, and until somebody has, a conformance claim would be a guess with a badge on it. What follows is what has actually been done and what has not.

What has been done

Colour and contrast, measured rather than eyeballed

Every colour pairing this site ships was computed with the WCAG relative-luminance formula, and a check re-computes them from the actual stylesheet on every build. Body text and prices on the menu read at 14.24:1 against a 7:1 requirement for the highest level. The small print — allergen text, heat words, the cash-only line — reads at 7.93:1, which is the highest level for small type rather than the minimum. The lowest pairing anywhere on the site is 4.68:1 against a 4.5:1 requirement.

The brand orange is the tightest constraint in the whole system, so it is never used as text or as a rule on a light background. Where it appears as a button fill it carries a dark label and a one-pixel dark border, and that border is what satisfies the non-text-contrast rule.

No meaning carried by colour alone

Every signal on this site is a word as well as a colour. “Vegetarian”. “Mild”, “Medium”, “Hot”, “Extremely hot”. “Sold out”. Allergens are set as bold capitals inside the description rather than as a dot or an icon, so they survive greyscale, colour blindness, a screen reader and the printout. Heat is never a flame graphic, because a graphic cannot be read aloud.

Targets big enough to hit

Every button, checkbox row, filter chip, quantity control and form field is at least 44 by 44 CSS pixels, with real space between adjacent ones so a thumb cannot catch two at once. That is the WCAG 2.2 enhanced size rather than the 24-pixel minimum. Phone numbers and email addresses that sit in a line of text are ordinary text links.

Type you can read

Body text is 17 to 18 pixels, not 16, because this audience skews older and reads in poor light. Nothing on the site is set below 14 pixels, and the small print floor is 15. Every form field is at least 17 pixels, so an iPhone never zooms the page when you tap into one. The typeface is Atkinson Hyperlegible Next, drawn by the Braille Institute so that a low-vision reader can tell a 1 from an l from an I, and prices are set in a monospaced companion so the figures line up in one column.

You can zoom to 200% and reflow to a 320-pixel-wide window without losing content or having to scroll sideways.

Keyboard and focus

Everything works from a keyboard. There is a visible two-pixel focus ring in every context on the site, which thickens to three pixels if your system asks for more contrast and switches to your operating system’s own highlight colour in a forced colours mode. A skip link at the top of every page jumps straight to the content.

Motion

If your device asks for reduced motion, the site honours it. No animation ever hides content: every section is fully visible without JavaScript and without waiting for anything to fire. The colour change between bands snaps rather than fading, for everybody, because a fade passes through a moment where the text and the background are the same colour. The site also honours a request for more contrast and a request for reduced transparency.

Structure a screen reader can follow

One heading level one per page, headings in order underneath it, real landmarks, real lists, real tables with proper row and column headers, and genuine form labels tied to their fields. Errors are announced, described in words next to the field, and never signalled by a red border alone.

It works without JavaScript

The whole menu, every price and every category is rendered on the server, so the page a search engine reads and the page a screen reader reads are the same page. Dietary filters are real checkboxes. The frequently asked questions are native disclosure elements, not a scripted accordion. Building a list of dishes needs JavaScript. Ringing us does not, and every phone number on the site is a link you can tap.

The three WCAG 2.2 rules that catch most sites out

• Consistent help. The Call button sits in the same place at the top of every page, including your order list and the booking page, and both telephone numbers and the email address are at the foot of every page.
• Redundant entry. Nothing is asked for twice. The email we write for you already holds your list, so you never type it out again. On your order list, what you type stays filled in if you pop out to your phone app and come back.
• Accessible authentication. There is no account, no password and no puzzle to solve. You never have to remember anything to order food here.

Printing

The menu has a proper print stylesheet: no navigation, no list bar, the prices intact, and both telephone numbers and the opening hours at the foot of the page. Curry-house menus get printed and pinned to fridges, and this one prints.

What we know is not right yet

This is the honest half of the page. If you hit something that is not on this list, we would rather hear about it than not.

• No screen reader test with a real person yet. The checks so far are automated and by hand at a desk. That is not the same thing. We will name the date here once that test is booked.
• Allergen information is not there per dish. The site carries the kitchen’s statement and nothing more, because the per-dish list is still being written down with the chef. Someone filtering the menu by what they must avoid cannot do that yet. Ring us and we will talk it through, every time, until it is.
• The map is a picture. It shows straight away, and its text alternative says what it shows, but you cannot zoom or move it on the page, and its street names are small. Everything it tells you is on the page in words as well: the address, the postcode and the restaurant’s own directions. The Directions button opens Google Maps, in a new tab or in your maps app.
• Where a fact is not confirmed, we say less rather than guess. If the restaurant has not yet answered something — how many the room seats, exactly when last orders are — you will find the page quiet about it, or pointing you at the telephone, rather than filling the gap with something plausible. The build refuses to publish an unanswered fact to the live site at all.
• There are no photographs of the food yet. We show no stand-in pictures. Photographs of the real food are on the list.
• The order and booking emails open in your own email app, which we do not control. We write them as plain text so they read well anywhere. On a phone with no email app set up, the button may do nothing, so the address is always shown in words as well, and you can copy your order and paste it yourself.
• There is no British Sign Language or Easy Read version of any page on this site.
• Some of the restaurant’s own words contain typing errors. Dish names and descriptions are reproduced exactly as the restaurant publishes them, including their spellings. Correcting them without asking would be putting words in their mouth, and it is a question we have with them.

There are no PDFs on this site. The old website’s price list was a PDF from 2019 with prices that had not been touched since; it is gone.

If we do not put it right

The Equality Act 2010 gives you rights here, and Bude Tandoori is a service provider under it. If you have told us about a barrier and you are not happy with what we did about it, the Equality Advisory and Support Service gives free, independent advice on what to do next, at equalityadvisoryservice.com. The Equality and Human Rights Commission is the regulator.

The Public Sector Bodies Accessibility Regulations 2018 do not apply to this site, because Bude Tandoori is a restaurant rather than a public body. The Equality Act does apply, and it is the one that matters.

How this site was checked, and when

This statement was prepared on 28 September 2026, when the site was rebuilt. It is reviewed whenever a new page ships and at least once a year.

The checks behind it are:

• every colour pairing recomputed from the shipped stylesheet on each build, with the build failing if one drops below its floor;
• every text size resolved at 320, 375, 768 and 1440 pixels wide and checked against the 14-pixel floor;
• a source check that fails the build on a focus ring removed without a replacement, on an animation of a property that causes layout, and on a button that does not declare a 44-pixel minimum in both directions;
• manual keyboard-only walkthroughs of the menu, the order list and the booking page. Those last two changed to phone and email on 28 September 2026, and the walkthrough is still to be repeated on the new version;
• the site loaded with JavaScript switched off, to confirm the menu and the prices are still there.

Still to do: a session with a screen reader and somebody who uses one every day, and a pass on a mid-range Android phone in low light, which is where the heat words and the links sit closest together in colour.

Last reviewed 28 September 2026.