Accessibility Statement
How Chick-fil-A Menu works towards WCAG 2.1 AA, what we have done, and how to report a barrier.
Last updated: 23 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. Menu search and the dietary filters fall back to ordinary links and forms.
- Warnings that matter — such as the shared-kitchen cross-contact note on grilled items — 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; the category pages and the dietary filters break them into smaller sets.
- 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.
Frequently Asked Questions
Does Chick-fil-A Menu meet WCAG accessibility standards?
We aim to meet WCAG 2.1 level AA across the site. That is a goal we actively work towards, not a certification we hold or claim to have had audited — we would rather say that plainly than overstate our conformance, and we welcome reports of anywhere we fall short of it.
Does the site work without JavaScript or with a screen reader?
Yes. The menu, search and dietary filters fall back to ordinary links and forms when JavaScript is unavailable, every page is fully keyboard-operable with a visible focus outline, and proper landmarks and heading structure run through the whole site, including a "skip to main content" link at the top of every page.
Are food-safety and allergen notes presented accessibly?
Yes — notes that matter, such as the shared-kitchen cross-contact caution on grilled items, are written into the page as visible text, never hidden inside a title-attribute tooltip that a screen reader or a touch screen would never reveal to the people who most need to read it before they order.
How do I report an accessibility barrier on this site?
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 our queue rather than a general backlog, and we treat them with the same urgency as a broken page.