Inclusive by Design
Accessibility
We are committed to making our website accessible to everyone, regardless of ability or technology.
Our Commitment
Kei Concepts is committed to ensuring that our website is accessible to all users, including those with disabilities. We believe that every guest — whether dining in our restaurants or browsing our website — deserves an inclusive, barrier-free experience.
We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level. These guidelines are widely recognized as the international standard for web accessibility and are designed to make content perceivable, operable, understandable, and robust for all users.
Continuous Improvement
Accessibility is not a one-time effort. We are committed to continuous improvement. Our goal is to achieve and maintain a Lighthouse accessibility score of 100 across all pages. We regularly audit our site using automated tools and manual testing, and we address any issues as quickly as possible.
Our development team follows accessibility best practices as part of our standard workflow, including semantic HTML, ARIA attributes, keyboard navigation support, sufficient color contrast, and screen reader compatibility.
Third-Party Content
Our website may include third-party content or link to external services (such as reservation platforms, delivery services, and social media) that are outside our control. While we encourage these partners to maintain accessibility standards, we cannot guarantee the accessibility of their content.
What We Do
- Semantic HTML structure with proper heading hierarchy
- ARIA labels and landmarks for screen reader navigation
- Keyboard-accessible navigation and interactive elements
- Sufficient color contrast ratios meeting WCAG AA standards
- Focus indicators visible on all interactive components
- Alternative text for all meaningful images
- Responsive design that works across devices and zoom levels
- Reduced motion support for users who prefer minimal animation
- Skip navigation links for efficient keyboard browsing
- Form labels and error messages that are programmatically associated
Known Limitations
We work hard to keep this site accessible, and we honestly disclose the following limitations:
- Non-English brand words: Some of our restaurants use words from Italian (Ristorante) or Japanese (Izakaya). These words appear within English text without
langattributes. Screen readers that adjust pronunciation by language may not switch languages for these single words. This is a Level AA “Language of Parts” limitation (SC 3.1.2) that we’ve accepted to keep editor workflows simple. - Third-party embeds: Reservation, ordering, and map services (Toast, OpenTable, DoorDash, UberEats, Google Maps) open in new tabs or as embeds. We link to them clearly but cannot guarantee the accessibility of their content.
- Development preview tools: Internal preview and design tools at
/preview/*are not user-facing and are excluded from our a11y conformance testing.
How We Test
Our accessibility conformance is verified on every code change by:
- Automated linting:
eslint-plugin-jsx-a11yruns on every pull request and blocks merges on known-bad patterns (missing alt text, inaccessible form labels, inaccessible interactive elements). - Automated runtime checks:
axe-coresweeps every public and admin route using Playwright, checking against WCAG 2.1 Level A and Level AA rules. - Lighthouse CI: Google Lighthouse tests every page at build time and blocks merges below an accessibility score of 0.95.
- Periodic manual audits: We walk through key user flows using VoiceOver and NVDA screen readers, plus keyboard-only navigation, to catch quality-of-experience issues that automated tests cannot.
Report an Accessibility Issue
If you encounter any accessibility barriers on our website, we want to know about it. Your feedback helps us improve the experience for everyone. Please contact us with a description of the issue and the page where you encountered it.
Attn: Accessibility
Huntington Beach, CA 92647
When reporting an issue, please include the web address (URL) of the page, a description of the problem, and what assistive technology you were using (if applicable). We aim to respond to all accessibility feedback within two business days.
This accessibility statement was last updated on March 20, 2026.