llms.txt
Compare with other sites' llms.txt files →# AccessLumens
> An automated accessibility checker that tests websites against WCAG 2.2 Level AA and PDF documents against both WCAG 2.2 and PDF/UA (ISO 14289) in the same tool. Most tools do one or the other: browser extensions and crawlers cover web pages, while PDF conformance checkers cover documents. AccessLumens covers both, and publishes its scoring model rather than treating it as a black box.
## What it does
- Website scanning: single page, full-site crawl, or a live user-journey walkthrough that exercises real interactions rather than a static page load.
- PDF document scanning: WCAG 2.2 plus PDF/UA-1 and PDF/UA-2 structural conformance, including the tag tree, document structure, and contrast sampled from the rendered page rather than inferred from the drawing model.
- Keyboard and experience analysis beyond the core rules engine: focus visibility, keyboard traps, and focus order.
- Scored, prioritised reports with element-level evidence and remediation guidance.
- PDF repair: rebuilds the tag tree, sets language and a title read from the document's first page (the file name is only a fallback), embeds fonts, fixes tab order, writes the character-to-Unicode map for fonts that declare a standard encoding, and recolours text that fails WCAG 1.4.3 contrast. Recolouring moves each failing colour only as far as it needs to pass, keeps its hue, leaves passing text alone, and is shown to the user before and after, rendered from their own pages, before they pay. The user can substitute their own colour for any of them, or undo the recolouring entirely and keep every other repair; the document is re-checked and re-scored either way. The recolouring is rejected if any pixel changes outside the text it targeted, and the repaired file is re-checked against the original before delivery and discarded if the text, forms or rendering changed, so a repair that made the document worse is never handed over.
- Picture descriptions in PDF repair: AI drafts a description for each picture, the user reads and edits them, and the approved ones are written into the document, which is then re-checked and re-scored. A picture the user marks as decoration is made an artifact and removed from the structure tree rather than given empty alternative text. This is the only feature that sends any part of a document to a third party, and it is opt-in. Alternative text in a PDF replaces the element it is written on and everything inside it, so where an auto-tagger has grouped a caption into a figure, the caption is moved out to sit beside it rather than being silenced by the description; where it cannot be separated, the picture is left undescribed and the reason is shown.
- Existing structure is kept: a document whose tag tree is already structurally sound is never re-tagged, whatever its score, and font embedding (which regenerates the file and drops tags) only runs when the structure is being rebuilt anyway.
- Before-and-after structure preview: before payment, the repaired pages are drawn with every tagged element (headings, paragraphs, figures, tables, lists, links, form fields) boxed and numbered in screen-reader reading order, beside the original, where untagged content is marked. It shows the reading order; it does not let the user rearrange it. Figures without a real description are flagged, and placeholder alternative text such as "image 1" or "description pending" is treated as missing rather than counted.
- Broken tables are reported, not rewritten: the tags are compared against what is drawn on the page, and tables whose structure does not match what a sighted reader sees are named by page. What a column means is a judgement about the author's content, and the tool says so rather than guessing.
- PDF/UA identifier: a repaired document is declared PDF/UA-1 in its XMP metadata only when the re-check finds it conforming in every other respect, and the result is validated again afterwards. A document that still fails anything is left undeclared, because the identifier is a claim of conformance.
- Regulatory context detection: infers the likely governing jurisdiction (ADA, Section 508, EAA, AODA, and others) from signals on the site itself.
## How it works
Page analysis runs axe-core, the open-source rules engine maintained by Deque, inside a real headless Chromium browser, extended with checks of our own. PDF analysis uses veraPDF for PDF/UA conformance plus our own WCAG-mapped checks. Automated testing can reliably evaluate only the machine-checkable portion of WCAG, so a report is a diagnostic and prioritisation tool, not a conformance certification.
## Key pages
- [Scanning methodology and scoring model](https://accesslumens.com/methodology): the full detection and scoring internals, including the SWBS scoring model, automated coverage limits, and known false-positive and false-negative cases. Written to be interrogated rather than trusted.
- [PDF accessibility checker](https://accesslumens.com/pdf-accessibility-checker): the PDF/UA and WCAG document-checking product.
- [Sample report](https://accesslumens.com/sample-report): a complete example report with no signup.
- [PDF repair](https://accesslumens.com/pdf-remediation): upload an inaccessible PDF and get a repaired one back, priced against a measured improvement.
- [Accessibility MCP server](https://accesslumens.com/accessibility-mcp-server): a free, local MCP server (npm @accesslumens/mcp) that lets AI coding agents such as Claude Code, Cursor and GitHub Copilot scan pages, including localhost, for WCAG 2.2 issues with the same scanner as the site, fix them and rescan. No account or API key; nothing is sent to AccessLumens.
- [PDF tools compared](https://accesslumens.com/pdf-remediation-tools-compared): Acrobat, CommonLook, axesPDF, Equidox and AccessLumens side by side, including where we are behind.
- [Pricing](https://accesslumens.com/pricing): scanning is free; reports are paid, first report free. Repairing a PDF is $5 per document, charged only for the documents whose re-check shows the score improved. Volume pricing from 6 documents.
- [FAQ](https://accesslumens.com/faq)
- [Accessibility disclaimer](https://accesslumens.com/accessibility-disclaimer): what an automated scan can and cannot establish.
- [AI disclosure](https://accesslumens.com/ai-disclosure): where AI is and is not used in producing a report.
- [Security](https://accesslumens.com/security)
- [WCAG criteria and accessibility rules](https://accesslumens.com/rules): all 86 WCAG 2.2 success criteria, each with our own measured failure rate where one exists, cut by industry, CMS vendor and e-commerce platform. States plainly that only 22 of the 86 produce any automated signal, so an automated pass rate is not conformance.
## Original research
Primary data we collected and published. Free to read, cite, and quote with attribution.
- [Research index](https://accesslumens.com/research): aggregate WCAG 2.2 statistics across industries, in the style of the WebAIM Million.
- [The State of US County PDF Accessibility 2026](https://accesslumens.com/research/state-of-us-county-pdf-accessibility-2026): PDF documents harvested from a random sample of US county portals, checked against PDF/UA and WCAG 2.2 ahead of ADA Title II making them regulated web content from 26 April 2027.
- [The State of US Healthcare Accessibility 2026](https://accesslumens.com/research/state-of-us-healthcare-accessibility-2026): US healthcare providers scanned against WCAG 2.2 ahead of the HHS Section 504 web deadline. Patient-portal vendor predicts keyboard failure independently of organisation size.
- [The State of SEBI-Regulated Financial Accessibility 2026](https://accesslumens.com/research/state-of-sebi-financial-accessibility-2026): Indian exchanges, brokers, AMCs, depositories, RTAs and KRAs scanned before SEBI's 31 July 2026 remediation deadline.
- [The State of EU E-Commerce Accessibility 2026](https://accesslumens.com/research/state-of-eu-ecommerce-accessibility-2026): Europe's largest online stores across 8 countries, one year after the European Accessibility Act took effect. Names individual retailers.
- [The State of US Local Government Accessibility 2026](https://accesslumens.com/research/state-of-us-local-government-accessibility-2026): US city government sites measured against the ADA Title II web deadline. A city's CMS vendor turned out to predict its accessibility risk.
- [The State of Shopify DTC Accessibility 2026](https://accesslumens.com/research/state-of-shopify-accessibility-2026): Leading Shopify DTC stores scanned against WCAG 2.2, including scripted keyboard testing.
## Guides
- [How to Remediate a PDF: The Obligation, the Workflow, and the Tools](https://accesslumens.com/blog/how-to-remediate-a-pdf): PDF remediation for an existing backlog: which laws put your documents in scope and by when, how to triage a document library, and what each remediation tool is actually for.
- [How to Make a PDF Accessible (WCAG 2.2 and PDF/UA)](https://accesslumens.com/blog/how-to-make-a-pdf-accessible): What makes a PDF unreadable to a screen reader, the fixes in the order documents actually fail, how PDF/UA-1 and PDF/UA-2 relate to WCAG 2.2, and why some checkers give a perfect score to a file they never read.
- [WCAG 2.2 Compliance Checklist (2026)](https://accesslumens.com/blog/wcag-2-2-checklist): A plain-English WCAG 2.2 Level AA checklist: all four principles, the nine criteria new in 2.2, and what you can automate vs. test by hand.
- [ADA Website Compliance: A Practical Guide for Businesses](https://accesslumens.com/blog/ada-website-compliance): What ADA website compliance means in practice, who's covered, why web-accessibility lawsuits keep rising, and a pragmatic path to lower your risk.
- [The European Accessibility Act: Who Must Comply and How](https://accesslumens.com/blog/european-accessibility-act): The EAA became enforceable on 28 June 2025 and reaches private companies selling into the EU. Who's covered, the microenterprise exemption, and a readiness checklist.
- [The Most Common Accessibility Issues (and How to Fix Them)](https://accesslumens.com/blog/common-accessibility-issues-and-fixes): The eight accessibility defects we see most often (low contrast, missing alt text, unlabeled forms, focus problems, reflow) and exactly how to fix each.
## Contact
- support@accesslumens.com
- [Contact page](https://accesslumens.com/contact)