For everyone
Web accessibility
Accessibility is not a niche. It is the difference between a customer completing a form and giving up on it.
The usual picture of accessibility is a screen reader user, and that matters. But the larger group is quieter: people with weak eyesight, people using a phone in bright sunlight, people with unsteady hands, and anyone over about fifty reading small grey text on a white background.
Almost every accessibility failure we find comes down to one thing. Colour contrast. Light grey text, pale buttons, brand colours that pass on white and quietly fail on a tinted section behind them.
So we audit the colour tokens rather than the finished components, because fixing a token fixes every page at once. Every text colour on this site was checked against white and against all four tinted backgrounds before a single component was written.
What the work covers
Included in every accessibility project.
Contrast audited at token level
Each text colour tested against every surface it can appear on, not just the default white. That second check is the one people skip.
Full keyboard operation
Every link, button, menu and form reachable by keyboard, with a focus outline you can actually see.
Semantic markup
Real headings in order, real buttons, real labels. A screen reader announces the page correctly because the page is built correctly.
Descriptive alternative text
Written to describe what the image shows and why it is there. Decorative images marked as decorative rather than described pointlessly.
Reduced motion respected
Every animation on this site checks the operating system setting and stops. Motion sensitivity is real and the fix is one media query.
Forms that explain themselves
Labels attached properly, errors described in words next to the field, and never colour alone to indicate a problem.
No themes, no page builders, no plugin stacks
Every site written from scratch, starting from almost nothing and adding only what the pages need. The whole speed recipe is published, not kept secret.
Read the recipe →AI, used properlyWe use AI to go faster, not to decide
It writes the mechanical parts. It never chooses the architecture, the performance budget, or a single fact about your business. Everything is reviewed by the person who will maintain it.
Where we draw the line →Questions
Asked often enough to answer here.
If yours is not here, the general questions page covers how we work, or you can just ask.
Is accessibility legally required in India?
The Rights of Persons with Disabilities Act 2016 requires accessible information and services, and government sites follow the GIGW guidelines. Private businesses face less direct enforcement than in the US or EU. We build to WCAG AA regardless, because the commercial argument stands on its own.
Will an accessibility overlay widget fix this?
No. Those widgets sit on top of the problem and are widely criticised by the disabled users they claim to serve. They also add weight to every page. The fix is in the markup and the colours, and it is not expensive when done during the build.
Does accessible design have to look plain?
Not at all. This site is built to WCAG AA and it is full of colour and motion. The constraints are on contrast and on respecting a reduced motion setting, and neither one limits the design in practice.
Related work we do
All 16 servicesCustom web development
Websites written from scratch for one business, rather than a theme bent into shape until it almost fits.
Next.js development
The framework we reach for first, and the one we know well enough to know when it is the wrong answer.
Bun and Node.js backends
The part nobody sees, which is exactly why it has to be right.
Want this for your business?
Tell us what you have now and what is not working. We will tell you what we would do and what it would cost.