Accessibility Statement
How Taco Bell Menu works towards WCAG 2.1 AA, what we have done, and how to report a barrier.
Last updated: 22 July 2026
EasyMenue wants everyone to be able to read this menu, including people using a screen reader, a keyboard alone, magnification, or a phone in bright sunlight.
Target
We aim to meet WCAG 2.1 level AA. That is a goal we work towards, not a certification we hold, and we would rather say so plainly than claim conformance we have not had audited.
What is in place
- A "skip to main content" link, and proper landmarks and heading structure on every page.
- Full keyboard operation, with a visible focus outline.
- Text alternatives for dish photographs, and an explicit "no photograph available" label rather than a silent gap.
- Touch targets sized for thumbs, and a layout that reflows to narrow screens without horizontal scrolling.
- The site works without JavaScript. The restaurant picker falls back to an ordinary form, and to browsing restaurants by state.
- Warnings that matter — such as the shared-kitchen cross-contact note on certified vegetarian dishes — are written into the page as visible text, never hidden in a tooltip that a screen reader or a touch screen would never reveal.
Known limitations
- Some imported dish photographs have generic alt text where no better description has been written yet.
- Long menu listings can be tiring to page through with a screen reader; choosing a restaurant first shortens them considerably.
- We do not control the content of the imported menu descriptions.
Tell us about a barrier
If any part of this site is hard or impossible to use, email admin@easymenue.com with the page address and what went wrong, including the assistive technology and browser you were using if you can. Accessibility reports go to the front of the queue.