Built to survive
the audit.

Section 508 and WCAG 2.1 AA from the first wireframe — delivered for the Air Force, DECA, and the Bush Library.

Read the column
headings.

Two lists, deliberately separate. We will not blur a standard we meet into an authorisation we hold.

Standards we build to

Delivered against on shipped public-sector programs. Ask and we will send the engagement record.

Section 50829 U.S.C. § 794d
Delivered on public-sector programs, audited before launch and again after every release.
WCAG 2.1 Level AASuccess criteria A + AA
Built in from the first wireframe, then verified by automated scan and manual passes.
USWDS alignmentU.S. Web Design System
Component patterns, typography, and colour tokens aligned to the federal design system.
Plain languagePlain Writing Act guidance
Written to the Act's reading-level and structure guidance, then tested with real users.

Environments we build toward

Subject to the agency's own authorisation. Tebeau Group holds no authorisation in this column.

FedRAMPCloud service authorisation
We build to FedRAMP-aligned controls inside a boundary your agency has already authorised.
FISMACategorisation and ATO
The categorisation and ATO belong to your system and your authorising official, not to us.
Security clearanceFacility and personnel
Tebeau Group holds none. Cleared work runs through a prime that holds what the work requires.
Contract vehiclePath to award
No GSA schedule. We come in as a technology subcontractor to a prime contract holder.

Nothing in the right column is a certification claim, and we would rather lose the bid than imply it is.

How the audit
actually runs.

Six passes, every release. Automated tooling finds a fraction of it; the rest needs hands and ears.

01

Automated baseline in CI

axe-core and Lighthouse run on every route, so a regression fails the build, not the audit.

02

Keyboard-only traversal

Every control reached, operated, and escaped without a mouse. Focus order and visible focus.

03

Screen-reader passes

NVDA and JAWS on Windows, VoiceOver on macOS and iOS. Names, roles, states, live regions.

04

Contrast, zoom, reflow

4.5:1 text and 3:1 UI contrast, 200% text zoom, 400% reflow with no loss of content.

05

Remediation and re-test

Each finding carries a WCAG success criterion, an owner, a fix, and a documented re-test.

06

Written conformance report

A VPAT 2.5 / ACR for your accessibility office, with known exceptions listed, not buried.

The pipeline behind
the paperwork.

Unstructured forms in, system-ready records out, with low-confidence extractions routed to a person.

Reference architecture for the document processing pipeline: ingestion, classification, extraction and routing, with low-confidence extractions diverted to human review
Representative architecture, not a delivered artifact — the operational interfaces are not ours to publish.

99.999%

Classification accuracy on the document types the engine was trained to handle.

78%

Reduction in manual processing time across the logistics workflow it was applied to.

Human in the loop

Low-confidence extractions divert to review instead of writing a wrong value.

Visual treatment for the U.S. Air Force intelligent document processing engagement

Same engine, citizen side.

Intake, eligibility, and status lookup are the same problem: unstructured input, auditable output.

Read the Air Force case record

The four
hard questions.

Do you deliver Section 508 conformant websites?

Yes. Section 508 and WCAG 2.1 Level AA are the standards we build to on every public-sector program.

We have delivered against them for the Defense Commissary Agency and a 45-location veterans network.

Conformance is verified before launch by automated scan plus manual keyboard and screen-reader passes.

You get a VPAT 2.5 / ACR that lists known exceptions rather than omitting them.

How do you audit accessibility, specifically?

Six passes, run on every release, not once at the end of the project.

An axe-core and Lighthouse baseline runs in CI, so a regression fails the build instead of the audit.

Then keyboard-only traversal, and screen-reader passes on NVDA, JAWS, and VoiceOver.

Contrast at 4.5:1, 200% text zoom, and 400% reflow with no loss of content or function.

Every finding carries a WCAG success criterion, an owner, a fix, and a documented re-test.

Does Tebeau Group hold FedRAMP or FISMA authorisation?

No, and we will not imply otherwise anywhere on this site.

FedRAMP authorisation attaches to a cloud service offering, not to a development vendor.

FISMA categorisation and the ATO belong to the agency's system and its authorising official.

We build to FedRAMP-aligned controls inside the boundary your agency has already authorised.

We also hold no facility or personnel security clearance; cleared work runs through a prime.

Can you work as a subcontractor to our prime?

Yes. That is how our federal work has been structured to date.

On the Air Force IDP program we were the technology subcontractor to the federal-contract holder.

That partner was the prime of record and the party responsible for delivery to the Air Force.

We hold no GSA schedule, so we come in through your prime or a partner contract holder.

Call.
Don't book.

You are screening for a reason to disqualify us. Ask it out loud and get a straight answer.

Johnathan M. Tebeau

Founder & CEO, Tebeau Group, LLC — Dallas, Texas. Every engagement starts with him.

(469) 564-0663
hello@tebeau.group