OpenTable
Is the OpenTable Reservation Widget ADA Compliant? WCAG 2.2 Keyboard & Iframe Teardown
Verdict
OpenTable hosted reservation pages have matured significantly in ARIA labeling, yet restaurant websites embedding OpenTable via custom iframes or wrapper modals frequently introduce WCAG 2.4.1 and 4.1.2 violations. Our specimen benchmark scored 68/100 due to untitled wrapper iframes, broken ARIA combobox wrappers on custom date/time bars, and low-contrast unavailable time-slot pills.
- Critical / serious
- 0 / 3
- Moderate / minor
- 0 / 0
- Keyboard
- Partial
- Overlay script
- None
axe-core rules triggered: aria-input-field-name, color-contrast, frame-title · Scanned
Key findings
- Merchant-pasted OpenTable iframe embeds frequently omit a descriptive title attribute (WCAG 4.1.2 frame-title), causing screen readers to announce raw widget query URLs.
- Custom "skinny" horizontal reservation bars built by third-party WordPress themes often wrap OpenTable parameters in non-standard div comboboxes that fail keyboard arrow navigation.
- Fixed-width 340px embed containers with scrolling="no" clip time-slot buttons on 320px mobile screens (WCAG 1.4.10 Reflow).
- Direct links to the hosted OpenTable reservation flow outperform custom JS wrapper modals on keyboard focus reliability.
Breakdown
| Integration Method | Iframe Title Risk | 320px Mobile Reflow | Keyboard Reliability |
|---|---|---|---|
| Standard Hosted Link / Button | None (no iframe) | Pass (responsive page) | High (native anchor + hosted form) |
| Official Script Widget (Unmodified) | Low if container untouched | Pass when fluid width | Moderate to High |
| Custom Theme Iframe Wrapper | High (often missing title) | Fails when width hardcoded | Low (double scrollbars & focus loss) |
| Custom JS Modal Popup Wrapper | Moderate | Mixed on iOS zoom | Low unless native <dialog> is used |
Failing markup and the fix
<div class="booking-embed">
<iframe src="https://widgets.example.com/reserve?rid=4021" scrolling="no"></iframe>
<div role="combobox" class="time-picker">7:30 PM</div>
</div><section aria-labelledby="reserve-heading">
<h2 id="reserve-heading">Reserve a Table</h2>
<iframe
title="Reserve a table by date, time, and party size"
src="https://widgets.example.com/reserve?rid=4021"
></iframe>
</section>Where do OpenTable embeds break on restaurant websites?
In hospitality demand letters, reservation flows sit right beside PDF menus as primary targets because an inaccessible booking widget blocks a guest from securing a table. Most failures we observe occur at the boundary between the restaurant theme and the embedded widget rather than on OpenTable servers.
Designers frequently wrap the OpenTable script inside a custom popup div with an unfocusable SVG close icon, or paste an iframe snippet without a title attribute and set scrolling="no". Under WCAG 2.2 AA, disabling iframe scrolling clips enlarged text at 200% zoom.
Should restaurants embed an iframe or link directly to the booking flow?
When a restaurant theme cannot guarantee a native HTML dialog wrapper and 320px responsive width, placing a high-contrast link button ("Reserve a Table on OpenTable") or using native HTML date and party-size selects before handing off to the booking URL avoids cross-origin focus traps altogether.
Questions
Why does Deque axe-core flag embedded booking iframes?
Rule frame-title (WCAG 4.1.2) requires every iframe to carry a non-empty, human-readable title attribute so screen-reader users know whether an embedded frame is a reservation form, a map, or an ad.
Has a vendor release fixed something above? Request a free re-test or read how we test.