Skip to main content

Test your site the way a screen reader reads it.

Paste a URL. You get back the element, the rule it breaks and the change to make. The first scan needs no account.

Course documents are a different job, and they have their own home.

Go to documents

What we can back up

  • Gamyata's engine powers SugamyaWeb, India's national accessibility platform: 1,500+ government websites, 250+ departments, 350,000+ issues resolved, 99.99% uptime (platform statistics as published by SugamyaWeb).

  • DOJ's Title II web rule requires WCAG 2.1 AA by April 26, 2027 for public entities with populations of 50,000 or more, and April 26, 2028 for smaller entities and special districts. It covers web content, mobile apps and documents, and it has a defined exception structure, so not every file you find is in scope.

  • The rule itself says: "Advanced technology, such as generative AI, does not yet reliably automate the remediation of inaccessible content at scale." (DOJ Title II interim final rule, April 2026, page 20907.) That is why a person reviews everything we attest.

  • Winner

    Government Innovation Challenge

  • 250+

    Government Departments Served

  • 1,500+

    Websites Tested

  • 350,000+

    Issues Resolved

Source: SugamyaWeb, Government of India

How it works

  1. Step 1

    You point us at something

    A page, a site or a document. Testing runs in layers: the code, the keyboard, what an assistive technology is actually told, and a review pass for the judgement calls.

  2. Step 2

    You get findings you can act on

    Each finding names the element, the criterion it breaks and the change to make. No score without the detail underneath it.

  3. Step 3

    A person signs what you hand over

    When a deliverable has to stand up to procurement or an audit, an expert reviews it before it leaves us, and we write down what we could not evidence yet.