SGD Labs
← All posts
Build-in-publicNovember 10, 2026 · 6 min read

A WCAG audit on a small SaaS app: what failed

I ran a WCAG audit on a small SaaS app I build alone, LinkinUp, and it failed in ways I didn’t expect. The default button colour every new user gets didn’t meet contrast. Two modals, one of them “delete my account”, weren’t real dialogs. A keyboard user had no way to skip the navigation.

This is the full list, with the numbers, the fixes and the parts that are still open. No victory lap. If you run a small SaaS and you’ve been putting off an accessibility pass, this is roughly what you’ll find.

Nobody made us do this

The EU’s Accessibility Act has applied since 28 June 2025 (e-include.eu). It also says, in Article 4(5), that “microenterprises providing services shall be exempt” from its accessibility requirements (Directive 2019/882, Art. 4). A microenterprise is one with “fewer than 10 persons” and turnover or a balance sheet “not exceeding EUR 2 million” (Art. 3).

One engineer is comfortably under that line. I’m not a lawyer, and this isn’t advice on whether the law applies to you. The point is that the exemption was never the reason to skip it. LinkinUp is a link-in-bio page for creators. If someone can’t read a musician’s bio or reach their tour dates, the product failed at its one job, legal or not.

How the audit was run

The audit targeted WCAG 2.1 level AA and ran against a local production build with seeded test accounts, third-party scripts blocked:

  • axe-core through Playwright, at a phone size (375×812) and a desktop size (1440×900), on every page.
  • Lighthouse, mobile and desktop.
  • Scripted keyboard passes: tabbing through each page, opening and closing dialogs, reordering links without a mouse.
  • A contrast matrix: every theme, all 20 profile gradients and every tint overlay, computed rather than eyeballed, because a single-page scan only ever sees the default theme.

These are lab numbers. They’re good for before-and-after comparisons, not as a claim about production.

What the WCAG audit found

Contrast, starting with the default. The out-of-the-box profile button colour, blue with white text, came in at 4.09:1. WCAG 2.1 asks for 4.5:1 for normal text (W3C, SC 1.4.3). So every profile that never touched its appearance settings failed. The app’s own primary buttons were worse, at 3.68:1. On dark-page gradients, secondary text (bio, username, empty states) failed on 15 of 20 gradients, and primary text on 6. In total axe flagged 202 contrast nodes across 18 pages.

Controls with no name. 56 buttons on 15 pages had nothing for a screen reader to announce: the drag handle on every link row, the profile carousel arrows, password show/hide toggles, the mobile menu. Add unlabelled colour inputs, admin filter dropdowns and icon-only social links on top.

Modals that weren’t dialogs. The delete-account and cookie-preference modals were hand-built overlays. Focus stayed on the button behind them, Tab walked straight out into the page, and Escape did nothing. A screen-reader user could reach account deletion with no announced context. That one bothered me most.

No way to skip ahead. No skip link, so the first Tab stop on the home page was the beta banner’s feedback button. Ten pages had no main landmark at all, and the dashboard had two unlabelled navigation regions.

Drag and drop that talked in UUIDs. Keyboard reordering technically worked, but the announcements read out raw database IDs (“Draggable item 589f7960-… was moved over…”), and there was no way to reorder without dragging.

No reduced-motion support. 29 files used an animation library, and none of them respected the operating system’s “reduce motion” setting.

The Lighthouse accessibility scores looked fine before any of this was fixed, mostly in the high 80s and 90s. That’s the trap: the score samples, and it never sees the gradients and themes you didn’t render.

What got fixed, in numbers

Ten commits, one per finding, merged on 26 September 2026:

  • axe violations: 660 → 0 across 44 page-and-viewport checks.
  • Contrast nodes: 202 → 0. A small contrast utility now adjusts a profile’s colours at render time, keeping the hue and moving only as far as needed, so no stored user data had to change. The appearance picker warns when a choice fails, but doesn’t block it.
  • Average Lighthouse accessibility: 92 → 99 on mobile, 95 → 99 on desktop.
  • Dialogs: all three hand-built modals, delete account, cookie preferences and Pro upgrade, were rebuilt on a proper dialog component. Focus moves in, stays in, Escape closes, and focus returns to the button that opened it. The delete dialog opens with Cancel focused.
  • Navigation: a skip link on every route, a main landmark everywhere, labelled navs, fixed heading order.
  • Reordering: Move up and Move down buttons as a non-drag path, with announcements that use the link’s title.
  • Motion: the whole app now follows the reduce-motion setting, and the scrolling marquee on the home page has a pause button.

The browser QA pass afterwards caught one more, older bug: on an 800px-tall screen, the cookie dialog’s Save and Accept buttons sat below the bottom of the window, unreachable. Fixed in the same branch.

Writing this post turned up one more: Google Analytics was loading, and setting its cookies, before anyone made a cookie choice. It now waits until a visitor accepts.

What’s still open

  • Background images. Text over a user’s uploaded photo can’t be checked automatically. Gradients and solid colours are handled; photos aren’t.
  • The internal style-guide page still has contrast findings. It’s a developer page, not something users see, but it’s open.
  • Admin analytics under-counts once views pass 1,000 in the window. That one is a performance and correctness problem rather than accessibility, and it’s tracked separately.
  • ATSResu.me hasn’t had this audit. It got one accessibility fix in its September QA pass (an accordion that hid its state from screen readers and had no focus ring). A full pass is still to do.
  • This isn’t a conformance claim. Zero axe violations means the automated checks pass. It doesn’t mean a disabled person has used every flow and found it fine.

What I’d tell another small SaaS

  1. Audit your defaults first. The worst finding wasn’t an edge case. It was the colour every new account starts with.
  2. Render your themes. If users can pick colours, compute contrast for every combination. A scan of one page sees one theme.
  3. Use the dialog component you already have. Every broken modal here was hand-rolled next to a working dialog primitive that was already installed.
  4. Fix the method before the numbers. The audit had to correct two of its own early figures because the first runs weren’t like-for-like. Measure before and after the same way, or the deltas are fiction.
  5. Write down what you didn’t fix. An open list is more useful to your future self than a score.

That’s the build-in-public deal from the first post: the mistakes go in too. If you want to see what’s being built, the products are on the home page, and LinkinUp is the one this post is about.

Sources

Written by the builder

SGD Labs is one senior engineer shipping affordable, well-designed SaaS tools solo — no growth team, no seed round. These posts are the running commentary. More about SGD Labs.

Built by the same hands

The products this blog is about — go kick the tires.