About
Who makes this, and how it is made
Three things worth knowing: the person behind it, what the product is actually trying to do, and the design system holding the interface together.
Developer
The person behind it
The whole point of the internet is to connect people, and to let them communicate regardless of physical borders. Shutting people with disabilities out of that breaks the internet's most basic rule. If anyone should find the internet accessible, it is them.
Allcess exists so that small businesses, which make up so much of today's internet, are accessible to them too.
Project
What Allcess is trying to do
The European Accessibility Act may apply to e-commerce in the EU depending on the size and location of the business, and very small businesses can be exempt. Most small stores have no way to find out where they stand that does not cost more than the store makes in a month. Allcess is the cheap, honest first step: find what is broken, say what it takes to fix, and stop short of promising anything a scanner cannot deliver.
One problem, narrowly
Small stores get told they have an accessibility problem and handed a list of hundreds of findings. Allcess crawls the storefront, then rolls those findings up by the change that fixes them, so the list becomes work you can actually start.
478 findings → 5 real fixes
It refuses to claim compliance
Automated testing catches somewhere between a third and a little over half of real accessibility problems. Anything promising a compliant site from a scan is selling something. The FTC fined an overlay vendor $1M over exactly that claim.
Evidence of effort, not a certificate
It changes nothing on your site
Pages load in headless Chrome the way a visitor's browser would. Allcess reads what renders, writes nothing back, and never needs a login to your store.
Read only, no install
Built on the standard engine
Findings come from axe-core, the same rules engine inside Chrome DevTools and most professional audit tooling. The work Allcess adds is grouping, severity ordering, and writing the fix in language a shop owner can act on.
axe-core + headless Chrome
The stack
Next.js on the App Router with React Server Components, Postgres through Prisma, Auth.js for sessions, Tailwind for styling and Framer Motion for the parts that move. Puppeteer drives the crawler. Reports render to PDF server side.
Next.js 16 · Prisma 7 · Postgres
It scans itself
Every page of this site is run through the same scanner, in both themes. It has caught real problems here: a primary button under the contrast threshold, a list whose semantics an animation wrapper had broken, a missing landmark. All fixed before shipping.
Every page, both themes
Styling
The design system
Warm orange on near white or near black, with structure and spacing doing the work that decoration usually does.
Restraint over decoration
Orange on near white, or on near black, and very little else. Sections are separated by surface and spacing rather than ornaments, so the findings are always the loudest thing on the screen.
IBM Plex Sans
A grotesque drawn for engineering documentation: sober, legible at small sizes, with figures that line up in tables. Served from this domain rather than a font CDN. Rule IDs are set in its sibling, Plex Mono, because they are code.
The skewed bar
The mark is a parallelogram sheared twelve degrees. It appears at two scales: the logo lockup, and the small bar in front of each section label. One shape carrying the brand, so nothing else has to.
One scale for everything
Type steps up by roughly a major third with line heights on a 4px grid. Controls are 40px tall with a 6px radius; anything that contains other things gets 8px. A button on the pricing page and a button in the scan report are the same button.
Contrast is a build constraint
Every pairing was checked against WCAG AA in both themes before it shipped. That is why there are three oranges: the brand orange for the mark, a deeper one that white button labels clear 4.5:1 on, and a text orange tuned separately for light and dark backgrounds.
Motion that stays out of the way
Sections fade in once as they scroll into view, and controls answer a click by showing what changed. Under prefers-reduced-motion the decorative part is removed rather than slowed down.
Get started
See what's actually on your site
Add your store's address and have a full scan back in minutes.
- Crawls your whole storefront, not just the homepage
- Findings grouped by fix, not by page
- Fix guidance tailored to Shopify and WooCommerce
- A dated PDF record of every scan