1
Intake and validation
Source is validated, page count is detected, and a request is created.
Compliance Lead focus: Confirm policy class and impact tier so SLA urgency is set correctly.
Operational lifecycle
How the document workflow runs
From source intake to delivered HTML and ongoing support. Every request follows an explicit lifecycle with ownership visibility at each stage.
The process
How it works in 4 steps
From upload to ongoing maintenance. A clear path to accessible documents.
Step 1
Submit
Upload your PDF, DOCX, or PPTX. We validate format, detect page count, and create your request.
Step 2
Convert
Our team converts your document to semantic, accessible HTML with human QA at every stage.
Step 3
Review
You receive the converted HTML in your workspace. Edit text, check accessibility scores, save versions.
Step 4
Maintain
Ongoing workspace keeps your documents editable, validated, and exportable. Full offboarding support included.
Why this works
What makes this different
Three deliberate choices that set this workflow apart from typical document remediation services.
Human-led, not automated
Every document is converted by a human specialist, not an automated tool. This means better semantic structure and fewer accessibility regressions.
HTML, not PDF
We deliver semantic HTML, not remediated PDFs. HTML is natively accessible, responsive, and maintainable.
Learn why we chose HTMLWorkspace, not one-off
After delivery, you get an ongoing workspace to edit, validate, and version your documents. Not just a static file.
Role-based view
Workflow journey by role
Each role sees the same pipeline through a different lens. Select a role to see phase-specific notes.
Workflow Journey by Role
Viewing role notes for: Compliance Lead
2
Billing and queue transition
Manual invoice state is updated and request enters production queue.
Compliance Lead focus: Track turnaround commitments and document exceptions.
3
Conversion and QA
Human-led conversion produces accessible HTML and validates quality before handoff.
Compliance Lead focus: Capture review evidence for audit or governance reporting.
4
Post-handoff support
Workspace subscription activates after first handoff; user edits in-platform with issue tracking and escalation linked to the document.
Compliance Lead focus: Ensure unresolved barriers are triaged and closed with traceable outcomes.
Transparency
Request status model
Status transitions are explicit so users, admins, and support teams share one source of truth. Every request moves through these states.
submitted
Request accepted and validated against format policy
payment_pending
Awaiting billing progression and confirmation
queued
Ready for production scheduling
in_progress
Conversion workflow currently active
qa_review
Accessibility quality checks in progress
delivered
Handoff linked to editable workspace document
rejected
Rejected with explicit reason and deterministic code
cancelled
Closed without handoff delivery
Guarantees
Operating principles
Four commitments that shape how every request is handled, from first upload to offboarding.
Deterministic intake
Every request follows explicit validation rules. Rejections include reason codes and remediation guidance so resubmission is fast and predictable.
Human-led conversion
Human specialists handle conversion and QA. This reduces semantic accessibility regressions that automated tools commonly introduce.
Workspace activation
Your workspace subscription activates after first handoff. Edit text, save versions, and run accessibility checks, all within the platform.
Offboarding guarantees
Free ZIP export of all documents plus a 60-day hosted mirror. Your content is never locked in.
Start with one document
Ready to run this workflow on a live document?
Start with one conversion request, validate handoff quality, and then scale the same lifecycle across recurring document programs.