You will get a Next.js accessibility fix: axe-core 0, Lighthouse a11y 100, tested
Project details
I take a Next.js site to zero axe-core violations and Lighthouse Accessibility 100, then lock it with tests so it stays there. Written findings first (severity, reproduction, fix), then the code fixes: semantic landmarks, contrast tokens, focus order, keyboard reachability, form labels, media alternatives, ARIA only where native HTML can't. Proof is a before/after scorecard per route and a test that fails if the fix is removed. Built for agencies and teams shipping Next.js for state/local government, schools, hospitals, or anyone reading the ADA Title II web rule (WCAG 2.1 AA; compliance April 26, 2027 for populations of 50,000+ and April 26, 2028 below that — it applies even when a vendor built the site). Lighthouse 90+ and axe-core 0 are ship gates on everything I deliver; my own production surfaces measure a11y 100 / axe 0 on the live URL. Remote and async, written findings before any code changes; fixes land in your repo on a branch with tests, you merge.
Programming Languages
HTML & CSS, JavaScript, TypeScriptCoding Expertise
Cross Browser & Device Compatibility, Performance Optimization, W3C Markup Validation ServiceWhat's included
| Service Tiers |
Starter
$1,500
|
Standard
$3,500
|
Advanced
$6,500
|
|---|---|---|---|
| Delivery Time | 5 days | 7 days | 10 days |
Number of Revisions | 1 | 2 | 2 |
Bug Investigation | |||
Fix Documentation | |||
Detailed Code Comments |
Frequently asked questions
About Jonis
Next.js Accessibility & Production Engineer (axe-core 0, a11y 100)
San Antonio, United States - 12:41 pm local time
What I do
• Accessibility + Lighthouse remediation for Next.js/React sites — audit, fix, prove (before/after scorecard per route), hand off tests. WCAG 2.1 AA is the target the ADA Title II web rule sets for public-sector sites and their vendors.
• Production-readiness audits — written findings with severity, reproduction, and the fix specified.
• AI agents and MCP servers in production — Claude API, JSON-RPC tool endpoints, fail-closed error handling, tests that can fail.
• Monthly keep-it-green check — nightly Lighthouse + axe on every route, written report, regressions fixed.
Proof you can check in two minutes
Two hosted work samples with the measurements attached (linked from my portfolio section) — the page and both samples measure Lighthouse Accessibility 100 and axe-core 0 on the live URL. Founder-engineer at Bonis Systems LLC: five production Next.js/TypeScript surfaces and two MCP servers running on Google Cloud Run today. Lighthouse 90+ and axe-core 0 are ship gates on everything I deliver, not aspirations.
How I work
Remote and async, US Central time. Written findings before any code changes. Fixes land in your repo on a branch with tests; you merge. Focused engagements — your work is not queued behind three others.
Stack: Next.js (App Router), TypeScript, React, Node.js, Python, PostgreSQL/Prisma, Tailwind, Playwright/axe-core, Lighthouse CI, Google Cloud Run, Vercel, Stripe.
Steps for completing your project
After purchasing the project, send requirements so Jonis can start the project.
Delivery time starts when Jonis receives requirements from you.
Jonis works on your project following the steps below.
Revisions may occur after the delivery date.
Audit
Measure every in-scope route with Lighthouse and axe-core; written findings with severity, reproduction, and the fix specified.
Fix
Code changes on a branch in your repo — landmarks, contrast, focus order, keyboard, labels, media alternatives — each with a regression test.