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
Ayaz Ata Türkmen is a web developer based in Istanbul, building and releasing production websites since 2019, currently alongside continuing education.
Allcess is the current focus. The crawler, the reporting pipeline and this site are designed and maintained solo, and that scope is deliberate: a product is easier to stand behind when it claims only what it can be shown to do. It is also why this site documents what automated scanning misses rather than quietly leaving that out.
Interests outside of work include music and ice hockey.
Project
What Allcess is trying to do
The European Accessibility Act has applied to e-commerce in the EU since June 2025, and 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.
01 / 06
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
02 / 06
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
03 / 06
It changes nothing on your site
No script tag, no plugin, no overlay. Pages load in headless Chrome the way a visitor's browser would, the rendered result is read, and nothing is written back. The scanner needs no credentials for your store.
Read only, no install
04 / 06
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
05 / 06
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
06 / 06
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.
0 findings on allcess.com
Styling
The design system
Warm orange on near white, or on near black, and very little else. No illustration, no stock photography, no gradients doing the work that structure should do.
DORFic, loosely
Daylight, orange, red, futurism, graphic. A subset of the Frutiger Aero family: warm, high contrast, confident about edges. It gives the product an opinion without needing illustration or stock photography, neither of which a scanner has any business showing you.
Titillium Web
A humanist sans with squared terminals and slightly clipped corners. It reads as technical without going full monospace, which suits a tool that reports findings. Weights 400 through 900 are loaded; the headings sit at 600.
The skewed bar
The mark is a parallelogram sheared twelve degrees. It repeats at three scales: the logo lockup, the small bar in front of every section label, and the clipped top-left corner cut out of the primary buttons. One shape doing the work a whole icon set usually does.
The orange full stop
Every section heading ends in a period set in the brand orange. It is a small thing and it is most of why the type feels deliberate rather than default. It carries aria-hidden so a screen reader never announces a stray full stop.
Contrast is a build constraint
Every pairing was checked against WCAG AA for both themes before it shipped. That is why there are two oranges: a dark one for text on light backgrounds, a light one for text on dark. The brand orange itself never carries small text.
Motion that stays out of the way
Sections reveal on scroll, panels lift on hover, the progress bar tracks the page. All of it is short and none of it blocks reading. Anything decorative is hidden under prefers-reduced-motion rather than merely slowed down.
Get started
See what's actually on your site
Add a URL and get a scan back in minutes. No plugin, no code on your site, no sales call.
- 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