Make it usable by everyone — and provably compliant
We audit and remediate websites, PDFs and EPUBs against the standards that actually get checked: WCAG 2.1 for the web, GIGW for Indian government sites, and EPUB Accessibility 1.1 for publishers. You get the fixes and the report that evidences them.
For: Government departments and PSUs, publishers selling into Europe, universities, and any business whose customers include disabled users
The problem we usually walk into
Accessibility is usually discovered as a blocker, not a plan — a government department told its site fails GIGW review, a publisher whose distributor now demands accessibility metadata, a company that realises its forms cannot be used with a screen reader. Then it becomes urgent and nobody local does the work.
See what this costs \u2192What's included
Audit against the real standard
WCAG 2.1 A and AA, GIGW for government sites, or EPUB Accessibility 1.1 — tested with actual assistive technology, not just an automated scan.
Remediation, not just a report
Most vendors hand over a list of failures. We fix them: semantic structure, keyboard navigation, focus states, contrast, labels and error messages.
Document and PDF accessibility
Tagged PDFs with correct reading order, alt text, table headers and language markers — including regional-language documents.
Accessible EPUB 3
Reading order, alt text, MathML, navigation and accessibility metadata, validated with EPUBCheck and Ace by DAISY.
Indian-language accessibility
Correct language tagging and screen-reader behaviour for Telugu, Hindi, Tamil and other scripts — routinely missed even in otherwise compliant sites.
A conformance report
A statement of what was tested, what conforms, and what remains — the document your reviewer, distributor or procurement officer actually asks for.
How we work
In this order, because each step depends on the one before it.
- Step 1
Scope what must conform
Which standard, which pages or titles, and who is going to check it. This decides the whole job.
- Step 2
Audit and prioritise
Automated testing plus manual screen-reader and keyboard passes, ranked by how much each failure actually blocks a user.
- Step 3
Remediate
We make the fixes in your codebase or files, and explain each one so your team stops reintroducing them.
- Step 4
Verify and document
Re-test, then issue the conformance report and a short guide for keeping it compliant.
Questions we get asked
- What is GIGW and does it apply to us?
- The Guidelines for Indian Government Websites set the standard for central and state government sites and apps, and reference WCAG conformance. If you are a department, PSU, university or a vendor building for one, your site will be assessed against it.
- Why are publishers suddenly asking about accessibility?
- Distributors and retailers selling into Europe now require accessibility conformance and metadata for digital publications, so it has become a condition of distribution rather than a nice-to-have. Back-list titles are where most publishers are exposed.
- Can you not just run an automated checker?
- Automated tools catch perhaps a third of real failures and miss the ones that matter most — reading order, meaningful alt text, keyboard traps, focus management. We run the tools and then test by hand with a screen reader.
- Do we have to rebuild the site?
- Rarely. Most failures are fixable in place: heading structure, labels, contrast, focus states and ARIA. We only recommend a rebuild when the markup is so tangled that fixing it costs more than replacing it.
Tell us what you need
A 20-minute call, then a written fixed-price scope. No obligation.