Skip to main content
Illustrative Example

Illustrative scenario: This institution, its quotes, timeline, costs, and outcomes are fictional planning assumptions, not customer evidence. Automated scores do not establish WCAG conformance; every file requires appropriate human review.

How a Large University Could Achieve STEM Compliance Efficiently

A 25,000-student scenario: How bulk processing and LaTeX support could make STEM accessibility achievable.

25,000

Students

200

STEM courses

4 months

Illustrative planning window

The Challenge: A Large STEM Inventory

In this hypothetical exercise, a university inventories course materials and chooses a four-month evaluation window. These quantities are assumed for planning:

Content Inventory

  • 2,500 PDF lecture notes (mostly scanned)
  • 3,200 PowerPoint presentations
  • 10,000+ LaTeX equations (math, physics, engineering)
  • 800 video lectures (auto-captions only)
  • 1,500 homework assignments

Manual Estimate

  • 12,000+ hours of work
  • $1.26M cost (at $75/hr)
  • 18 months with 3 FTE staff
  • Misses deadline by 14 months

"We were told the deadline was 'non-negotiable.' Manual remediation would take until mid-2027. We needed automation."

Director of Accessibility Services

Why They Chose Aelira

  • Native LaTeX/MathML source remediation - YuJa and Ally don't remediate native LaTeX source
  • CLI bulk processing - IT could script entire workflows
  • AI-assisted fixes - supported partial changes requiring human review
  • Transparent pricing - $2,249/mo managed department starting price
  • Local deployment option - Confirm configured providers, fallback behavior, and data handling
  • Terminal-native - Integrates with existing IT workflows

Implementation: 4-Month Sprint

1

Month 1: Setup + Pilot

November 2025

Week 1-2: Infrastructure

  • Installed Aelira CLI on IT department servers
  • Created bash scripts for bulk processing workflows
  • Set up automated directory scanning (cron jobs)
  • Trained 3 IT staff on CLI commands

Week 3-4: Pilot (5 courses)

  • Processed 250 files (PDFs, PPT, LaTeX)
  • Automated findings reviewed on every sampled file; unresolved issues recorded
  • Faculty feedback: "Didn't notice any changes to workflow"
  • Go-ahead for full rollout
2

Month 2: Bulk Processing

December 2025

# Illustrative scan commands; confirm your installed release
$ aelira scan pdf /courses/stem/pdfs --format json --output pdf-findings.json
$ aelira scan ppt /courses/stem/slides --format json --output slide-findings.json
$ aelira scan latex /courses/stem/math --format json --output math-findings.json
# Review generated output and unresolved issues before publication

Processed

  • 1,200 PDFs (OCR + structure)
  • 1,500 PowerPoints (contrast + alt text)
  • 4,500 LaTeX equations MathML
  • 50 courses (25% of total)

Time Savings

  • Automated: 120 hours
  • Manual review: 300 hours
  • Total: 420 hours (vs 6,000 manual)
  • Illustrative labor estimate only; verify with a measured pilot
3

Month 3: Scaling Up

January 2026

Parallel Processing (5 IT staff)

  • Each staff member processed 20 courses/week
  • Total: 100 courses (50% of remaining workload)
  • Automated: 250 hours, Manual review: 600 hours

Edge Cases Handled

  • Complex LaTeX packages (ChemFig, TikZ) require manual testing
  • Scanned PDFs with poor quality - 85% success (manual fallback)
  • Multi-language content requires language-specific manual review
4

Month 4: Final Push + QA

February 2026

Remaining Courses

  • Processed final 50 courses
  • Priority: High-enrollment courses first
  • Automated: 100 hours, Review: 200 hours

Quality Assurance

  • Spot-checked 10% of files (random sample)
  • Scan findings are review prompts, not compliance scores
  • 3% edge cases fixed manually

Illustrative planning outputs (not results)

Review

All sampled outputs

No conformance outcome is assumed

Pilot

Measure time required

The scenario's hour estimates are assumptions, not measured savings

Compare

Real quotes and staff time

The original scenario totals are not product outcomes

Cost Model to Validate in a Pilot

Manual Remediation (Projected)

  • Labor (3 FTE × 18 months): $1.26M
  • Tooling & licenses: $84K
  • Training: $28K
  • Total: $1.37M
  • Timeline: Set from applicable obligations and available staff

Aelira (Projected/Illustrative)

  • Aelira (4 months): $5,596
  • Labor (3 IT staff part-time): $157K
  • Server costs: $3K
  • Total: $165K
  • Timeline: Measure supported processing and review work

These totals are illustrative assumptions, not a savings forecast or conformance result.

LaTeX support and CLI-based workflows can significantly reduce the time required for STEM accessibility compliance.

Hypothetical scenario showing potential time savings for large STEM departments.

Explore STEM Accessibility Solutions

Learn how LaTeX support + CLI bulk processing + AI fixes could help your university meet compliance requirements.