Legal PagesAccessibility Statement
HostKit accessibility commitment, WCAG target, known limitations, reporting form, response timeline, and restaurant content responsibilities.
Version 2026.06.07 | Effective June 7, 2026 | Last updated June 7, 2026Commitment and standard
- HostKit targets WCAG 2.2 AA required, selected AAA improvements where feasible for public pages, checkout, restaurant menu pages, dashboard workflows, and support paths.
- HostKit designs for keyboard access, visible focus, sufficient contrast, semantic landmarks, labels, error messages, reduced motion, screen-reader compatibility, responsive reflow, and accessible forms.
- Selected WCAG AAA improvements may be implemented where feasible, but WCAG AA remains the required baseline.
Known limitations
- Restaurant-uploaded content, third-party widgets, third-party embeds, and legacy integrations may require additional remediation by the restaurant or vendor.
- AI-generated or restaurant-entered descriptions, allergen statements, images, and menu content must be reviewed by the restaurant for accuracy and accessibility.
- HostKit does not promise that every third-party service or restaurant-provided asset is fully accessible.
Reporting accessibility issues
- Accessibility issues can be reported through the accessibility form or accessibility@hostkitapp.com.
- HostKit aims to acknowledge accessibility reports within 5 business days and provide a remediation timeline when practical.
- Reports should include the page URL, assistive technology used, browser/device, issue description, and contact information for follow-up.
