Thesis diagnostics online
Purdue · 2026 rule set · community built
Will your thesis
pass review?
Run your Word file through the formatting and accessibility checks that Word misses. Every finding comes with a location, a rule ID, and what to fix.
- 89deterministic checks
- AAWCAG 2.1 findings
- 0files stored
Check my thesis
EngineDeterministicNo AI decisions
StorageNoneDeleted after analysis
ScopePurdue2026 guidelines
Nothing is stored. Ever. Your file is analyzed and deleted the second the report is done — no database, no accounts, no tracking. Working under embargo? Skip the upload and run it on your own machine instead.
Drag your .docx here, or
Word files only (.docx) · max 50 MB · no database, no storage, no tracking — your file is analyzed and deleted the second the report is done, because there is nowhere here it could be kept. Thesis under confidentiality or embargo? Skip the upload: download the checker and run it on your own machine instead — fully offline, same 89 checks.
Something in this report look wrong? Tell me — it helps the next student.
Accessibility ADA / WCAG 2.1 AA
Alt text, chart contrast, heading structure, table accessibility, reading order. An empty section means no accessibility issues were found.
Formatting
Current rules — Purdue University, as per 2026 guidelines
Everything below is enforced by the checker, one finding per rule, each with what the handbook wants instead. This list is generated from the checker's source code, so it can never go stale — the readable version lives in RULES.md.
How it works
- Upload. Your
.docxis read directly — styles, numbering, images, tracked changes. - 89 checks run. Handbook rules, template rules, accessibility rules, submission hygiene. No AI guessing.
- You get locations + fixes. Every finding carries a stable rule ID and says what the handbook wants instead.
Want the auto-fixer too, or to run offline? The command-line tools are in the repo.
Not at Purdue?
Purdue is the only school supported today — every other university's rules are still waiting for someone who knows them (maybe you?). School requirements live in config files, not in code: adding yours means copying one JSON file and filling in your handbook's numbers.
Request your school — attach your graduate school's handbook (or its key numbers: page size, margins, font, spacing, heading styles) and the maintainer will help turn it into a config. Developers: the universities guide and the contribution guide walk you through it.
Who built this?
Amogh Arya Munipalle — written while formatting a Purdue thesis, when the choice was "check 89 rules by hand, again" or "teach a script to do it." The script won, and now it's yours.
See the rest of the work at the portfolio, or follow along on GitHub.