About

Literaria was born in San Juan — at the collision of two regulatory frontiers.

Accessibility law moved from advisory to enforceable. Bilingual education moved from optional to mandated. Every institution we talk to is staring down both deadlines at once. We built the infrastructure they wish already existed.

Founder

Saudy Badillo, founder of Literaria.

Software entrepreneur. Accessibility specialist. Based in Puerto Rico. I've spent the last several years building production systems at the intersection of compliance, AI, and education — the work most people consider too messy to automate well.

I started Literaria after watching the same scene repeat across dozens of institutions: a content team racing toward an accessibility deadline, a separate team racing toward a bilingual-content deadline, a third team manually compiling audit evidence for a regulator. Three workflows. Three deadlines. Zero infrastructure designed to handle them as a single problem.

Literaria is that infrastructure. One pipeline turns source content into WCAG 2.1 AA conformant, PDF/UA-aligned, bilingual EN ↔ ES learning modules with audit evidence attached on the way out. Built on Perplexity Computer because the regulatory monitoring, the content transformation, and the orchestration are all multi-agent problems — and that's what Computer is for.

Where Literaria sits

Every tool in the accessibility stack operates on content that already exists. Literaria operates one step earlier.

One pipeline. Source content goes in. Compliant, bilingual, audit-ready learning material comes out. The rest of the stack does its job better when Literaria feeds it.

Scanners & auditors

axe, WAVE, Pope Tech, Siteimprove, Level Access.

They tell you what's broken. Literaria produces content that isn't.

Remediation tools

Anthology Ally, EquidoxAI, CommonLook.

They fix documents after the fact. Literaria generates them born compliant.

LMS platforms

Canvas, Blackboard, Moodle.

They deliver content. Literaria produces what they deliver.

Translation services

Google Translate, DeepL, human agencies.

They convert after the fact, one language at a time. Literaria thinks in EN and ES from the first prompt.

Regulatory thesis

Why now.

Three forcing functions are hitting institutions at once. Each one alone is manageable. Together, they break the manual workflows everyone is currently using.

F1

ADA Title II final rule

The federal deadline that finally has teeth.

State and local governments — including public colleges — must conform digital content to WCAG 2.1 AA by April 26, 2027 (entities serving ≥50k population) and April 26, 2028 (smaller entities and special districts), per the DOJ's April 2026 Interim Final Rule extending the original deadlines by one year. HHS Section 504's parallel May 2026 deadline was not extended. Manual remediation runs $50K-$300K per major program. The math doesn't work without infrastructure.

F2

Bilingual mandates in HSI states

Spanish parity is no longer optional in the markets that matter most.

Texas (HB 100), Florida (Hispanic Heritage rule), New Mexico, California, and the entire UPR system either mandate or strongly incentivize parallel English/Spanish delivery. Translation done after the fact breaks accessibility — alt text, heading order, language attributes all drift. Single-pipeline output is the only durable answer.

F3

Audit evidence is the real deliverable

Regulators don't ask if you're accessible. They ask for proof.

OCR, DOJ, and state auditors don't ask "is your content accessible?" — they ask "show me the evidence". axe-core scan logs. veraPDF reports. Remediation tickets. Last-modified dates per WCAG criterion. Literaria produces all of that automatically, on every module, every time.

Why Computer

A defensible moat is built on orchestration, not on a model.

Anyone can call an LLM. The defensible work is the orchestration: routing transformation jobs across five specialized workflows, working through a queue of pending tasks every hour, monitoring W3C/WAI/ADA.gov for regulatory drift, validating PDFs through veraPDF, and producing audit evidence that survives a regulator's review. Perplexity Computer is the substrate that makes all of that possible from one founder, one workspace, one tight 5-week sprint.

See it run

Want to talk?

We answer fast. Bilingually.

Pilot programs run 6-8 weeks. We work with one class, one course, one regulatory deadline at a time — and we ship.

Book a pilot demo