Compliance and Accessible Digital Services

Accessibility starts with the structure of the service.

Marchitects helps public institutions plan accessible communication and digital-service systems. We connect language, content structure, documentation, governance, and implementation requirements from the beginning.

01 Why accessibility is structural

Accessible services are planned, then built.

Title II of the Americans with Disabilities Act requires state and local government web content and documents to meet WCAG 2.1 Level AA. That includes the website, the forms, and every PDF published on a public page.

When accessibility is added at the end, each new document and page repeats the same defects. When it is part of the content structure, the staff workflow, and the vendor requirements, the service stays accessible as it grows.

Language, content structure, documentation, governance, and implementation requirements belong in the same plan.

02 What Marchitects evaluates

Work can include

  • Accessibility assessments
  • ADA and WCAG architecture
  • Content and document requirements
  • Governance frameworks
  • Remediation planning
  • Vendor and implementation requirements
  • Staff workflows
  • Quality assurance documentation
  • Public accountability records
03 ADA and WCAG architecture and remediation

From the page template to the document archive.

  • Page and template architectureHeadings, landmarks, navigation, forms, color contrast, and keyboard access defined at the template level so every new page inherits them.
  • Document and PDF requirementsTagging, reading order, alternative text, and table structure for agenda packets, planning documents, procurement bids, and public forms.
  • Remediation planningAn inventory of existing content, a priority order based on public use and exposure, and a sequence the institution can staff and fund.
04 Governance, documentation and accountability

Accessibility the institution can maintain and prove.

Governance frameworks

Roles, review points, and standards that decide who publishes what, and how it is checked before it goes live.

Staff workflows

Authoring and publishing steps that produce accessible content by default, with training materials staff can keep using.

Quality assurance documentation

Testing records that show which content was reviewed, against which criteria, and what was corrected.

Public accountability records

Accessibility statements, feedback channels, and a documented record of remediation progress.

05 Procurement and implementation

Requirements that carry into every contract.

Vendor and implementation requirements translate the accessibility plan into solicitation language, acceptance criteria, and delivery checkpoints, so each vendor builds to the same standard.

Procurement note

Public-sector compliance and procurement may be delivered through Marketing Automation Techs LLC when the solicitation requires that entity.

06 Institutional research

California public document audit.

Marchitects reviewed the public document archives of 50 California government entities, including agenda archives, planning departments, procurement pages, and public forms.

50California government entities reviewed
6,294Untagged PDF documents identified across public archives
27Entities rated high PDF exposure
8 of 11Active vendor contracts without PDF remediation in scope
07 Process

From assessment to commissioning.

01
Assess.

Inventory the digital service, its content, documents, and vendors, and measure it against WCAG 2.1 AA.

02
Architect.

Define the content structure, document requirements, governance, and remediation sequence.

03
Build.

Implement templates, remediation, staff workflows, and vendor requirements.

04
Commission.

Train staff, document quality assurance, and publish the public accountability record.

Compliance and Accessible Digital Services

Accessibility starts with the structure of the service.

Review the Digital-Service Structure