Accessibility-native learning content infrastructure
Source documents go in. Structured, WCAG 2.2 AA conformant learning modules come out — in English and Spanish, with the compliance documentation to prove it.
Bring one document. Get the module back.
First module in 14 days · No procurement contract · No onboarding
Soy Saudy Badillo.
Literaria es mi proyecto. Es una aplicación que toma un documento —un PDF, un manual, un currículo, una política— y lo convierte en un sistema educativo completo.
No es un PDF más bonito. Es un módulo de verdad: el documento fiel, y sobre él las unidades de enseñanza, los términos clave, las tarjetas de práctica, el Simulador y una tutora anclada al contenido. En inglés y en español, generados a la par.
Cada módulo se construye conforme a los estándares de accesibilidad que exige la ley ADA —WCAG 2.2 AA— y se valida antes de publicarse. Cumple desde que se genera; no hay que remediarlo después.
Todo lo que ves en esta página es la plataforma corriendo hoy. No hay maquetas. El site completo llega con el lanzamiento; esto es el adelanto.
Escríbeme. Contesto yo.
Saudy Badillo, fundadora de Literaria
saudy@literaria.ai
I'm Saudy Badillo.
Literaria is my project. It takes a document — a PDF, a manual, a curriculum, a policy — and turns it into a complete learning system.
Not a prettier PDF. A real module: the faithful document, and on top of it the teaching units, the key terms, the practice cards, the Simulator, and a tutor grounded in the content. English and Spanish, generated side by side.
Every module is built to the accessibility standards the ADA requires — WCAG 2.2 AA — and validated before it publishes. It conforms from the moment it is generated. There is nothing to remediate afterward.
Everything on this page is the platform running today. There are no mockups. The full site arrives with the launch; this is the preview.
Write to me. I answer personally.
Saudy Badillo, founder of Literaria
saudy@literaria.ai
The shift
Existing tools attack accessibility at the document layer — fix this PDF — or at the site layer — scan this domain. Both start after the content already exists, which is why they never finish. The source keeps changing, and the fixing starts over.
Literaria operates upstream. The question stops being how do we make our existing content compliant and becomes how do we produce content that is compliant the moment it exists.
Why now
In April 2026 — days before it was due to take effect — the Department of Justice pushed the ADA Title II web accessibility deadline back by a year.
April 26, 2027
State and local governments and public institutions serving 50,000 or more. Because population is counted at the state level, that is effectively every public university.
April 26, 2028
Smaller public entities and special district governments.
The scope did not change. The standard did not change. The Department has said plainly that it expects to enforce the rule when the new date arrives. The clock was reset, not stopped — and it was reset in part because retrofit remediation cannot keep up with the volume. That is not a reprieve. It is an admission that the fixing model does not scale.
What does not wait:
Content that is born accessible does not need the extra year.
The rule sets WCAG 2.1 Level AA as the floor. Literaria builds every module to 2.2 AA.
01 — Transformation
Drop in a policy manual, a training procedure, a course syllabus, a certification curriculum. Literaria extracts the structure, identifies the learning objectives, and builds the sections, the key terms, and the knowledge checks.
Every module is validated before it publishes. If it does not meet WCAG 2.2 AA, it does not ship — the gate blocks it. The score is not a report you run afterward. It is a condition of the module existing.
02 — Bilingual
Both versions are generated at the same time, from the same source. The Spanish reads as though it were written in Spanish, because it was: Literaria adapts regional vocabulary, examples, and context rather than translating after the fact.
This matters structurally, not cosmetically. Translation done as a post-process breaks accessibility — alt text drifts, heading order shifts, language attributes fall out of sync. Parallel authorship is the only version of bilingual content that survives an audit.
The module
This is the part most platforms skip. Converting a document into accessible HTML gives you an accessible document. It does not give you a course.
A Literaria module has two layers that coexist. Layer one is the faithful source document, readable exactly as it was published — nothing paraphrased, nothing dropped. Layer two is a real learning module built on top of it: teaching units in the order they pay off, key terms with their bilingual glosses, the traps the assessment is built to catch, practice cards, and a check at the end of each unit.
Every unit stays anchored to the document sections it came from. A learner who wants the source is one link from the exact section, as published.
Practice
Reading is not learning, and an institution that has to demonstrate outcomes knows the difference. Each module ships with a Simulator drawn from its own content: questions, rationale-backed feedback, and practice cards for the terms that carry the weight.
None of it comes from a question bank. It comes from the institution's own document.
The tutor
ARIA Academic Reasoning & Inquiry Assistant
The name is deliberate. In accessibility, ARIA is the standard that makes an interface reachable by everyone. This ARIA does the same for the content inside it.
ARIA answers from the active module and nothing else. It works in the learner's language, it guides toward the answer instead of handing it over, and it names the section it drew from.
The constraint is the feature. A tutor grounded in the institution's own material cannot wander into content the institution never approved.
Who installs this
Different regulators, different deadlines, the same exposure — and the same answer: content built right the first time, in both languages, with the documentation attached.
Community colleges, certificate programs, vocational schools, regional universities. Digital course material has to be accessible, structured, and ready for the next academic year — and federal funding eligibility is tied to the documentation.
Employers large enough that "we didn't know" is not a defense. Training content that is outdated, English-only, and inaccessible creates employment-based legal claims — and the exposure compounds across every document the company owns.
Public-facing content and internal training carry an obligation that does not wait for a budget cycle. The exposure is public, the audit is scheduled, and the remediation contract never finishes.
Workforce development providers, grant-funded programs, and institutions running Workforce Pell Grant programs. Compliance is tied directly to the funding, every renewal cycle turns into a documentation crisis, and bilingual delivery is not a preference — it is an operating requirement.
What ships next
Not a mockup, not a slide. The rest of the platform is in active build, and rather than show you a rendering of it, here is the honest list.
A delivery calendar that ships sessions on cadence and replans when learners fall behind.
An on-demand bilingual conformance report for any cohort — the document a compliance officer hands the auditor.
A daily monitor of federal accessibility standards that flags which published modules a change in interpretation affects.
Portfolio-level compliance status, module coverage, and learner progress in a single view.
The pilot
Bring one document — a policy manual, a training procedure, a course syllabus, a certification curriculum. You get back a complete bilingual module, built to WCAG 2.2 AA, with the compliance documentation attached.
Show it to your compliance officer. Show it to your auditor. Show it to your CFO. If it does not stand up to all three, we have not done the job.
First module in 14 days · No procurement contract · No onboarding