Accessibility Statement

Our Commitment

Legal AI Governance is operated by Desired Path Consulting LLC. We believe that the legal-compliance information published on this Site, including the state bar AI ethics tracker, the AI sanctions case database, the court orders tracker, the downloadable templates, and the newsletter, should be available to every attorney and law firm staff member who needs it, regardless of disability, assistive technology, or browsing context. We design and develop the Site with that goal in mind and we treat accessibility issues as bugs.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA define how to make web content more accessible to people with disabilities. legalaigovernance.com substantially conforms with WCAG 2.1 Level AA based on our most recent audit, completed on 2026-04-29.

"Substantially conforms" means most of the Site fully meets the standard, with one known exception described under Known limitations below. We do not claim full conformance because part of the Site (the Tally newsletter form) is provided by a third-party vendor whose accessibility we cannot independently verify.

Audit summary, completed 2026-04-29:

• Lighthouse accessibility score of 100 out of 100 on every audited URL
• Zero hard color-contrast failures (104 foreground / background pairs computed)
• All Serious findings (10) and all Moderate findings (8) remediated and verified by re-scan
• Method: combined automated scanning (axe-core, pa11y htmlcs, Lighthouse) on representative URLs across all page types, programmatic accessibility-tree extraction for shared templates, manual code review of layouts and components, and computed contrast for all color pairs
• Standards: WCAG 2.1 Level AA, with WCAG 2.2 Level AA additions also met where applicable

Measures We Take

We treat accessibility as part of normal development rather than a separate workstream. Concretely, this means:

• Semantic HTML on every page: one <h1> per page, ordered headings, proper landmarks, real <table> markup with column scopes, real <button> elements for buttons, ARIA only when semantic HTML cannot do the job
• A skip-to-content link as the first focusable element on every page
• aria-current on breadcrumbs, in-page tables of contents, and the active section in the navigation
• aria-pressed on filter pills so screen-reader users know which filters are active
• aria-live="polite" on filter result counts so updates are announced
• Visible focus indicators on every interactive element, with both :focus-visible and :focus rules so older browsers do not lose them
• Touch targets at least 24 CSS pixels (per WCAG 2.2 SC 2.5.8), with primary call-to-action buttons sized at 44 CSS pixels
• Hover-only effects scoped to (hover: hover) so they do not stick on touch devices
• font-size: 16px on form inputs to suppress iOS auto-zoom
• prefers-reduced-motion override that disables transitions and animations for users who request reduced motion at the OS level
• Mobile-friendly layouts that reflow without horizontal scrolling at 320 CSS pixels wide and at 200% zoom
• Status information conveyed by both color and text label, never by color alone
• Consistent navigation, identification, and footer across the Site

Known Limitations

We track accessibility issues openly. The list below is what we know about today; if you find something not listed here, please let us know.

Newsletter sign-up form (third-party iframe). The newsletter sign-up form on the home page and at /newsletter/ is hosted by Tally and rendered inside an iframe. The iframe carries a descriptive title, but the form fields, validation messages, and submit control inside the iframe are under Tally's control rather than ours. We have not independently verified the iframe's WCAG conformance. If you cannot complete the form because of an accessibility barrier inside the iframe, email brian@desired-path.com with the same information you would have submitted and we will add you to the list manually.

Live screen-reader pass pending. The 2026-04-29 audit included programmatic accessibility-tree extraction for representative templates, which is the data screen readers consume, but we have not yet completed a live audio pass with NVDA, JAWS, or VoiceOver. Live screen-reader testing is on our follow-up list. In the meantime, please tell us if any element on the Site reads incorrectly with your screen reader.

Browser and Assistive Technology Compatibility

legalaigovernance.com is designed to work with:

• The two most recent major versions of Chrome, Edge, Firefox, and Safari on desktop and mobile
• Screen readers including NVDA, JAWS, VoiceOver, and TalkBack on the same browsers
• Keyboard-only navigation
• OS-level zoom up to 200%, browser zoom up to 200%, and viewport widths down to 320 CSS pixels
• OS-level reduced-motion preferences

The Site does not require JavaScript for primary content; the trackers, bar opinion summaries, court orders, case writeups, and templates all render and remain readable with JavaScript disabled. Some interactive enhancements (filter pills, the dismissible deadline banner, the mobile navigation menu) require JavaScript to function.

How to Report an Accessibility Issue

If you encounter any accessibility barrier on legalaigovernance.com, including a problem not listed above, please email brian@desired-path.com with "accessibility" in the subject line. To help us reproduce and fix the issue quickly, please include where you can:

• The URL where you encountered the problem
• What you were trying to do
• What the barrier was (for example, "the filter pills do not announce their pressed state in NVDA," "the deadlines text is too low contrast," "I cannot reach the newsletter submit button by keyboard")
• Your browser, operating system, and any assistive technology you were using (with versions if you have them)

We aim to acknowledge accessibility reports within five business days and to fix verified issues promptly, prioritizing barriers that block task completion. If a fix requires a vendor change (for example, the Tally iframe described above), we will tell you what we found and what the workaround is in the meantime.

We re-audit the Site against WCAG 2.1 AA at least annually and after any substantial change to layouts or shared components. The next planned audit cycle is 2027-04.