Accessibility · our opening argument
Accessibility is not a feature. It is the product.
Most government digital services fail basic accessibility testing. We engineer the opposite, from the first line of code. This page is the demonstration: open it with a screen reader, navigate it by keyboard, and audit it. We built it to be praised.
- WCAG 2.2 Level AA, AAA where practical
- Semantic HTML, landmarks, correct heading order
- Full keyboard operability, visible focus
- Every text pairing passes AA contrast
- Honors prefers-reduced-motion
A government service that excludes people is not finished
Public services are for everyone, including the roughly one in four adults living with a disability. When a benefits portal cannot be operated by a screen reader, or a permit form traps a keyboard user, the government has not simply shipped a flaw. It has denied access to a public right.
Accessibility is also the law. Section 508 of the Rehabilitation Act requires federal agencies to make electronic information accessible, and most state and local bodies are held to the same WCAG standard. We treat that obligation as the floor, not the goal.
Two terms you will see in every RFP
The federal requirement
A U.S. law requiring that electronic and information technology built, bought, or used by the federal government be accessible to people with disabilities. It points to WCAG for the technical detail.
The technical standard
The Web Content Accessibility Guidelines: a tiered set of testable success criteria (A, AA, AAA) maintained by the W3C. AA is the conformance level nearly every public body is measured against.
Perceivable
People can perceive the content, with captions, alt text, and sufficient contrast.
Operable
Everything works by keyboard, with enough time and no motion traps.
Understandable
Content reads plainly and forms explain errors clearly.
Robust
It works across browsers and assistive technology, today and tomorrow.
How we make a service conform
Whether we are building new or fixing what you have, the path is the same and it is documented at every step.
- 01
Audit
Automated scans plus manual testing with real assistive technology, against every AA criterion.
- 02
Findings & VPAT
A prioritized report and a Voluntary Product Accessibility Template documenting conformance.
- 03
Remediation
We fix the code, the content, and the patterns that caused the failures, not just the symptoms.
- 04
Verification
We re-test with users and assistive technology, then update the VPAT to reflect the result.
- 05
Monitoring
Accessibility regresses without attention. We set up checks so it stays conformant after launch.
A Voluntary Product Accessibility Template is the standard document procurement teams ask for. It states, criterion by criterion, how a product conforms to Section 508 and WCAG. We produce and maintain one for every engagement, and we will share a sample on request.
What ships in every Roebling Works build
- Semantic HTML with correct landmark regions
- Logical heading order, one h1 per page
- Full keyboard operability and a skip-to-content link
- Visible focus states on every interactive element
- Contrast verified against AA across the whole palette
- Meaningful alt text, ARIA only where genuinely needed
- Support for prefers-reduced-motion
- Labelled forms with clear errors and focus management
- A published accessibility statement and VPAT
Our accessibility statement
Roebling Works is committed to making this website usable by the widest possible audience, regardless of ability or technology. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across the whole site, and reach Level AAA where it is practical to do so.
Measures we take
- Semantic HTML with correct landmark regions and an unbroken heading order.
- A visible skip-to-content link and full keyboard operability with clear focus styles.
- Color contrast verified against AA for all text and user-interface components.
- Meaningful alternative text on images, with decorative images correctly hidden.
- Forms with associated labels, clear required-field indication, and announced errors.
- Respect for the prefers-reduced-motion setting on all animation.
Conformance and the VPAT
We assess this site against WCAG 2.2 Level AA using automated tooling and manual testing with assistive technology, including keyboard-only and screen-reader passes. A Voluntary Product Accessibility Template (VPAT) documenting conformance is available on request.
Feedback
If you encounter a barrier on this site, or need information in a different format, please contact us at [email protected]. We aim to respond within one business day and to resolve accessibility issues promptly.
Request an accessibility audit
We will tell you plainly where your service stands and what it takes to reach conformance.