Why I built AccessRecord
A short letter from Nabin Karna, the founder.
Hello, I’m Nabin Karna. I built AccessRecord, and I still run it myself, from Nepal.
If you sell software to schools, colleges or governments, sooner or later someone asks for your VPAT, or ACR: the report that says how accessible your product is. Two things about that report kept bothering me.
First, getting one written by an agency is slow and costly. Second, once it is written, it usually ends up as a PDF that nobody touches again, while the product keeps changing every month. Bit by bit the report stops being true, and the person reading it has no way to tell.
I wanted something simpler: one honest page for each report, tied to the product version it describes, that says plainly when it has fallen behind.
I also wanted to know how common the problem really is. So in October 2026 I went through all 471 tools in the public Edu App Center catalog. Only 41 of them led to an accessibility report a buyer could actually open. Of the 69 listings that pointed to a report, 12 led to a broken link. And of the 33 reports that carried a date, 8 were more than two years old. I published the whole study, with the method and the data, so you can check my work: The State of Edtech VPATs 2026.
AccessRecord has to meet its own standard, so it publishes its own record against WCAG 2.2 Level AA, on the same kind of page your buyers would see.
To be clear about what it is: AccessRecord won’t make your product accessible, and it doesn’t test it for you. It helps you keep an honest, current record of the work you have done, at one link you can give to any buyer.
I’m a small, independent founder. There’s no sales team and no ticket queue. When you write to support@accessrecord.app, I read it and I reply myself.
If this sounds useful, there are three easy ways to start. Download the free VPAT template. Try AccessRecord free for 14 days. Or just email me and tell me what you’re stuck on. I’d be glad to hear from you.
Nabin Karna
Founder, AccessRecord