Auto-playing hero carousels
Slideshows that rotate automatically with no way to stop them. Controls are unlabeled. Content inside non-active slides is completely hidden from screen readers.
The carousel auto-rotates with no pause button, no labeled controls, and content trapped inside hidden slides.
- No visible pause button — instant Level A failure
- Slide arrows and dots have no accessible names
- Non-active slide content is hidden from screen readers
- Users with vestibular disorders can't stop the motion
Remi uses a single hero image. All content is always visible and reachable.
- Static hero — no auto-play, no animation, no motion
- All page content accessible in reading mode, top to bottom
- Nothing to pause, no arrows to label, no hidden content
Navigation links coded as buttons
Screen readers tell users to “press” a button when they should “follow” a link. The user expects an action but gets a page navigation instead.
Links use role="button" — screen readers describe them incorrectly, confusing users about what will happen.
- Users expect buttons to do something, links to go somewhere
- The mismatch between role and behavior breaks trust
- One of the most common violations on template sites
Links are links. Buttons are buttons. Semantic HTML, no role overrides.
- Navigation uses <a> tags — announced as links
- Actions use <button> elements — announced as buttons
- Screen readers describe exactly what each element does
More violations baked into the platform
Birch & BarrelKeyboard users locked out
Interactive elements use tabindex="-1", removing them from keyboard navigation. Users who can’t use a mouse are locked out of the site.
Remi: Every element in natural tab order. Visible focus rings. Skip link on every page.
Clickable elements with no names
Logos, arrows, icons — all clickable, none labeled. Screen reader users have no idea what anything does.
Remi: Every interactive element has a descriptive accessible name.
Maison NoirForms without labels
Placeholder text is not a label — it disappears when you type and screen readers often skip it.
Remi: Every form field has a visible, persistent label linked to its input.
Low contrast text
Text over images, footer links, and UI elements below the 4.5:1 minimum. Low-vision users can’t read essential content.
Remi: All 5 themes contrast-audited. Solid white hero text with text-shadow. Never reduced opacity.
This is already happening
Sued by a blind customer who couldn’t order pizza online. The case went to the Supreme Court. Domino’s lost. The court ruled websites are public accommodations under the ADA. Every restaurant website is now a potential target.
Sued in January 2024 under the ADA and NYC Human Rights Law for inaccessible menus and ordering. This was their second accessibility lawsuit.
of businesses that get sued for web accessibility get sued again. The violations are in the platform code — switching themes or redesigning doesn’t fix them. You have to switch platforms.
Compare Remi to your current platform
Side-by-side feature, price, and accessibility breakdowns. Real numbers, no marketing math.
Remi vs
BentoBox
$149–249/mo + $500–1,000 setup fees $69/mo, flat. No setup fees.
BentoBox starts at $149/mo with a $500 setup fee. Remi is $69/mo flat. Both are restaurant-specific. What you actually get for the difference.
Read comparison →
Remi vs
Square Online
$0–79/mo + 2.9% + $0.30 per transaction $69/mo flat. No transaction take.
Square Online's free tier looks unbeatable until the 2.9% + $0.30 per transaction adds up. Here's the math at real restaurant volumes.
Read comparison →
Remi vs
Squarespace
$23–49/mo (most restaurants land at ~$45–70/mo all-in) $69/mo, flat
Squarespace looks beautiful and ships with menu friction. Real prices, where each platform wins, and what it takes to migrate to a restaurant-specific tool.
Read comparison →
Remi vs
Toast
$69/mo base, $250–500/mo typical with modules $69/mo, flat. Website only.
Toast's $69 base looks identical to Remi. The reality is feature stacking that pushes most restaurants to $250–500/mo. The honest comparison.
Read comparison →
Remi vs
Wix
$17–32/mo listed (~$60–100/mo real) $69/mo, flat
Wix is cheaper on paper and more expensive in reality. Here's what restaurants actually pay, and where Wix falls short on menus, accessibility, and lock-in.
Read comparison →
Remi vs
WordPress
Free software, $30–200+/mo all-in $69/mo, flat. Hosted, updated, compliant.
WordPress is free. The maintenance, hosting, plugins, and accessibility liability are not. The honest comparison for restaurants.
Read comparison →
Switch to a website that works for everyone
Remi builds accessibility into every page, every theme, every component. $69/mo — less than half what other platforms charge.