Accessibility

We design and build WineUp to work with keyboards, screen readers, browser zoom and small restaurant screens. Accessibility is reviewed as part of development, not added afterwards.

Our engineering target and best-practice standard is WCAG 2.2 Level AA. WineUp is not certified as WCAG 2.2 AA conformant — no qualified external audit has established that. We state the standard as a target, not a certification.

• Semantic HTML and a coherent heading hierarchy.
• Keyboard navigation across all interactive functionality, with visible focus states.
• A skip-to-content link at the start of every page.
• Accessible dialogs (age acknowledgement, pairing modals, sensitive actions) with roles and labels.
• Form labels and error messages connected to their inputs.
• Sufficient text/background contrast; state is never communicated by colour alone.
• Browser zoom to 200% and responsive reflow without loss of essential functionality.
• Alt text on meaningful images; decorative images are hidden from assistive technology.
• Correct language attributes for English and Spanish content.
• Reduced-motion support wherever animation exists.
• Generous touch targets for in-restaurant mobile use.

• Content uploaded by restaurants (menus, photos, descriptions) may lack adequate alternative text; we do not control that content.
• Recommendations are a vertical list (no longer a carousel) and filtering announces the number of results; each card is read when you navigate to it rather than on every filter change.
• Automated axe-core checks run against the real pages (home, register, login, dashboard, menu, wines, pairings, settings and the guest experience). They do not replace a full manual screen-reader audit, which is still outstanding.
• QR PDF exports are canvas-generated documents and do not include structural tagging.
• We do not use an accessibility overlay or widget — we prefer fixing the underlying code.

If you encounter an accessibility barrier, email wineuptech@gmail.com with the subject “Accessibility”, telling us the page, your browser and the assistive technology you use. We respond and try to provide an alternative way to access the information (for example, menu and recommendations by email or on paper via the restaurant).

September 13, 2026