# Accessibility Statement | USLege

> USLege's commitment to digital accessibility: our WCAG 2.2 AA conformance status, measures we take, known limitations, and how to report a barrier.

Canonical: https://www.uslege.ai/accessibility

---

Legal

# Accessibility Statement

Last updated August 3, 2026

On this page

1.  [Our Commitment](#our-commitment)
2.  [Standards We Follow](#standards)
3.  [Conformance Status](#conformance-status)
4.  [Measures We Take](#measures-we-take)
5.  [Compatibility](#compatibility)
6.  [Technical Specifications](#technical-specifications)
7.  [Known Limitations](#known-limitations)
8.  [How We Assess This Site](#assessment)
9.  [Public-Sector Customers](#public-sector)
10.  [Feedback & Contact](#feedback)

USLege, Inc. ("USLege," "we," "us") wants everyone who visits our website or uses the USLege application to have a full and equal experience — including people who use screen readers, keyboard-only navigation, voice control, screen magnification, or other assistive technology.

## Our Commitment

Legislative information is public information, and the tools people use to follow it should be usable by everyone. We treat accessibility as an ongoing part of how we design and build — not a one-time checklist. Accessibility is considered when we add new pages and features, and we fix barriers we find or that are reported to us.

## Standards We Follow

We use the [Web Content Accessibility Guidelines (WCAG) 2.2, Level AA](https://www.w3.org/WAI/standards-guidelines/wcag/) as our standard. WCAG is published by the World Wide Web Consortium (W3C) and is the most widely adopted benchmark for digital accessibility, including under the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act.

## Conformance Status

This website is **partially conformant** with WCAG 2.2 Level AA. "Partially conformant" means that some parts of the content do not yet fully conform to the standard. We use this term deliberately: we have not yet completed a full third-party conformance audit, and we would rather describe our status honestly than overstate it. We address known issues as we find them and welcome reports of anything we've missed.

## Measures We Take

### In how the site is built

-   Semantic HTML structure with landmark regions and a logical heading hierarchy
-   Visible keyboard focus states on links, buttons, menus, and form controls
-   Full keyboard operability — no functionality that requires a mouse
-   Alternative text on informational images; decorative images hidden from assistive technology
-   Sufficient color contrast for text against its background, and no information conveyed by color alone
-   Support for the `prefers-reduced-motion` setting — animations are reduced or removed for people who ask their device to limit motion
-   A skip-to-content link on long-form pages
-   Pages that remain usable when zoomed to 200% or viewed on small screens
-   Descriptive page titles and link text

### In how we work

-   Accessibility is part of our review checklist for new pages and features
-   Reported barriers are triaged like functional bugs, not deferred as enhancements
-   This statement is reviewed and updated as the site changes

## Compatibility

This website is designed to work with current versions of major browsers (Chrome, Firefox, Safari, and Edge) on desktop and mobile, and with common assistive technologies, including screen readers such as VoiceOver, NVDA, and JAWS. The site is built with standard, progressively enhanced HTML, so core content remains available even in older browsers or with JavaScript disabled.

## Technical Specifications

Accessibility of this website relies on the following technologies working with your browser and any assistive technologies or plugins installed on your computer: HTML, CSS, and JavaScript. No client-side frameworks or heavy interactive libraries are used, which keeps pages fast and predictable for assistive technology.

## Known Limitations

Despite our efforts, some parts of the site may not yet be fully accessible. Known areas include:

-   **Third-party embeds.** Some pages include embedded content we don't fully control, such as scheduling widgets and video players. Where an embed presents a barrier, contact us and we will help you complete the same task another way (for example, booking a demo by email).
-   **Video content.** Some older marketing videos may lack captions or audio descriptions. We are working through these; if you need the content of a specific video, ask us and we will provide it in an accessible format.
-   **Older content pages.** Some long-standing pages predate our current standards and have not yet been re-reviewed.

If you run into a barrier not listed here, please tell us — see [Feedback & Contact](#feedback) below.

## How We Assess This Site

We assess accessibility through internal self-evaluation, using a combination of automated testing tools and manual checks — including keyboard-only navigation and screen reader spot-checks on key pages and user flows. This statement will be updated if we complete a formal external audit.

## Public-Sector Customers

Many of our customers are government agencies and public institutions with their own accessibility obligations, including Section 508. If your organization needs accessibility documentation for procurement or compliance review, contact us at [support@uslege.ai](mailto:support@uslege.ai) and we will work with you.

## Feedback & Contact

Found a barrier? Email [**support@uslege.ai**](mailto:support@uslege.ai) with the page address and a short description of the problem. **We aim to respond within 2 business days.**

When you write to us, it helps to include the URL of the page, what you were trying to do, and the browser and assistive technology you were using — but none of that is required. Customers can also reach us through **Help & Support** inside the USLege application.

If any content on this site is inaccessible to you, we will provide it in an alternative format on request.

USLege, Inc.  
support@uslege.ai