Skip to content

Demo rebuild · East Austin, TX

Brasa: Wood-Fired, rebuilt.

Wood-Fired · $$$

Live-fire restaurants all make the same website: black background, orange accents, a video of flames, and text so dark it's practically smoke. It looks the part and reads terribly. Brasa is our rebuild — proof that a dark, loud, fire-driven brand can pass WCAG 2.2 AA without losing a degree of heat.

An honest note: Brasais a fictional restaurant. The “before” below is a composite of the most common findings from scans of real sites for this kind of restaurant — not a real place, and not a real audit. The “after” is very real: it’s the live demo at itsremi.app/r/brasa, running on Remi.

The typical old site: what our scanner would flag

Sites for wood-firedrestaurants tend to fail in the same ways. Here’s the composite, rated the way our scanner rates findings — and who each one locks out.

  • Serious

    Gray-on-black text fails minimum contrast

    The site goes dark to match the hearth, but the body text is a mid-gray on near-black that falls short of the 4.5:1 ratio WCAG requires. In a dim restaurant or on a sunny patio — which is exactly where guests read menus — it's illegible for anyone with low vision.

  • Moderate

    A fire video loops with no way to stop it

    Flames autoplay behind the hero on every page load: no pause button, no respect for the guest's reduce-motion setting. Atmospheric for most; nauseating for visitors with vestibular disorders.

  • Critical

    The menu is photos from the office printer

    The menu is a set of scanned images. Screen readers read nothing, the text can't be searched or translated, and zooming turns it to mush. The most damaging barrier a restaurant site can ship — and a known ADA lawsuit trigger (WCAG 1.4.5, Images of Text).

  • Critical

    The “Reserve” button isn't a button

    It's a styled page element with a click handler, so keyboard-only guests can never focus or press it — and screen readers announce nothing actionable. The single most important control on the site is unreachable for exactly the guests who need it most.

  • Moderate

    No “skip to content” link

    Keyboard users tab through the entire navigation on every page just to reach the menu. Multiply that by every page and every visit.

The Remi rebuild

The rebuilt Brasa keeps the personality — the palette, the type, the mood — and removes the barriers. Accessible to WCAG 2.2 AA by default, and owned by the restaurant: the domain, the content, the guest relationships.

Dark done right

Brasa keeps the near-black room and ember-orange highlights, but the ink is a warm off-white clamped to pass WCAG 2.2 AA on every surface. Moody and readable aren't opposites — you just have to check the math.

Fire that respects the guest

Motion honors the device's reduce-motion setting, nothing autoplays sound, and every moving element can be paused. The atmosphere comes from the palette and photography, not forced animation.

A menu you can actually read

Every cut, every side, every price is real text — with the “for two” and “ask for the catch” notes intact. Screen readers read it, search indexes it, and a guest can zoom it to 400% on a phone.

Real buttons, real keyboard path

Booking and ordering are built from actual buttons and links with visible focus, a skip link, and a tab order that makes sense — the whole site works without a mouse.

Click through the live demo

One hearth, a short menu, no shortcuts. The rebuild works the same way — loud where it should be, legible everywhere it counts.

Your restaurant next

Your site has its own version of this list.

Scan it free and see the findings in plain English. Then we rebuild it — migration is free, accessibility is built in to WCAG 2.2 AA, and you own everything: the domain, the content, the guest list.

Scan your site free →See pricing

Take online orders through Square and your whole site is free — $0/mo, no bill, ever. Dine-in only? A flat $99/mo founding price (regular $149), reservations included.

More rebuild stories