Skip to main content
TimeTrax

TimeTrax demonstration — not an official government website.

Public implementation sample

Government CMS Accessibility Lab

A working demonstration of how TimeTrax approaches accessible public information, online forms, meeting records, and content governance.

Explore the use cases Review the test method

What this sample proves—and what it does not

This lab targets WCAG 2.2 Level AA and demonstrates TimeTrax’s accessibility engineering and content-governance approach. USWDS components provide a tested foundation, but they do not by themselves guarantee that an implementation or service conforms to WCAG. Results apply only to the identified build, pages, user flows, browsers, and assistive technologies tested.

Accessibility is a delivery practice

Built into design, code, content, and maintenance

TimeTrax combines semantic HTML and USWDS patterns with manual keyboard, screen-reader, zoom, reflow, and document testing. Automated scans help find defects; human review determines whether people can complete the task.

Understandable by default

Plain labels, predictable navigation, meaningful headings, readable instructions, and errors that explain how to recover.

Operable without a mouse

Visible focus, logical tab order, keyboard-operable controls, modal focus containment, and no keyboard traps.

Sustainable after launch

Author guidance, constrained CMS fields, accessible document workflows, regression checks, and clear ownership.

Working use cases

Try the interactions

These examples use real controls and accessibility behavior—not screenshots. Navigate them with a keyboard, zoom the page, or use your preferred assistive technology.

Use case 1

Public comment form

Every field has a programmatic label. Instructions are connected to controls, required status is expressed in text, and validation moves focus to a linked error summary.

  • Keyboard and screen-reader friendly
  • Specific inline error messages
  • Polite status announcement on success
  • Character limit announced without color alone
For example, pedestrian safety plan
We use this only to send a confirmation.
Preferred confirmation format Select one
You can enter up to 500 characters

Demonstration only: nothing is submitted or retained.

Use case 2

Urgent public notice

A USWDS modal keeps keyboard focus within the dialog while it is open, supports Escape, exposes its title and description, and returns focus to the trigger when closed.

Visible content equivalent

September meeting moved to Council Chamber B

The accessible notice is available in the page flow as well as the modal. Critical information is not hidden behind an interaction.

Updated: September 12, 2026, 3:15 p.m. Pacific

Use case 3

Meeting records and documents

A structured archive makes dates, meeting types, document purpose, language, and accessibility status understandable before a file is opened.

On narrow screens, the table remains scrollable and its region can receive keyboard focus.

Example 2026 meeting records
Meeting date Record Format Accessibility status
Board agenda Accessible HTML Ready
Full meeting packet Tagged PDF, 2.4 MB Checked
Approved minutes Accessible HTML and PDF Ready

The status label includes text, so its meaning does not depend on color.

Use case 4

Expandable service information

USWDS accordions expose expanded and collapsed state to assistive technology. Each trigger is a native button and the content remains available without pointer gestures.

Filter by meeting date, committee, or record type. Search results should announce their count and keep the query visible.

Use case 5

Status messages

Background actions need a text update that screen readers can hear without forcing focus away from the current task.

CMS preview status

No update is running.

The live region announces the change. Focus stays on the button.

Accessible publishing at scale

CMS guardrails for content authors

A component library cannot protect a site if the publishing workflow permits missing headings, vague link text, uncaptioned media, or unreviewed documents. TimeTrax configures the CMS and editorial process together.

Accessible agenda and board-packet workflow

  1. Start with structure Use a controlled title, meeting date, committee, language, and document type.
  2. Author accessibly Require heading order, table headers, meaningful links, alt text decisions, and captions.
  3. Check the source Run the authoring-tool checker and correct reading order before export.
  4. Verify the output Test tags, language, document title, keyboard reading order, contrast, and searchable text.
  5. Publish with context Show file type, size, language, and verification status next to the link.

WordPress or a custom CMS

For WordPress delivery, TimeTrax can use WordPress core blocks with the accessibility-ready Twenty Twenty-Five theme as a controlled base, avoiding a proprietary page builder. For a custom CMS, the same rules become reusable Spring Boot templates, validated fields, role-based workflows, and publishing checks. In either path, “accessibility-ready” components still require implementation and content testing.

Evidence over assumptions

Verification method

We define the pages and user flows in scope, record the environment, test against success criteria, correct defects, and retain the results for regression testing.

Current build check

Seven tested states, zero automated violations

Checked September 12, 2026 with axe-core 4.13.0 in Chrome 153. Scripted checks covered the initial page, invalid and successful form states, open modal, expanded accordion, published status message, and a 320 CSS-pixel viewport.

  • 0axe violations
  • 11/11interaction checks passed
  • 0runtime errors
Demonstration verification matrix
Area Representative criteria Method Evidence retained
Structure and names 1.3.1, 2.4.6, 4.1.2 DOM and screen-reader review Page checklist and findings
Keyboard and focus 2.1.1, 2.1.2, 2.4.3, 2.4.7, 2.4.11 Manual keyboard path Flow, browser, date, and result
Zoom and reflow 1.4.4, 1.4.10, 1.4.12 200% zoom and 320 CSS-pixel viewport Exceptions and screenshots when useful
Forms and status 3.3.1–3.3.3, 4.1.3 Invalid and successful submission paths Focus destination and announcement
Automated checks Machine-testable A and AA rules axe-core plus HTML and code review Tool version, URL, date, and findings
Documents Applicable WCAG and PDF/UA techniques Source, tag tree, reading order, and assistive-tech review Per-document remediation log

Current limitation: This page is a focused implementation sample, not a third-party certification, VPAT, or Accessibility Conformance Report. The recorded check is not a substitute for manual screen-reader evaluation. Procurement-specific acceptance criteria and assistive-technology coverage are agreed for each engagement.

Standards and source material

Built on public, reviewable guidance

The implementation uses a locally hosted release of USWDS and references primary accessibility guidance. TimeTrax is not affiliated with or endorsed by the U.S. government or UCLA.

Plan an accessible public website

Need this approach applied to your content and services?

TimeTrax provides accessible website redesign, CMS implementation, document workflows, hosting, and ongoing support.

Contact TimeTrax

Meeting location changed

The September 17, 2026 public meeting will begin at 6 p.m. in Council Chamber B. The livestream address and telephone participation options have not changed.

For an accommodation or language assistance, contact the clerk at least two business days before the meeting.