Accessibility Conformance Report
OrderAble VPAT
WCAG 2.1 Edition · Report Date: May 4, 2025 · Prepared by: OrderAble Inc.
Product Information
- Product Name
- OrderAble Restaurant Ordering Platform
- Version
- 1.0
- Product Description
- White-label web-based restaurant ordering system
- Contact
- accessibility@orderable.app
- Report Date
- May 4, 2025
- Conformance Level Claimed
- WCAG 2.1 Level AA (Substantial)
Conformance Summary
41
Supports
0
Partial
0
Does Not Support
12
Not Applicable
Level A Success Criteria
| SC | Title | Status | Notes |
|---|---|---|---|
| 1.1.1 | Non-text Content | Supports | All interactive images and icons carry aria-label or aria-hidden. Menu item photos include descriptive alt text. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | Not Applicable | No prerecorded audio-only or video-only content. |
| 1.2.2 | Captions (Prerecorded) | Not Applicable | — |
| 1.2.3 | Audio Description or Media Alternative | Not Applicable | — |
| 1.3.1 | Info and Relationships | Supports | Semantic HTML5 elements used throughout. ARIA roles supplement where needed (tablist, group, live). |
| 1.3.2 | Meaningful Sequence | Supports | DOM order matches visual order across all pages. |
| 1.3.3 | Sensory Characteristics | Supports | Instructions do not rely on shape, size, color, or position alone. |
| 1.4.1 | Use of Color | Supports | Color is never the sole means of conveying information. Error states include text labels. |
| 1.4.2 | Audio Control | Not Applicable | No auto-playing audio. |
| 2.1.1 | Keyboard | Supports | All functionality operable via keyboard. Tab, Enter, Space, arrow keys tested. |
| 2.1.2 | No Keyboard Trap | Supports | Focus is never trapped. Stripe payment iframe traps focus internally per their ARIA dialog spec. |
| 2.1.4 | Character Key Shortcuts | Not Applicable | No single character keyboard shortcuts implemented. |
| 2.2.1 | Timing Adjustable | Not Applicable | No time limits on user actions. |
| 2.2.2 | Pause, Stop, Hide | Not Applicable | No moving, blinking, or auto-updating content. |
| 2.3.1 | Three Flashes or Below | Supports | No content flashes more than three times per second. |
| 2.4.1 | Bypass Blocks | Supports | Skip to main content link is the first focusable element in the ordering layout. Visible on focus. |
| 2.4.2 | Page Titled | Supports | All pages have descriptive <title> elements. |
| 2.4.3 | Focus Order | Supports | Focus order follows logical reading order. Skip link → cart → order type → heading → category nav → items. |
| 2.4.4 | Link Purpose (In Context) | Supports | All links and buttons have descriptive labels or accessible names. |
| 2.5.1 | Pointer Gestures | Supports | All functionality uses single-pointer activation. |
| 2.5.2 | Pointer Cancellation | Supports | Button actions trigger on mouseup/pointerup, not mousedown. |
| 2.5.3 | Label in Name | Supports | Visible label text is included in or matches the accessible name. |
| 2.5.4 | Motion Actuation | Not Applicable | No functionality requires device motion. |
| 3.1.1 | Language of Page | Supports | lang="en" set on <html> element. |
| 3.2.1 | On Focus | Supports | No context changes triggered on focus. |
| 3.2.2 | On Input | Supports | Form submission requires explicit button activation. |
| 3.3.1 | Error Identification | Supports | Form errors are identified in text and associated with the relevant field via aria-describedby. |
| 3.3.2 | Labels or Instructions | Supports | All form fields have visible labels. Required fields are labeled. Phone field includes hint text. |
| 4.1.1 | Parsing | Supports | HTML is valid. No duplicate IDs. No missing end tags. |
| 4.1.2 | Name, Role, Value | Supports | All UI components have programmatically determined names, roles, and values. ARIA states kept in sync with UI state. |
Level AA Success Criteria
| SC | Title | Status | Notes |
|---|---|---|---|
| 1.2.4 | Captions (Live) | Not Applicable | — |
| 1.2.5 | Audio Description (Prerecorded) | Not Applicable | — |
| 1.3.4 | Orientation | Supports | Content renders correctly in both portrait and landscape. |
| 1.3.5 | Identify Input Purpose | Supports | Name and phone fields carry appropriate autocomplete attributes. |
| 1.4.3 | Contrast (Minimum) | Supports | All body text uses #111 on white (≥15:1). Gray helper text uses gray-600 (#4B5563, 4.63:1 ≥ 4.5:1 required). |
| 1.4.4 | Resize Text | Supports | Text resizes up to 200% without loss of content or functionality. |
| 1.4.5 | Images of Text | Supports | No images of text used. |
| 1.4.10 | Reflow | Supports | Single-column layout at 320px width; no horizontal scroll required. |
| 1.4.11 | Non-text Contrast | Supports | UI components (buttons, form borders) meet 3:1 contrast against adjacent colors. |
| 1.4.12 | Text Spacing | Supports | No CSS overrides prevent user-defined text spacing. |
| 1.4.13 | Content on Hover or Focus | Supports | Tooltip content is dismissible and persistent while hovered. |
| 2.4.5 | Multiple Ways | Supports | Users can navigate via header links, in-page buttons, and direct URL. |
| 2.4.6 | Headings and Labels | Supports | Heading hierarchy is consistent: h1 per page, h2 for sections. Form labels are associated via htmlFor. |
| 2.4.7 | Focus Visible | Supports | All interactive elements show a visible focus indicator (focus-visible outline). |
| 2.4.11 | Focus Not Obscured (Minimum) | Supports | Focused elements are not fully hidden by sticky headers. |
| 2.5.7 | Dragging Movements | Not Applicable | No drag operations. |
| 2.5.8 | Target Size (Minimum) | Supports | Add-to-cart buttons are 44×44px. Cart quantity controls are 44×44px. |
| 3.1.2 | Language of Parts | Not Applicable | No multi-language content within pages. |
| 3.2.3 | Consistent Navigation | Supports | Header navigation is consistent across all restaurant ordering pages. |
| 3.2.4 | Consistent Identification | Supports | Components with the same function are labeled consistently. |
| 3.3.3 | Error Suggestion | Supports | Error messages describe what the user must correct (e.g., "Name is required"). |
| 3.3.4 | Error Prevention | Supports | Checkout order submission is reviewable before final confirmation. Order total is displayed prominently. |
| 4.1.3 | Status Messages | Supports | Cart announcements use aria-live="polite" region. "Garlic Bread added. Cart: 1 item." announced without focus movement. |
Legal Disclaimer
This document is provided for informational purposes. OrderAble Inc. makes no warranty, express or implied, regarding the accuracy of this report. Conformance claims reflect the state of the product as of the report date and may change as the product evolves. Restaurant operators who configure custom content (menu descriptions, photos) are responsible for the accessibility of that content per the Terms of Service.
Get your ACR on file
Your ordering system, fully documented.
This report is included with every Orderability subscription. Already a customer and need a standalone copy for procurement, legal, or an enterprise client? Purchase yours here.
$4,997one-time
Delivered instantly · PDF + live URL
Get ACR report — $4,997
Secure checkout via Cardcom