Need help? Email shivaji@ananyoo.com Contact

Yummy House Altamonte Accessibility Audit: WordPress Restaurant Site Tested and Retested to WCAG 2.2 AA

,

Project details

Start your audit

About the project

This Yummy House Altamonte accessibility audit covered the website of Yummy House Chinese Restaurant in Altamonte Springs, in the Orlando area of Florida. The site is built on WordPress with Elementor and does one job: show the dinner menu and the dim sum menu, give directions and let guests get in touch. We had already audited the sister site, Yummy House Florida, so the restaurant group came back to us when this location's site needed the same treatment.

A restaurant website is small, but it is the first thing a guest with a disability checks before deciding where to eat. If the menu is a picture of text, a blind guest cannot read it. If the search flyout cannot be closed with Esc or the suggestions cannot be reached with the arrow keys, a keyboard user is stuck in the header. Those are the barriers that decide whether a family books a table or goes somewhere else.

StandardWCAG 2.2 AA
PlatformWordPress + Elementor
TestingManual + Retest
RegionUSA

Why accessibility matters for a restaurant website

Florida is second only to California for web accessibility lawsuits under Title III of the ADA, and restaurants are one of the most frequently sued categories because their menus are so often published as images or PDFs. Beyond the legal risk, Orlando serves a large number of older residents and visitors, and guests with low vision, hearing loss or limited mobility want to check the menu, hours and location before they come. WCAG 2.2 Level AA is the standard that makes sure every one of them can.

Scope and standard

Our Yummy House Altamonte accessibility audit assessed the live site against WCAG 2.2 Level A and AA. The site has five pages, so we tested every element on every page rather than sampling, and tested the global header, search flyout, mobile menu and footer separately so a shared fix covers every page:

  • Home: hero section, dish carousel, feature blocks, dining room gallery, opening hours and calls to action
  • Menu and Dim Sum: the full dinner menu and the dim sum lunch menu, including how prices and dish names are structured for a screen reader
  • Contact and Search: the contact form and embedded Google map, and the site search results page
  • Global elements: header search button and flyout with suggestions, open and close menu button, mobile navigation and footer, tested once and reported for every page

How we ran the Yummy House Altamonte accessibility audit

  • Screen reader testing with JAWS and NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android, in both browse and focus modes
  • Keyboard only operation of every page, including the search flyout and its suggestion list, the carousel, the contact form and the map controls, with attention to focus order, Esc behaviour and a visible focus indicator
  • Colour contrast analysis of menu text, buttons and links against the dark red and gold restaurant palette
  • Browser zoom to 400% and text spacing checks for low vision users, with the menu tables and header checked at each size
  • A retest of every barrier after the fixes were applied, repeated with the same assistive technology until each item passed

What accessibility means on each part of the site

Because guests come to the site for the menu and the way to get there, our Yummy House Altamonte accessibility audit paid most attention to the parts of the site that stand between a hungry visitor and a table:

  • Header search and menu buttons: the search and menu toggles must be announced as buttons, not links, the search flyout must close with Esc, and the suggestion list must be operable with the Up and Down arrow keys.
  • Menus: the dim sum lunch menu, published as an image of text, needs a real text version so screen reader users and anyone zooming in can read dish names and prices.
  • Carousel and galleries: slides and gallery items need a visible focus indicator and controls that work without a mouse.
  • Contact form and map: the Send button and the embedded map controls need a visible focus indicator, and the form fields need labels and announced errors.
  • Colour and text: gold and red text on dark backgrounds must meet contrast ratios, and headings and body text must stay readable with custom text spacing.

The barriers we logged were the usual pattern for an Elementor build: toggles exposed with the wrong role, a search suggestion list that keyboard users could not reach, a flyout that ignored the Esc key, focus indicators hidden across slides, buttons and map controls, a menu delivered as an image of text, and several contrast and heading structure issues. Each barrier was recorded with the page, the WCAG success criterion, the actual and expected result, a code snippet and a recommended fix, graded by severity so the developer could start with the critical keyboard blocker.

Outcome

Every barrier found in this Yummy House Altamonte accessibility audit was fixed and then retested by us with the same screen readers and keyboard checks, and every one of them passed. The restaurant now has a WordPress site where the menu can be read, the search can be used and the contact form can be sent by every guest, along with a complete tracker showing what was found, what was changed and the retest result for each item.

Services we provided for this client

Accessibility settings

Saved on this device. Change them any time.

Read our accessibility statement