Accessibility Statement

Last updated: May 17, 2026

DocketBreeze, LLC (“we,” “us,” or “DocketBreeze”) is committed to making our websites, web application, and mobile apps usable by as many people as possible, including people with disabilities. This statement describes our approach, the steps we take, known limitations, and how to request assistance or report a barrier.

1. Our commitment

Legal technology should not create unnecessary barriers for attorneys, clients, or firm staff. We design DocketBreeze so that essential case information—documents, timelines, deadlines, and client communications—can be reached through common assistive technologies and keyboard interaction, not only through mouse or touch input.

We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for the parts of the Services we control, and we improve accessibility on an ongoing basis as we ship new features.

2. What this covers

This statement applies to:

• The public marketing site at docketbreeze.com (home, pricing, features, blog, and related pages)
• The authenticated attorney and client web portal
• The DocketBreeze iPhone app available on the App Store

Some embedded third-party tools (for example, scheduling widgets) are provided by external vendors and may follow their own accessibility practices.

3. Measures we take

Depending on the surface, we work to include:

• Semantic structure: meaningful headings, landmarks, and page language (lang="en") so screen readers can navigate efficiently.
• Keyboard support: interactive controls reachable by keyboard; modal dialogs that trap focus while open and close with the Escape key.
• ARIA where appropriate: labels on dialogs, alerts, carousels, and other dynamic regions; decorative icons marked aria-hidden when adjacent text conveys the same information.
• Visible focus: focus styles on interactive elements so keyboard users can see where they are.
• Forms: associated labels, validation messages, and error states tied to fields.
• Plain-language content: client-facing summaries and notifications written in everyday language, which benefits many users including those with cognitive disabilities.
• Responsive layout: content reflows on smaller screens without requiring horizontal scrolling for core tasks.
• Security without sacrificing basics: encrypted sessions (256-bit TLS) alongside standard browser and platform accessibility APIs.
• Typography and color: a high-contrast palette for primary text and UI chrome; we continue to refine secondary text contrast where it falls short of WCAG targets.
• Motion: marketing animations respect prefers-reduced-motion where reduced motion is requested at the system level.
• Mobile: the iOS app supports platform accessibility features such as VoiceOver and Dynamic Type within Apple’s guidelines.

4. Compatible technologies

We test with current versions of major desktop and mobile browsers (Chrome, Firefox, Safari, and Edge) together with common assistive technologies such as NVDA, JAWS, and VoiceOver. Older browsers or assistive technology combinations may not support every feature.

5. Known limitations

Despite our efforts, some areas may be difficult to use:

• Uploaded documents: PDFs and scans uploaded to a matter depend on the accessibility of the source file; we display them as provided.
• Rich text editing: some editor regions in the workspace are still being improved for screen-reader labeling and keyboard workflows.
• Complex data views: large tables, timelines, and visual case maps may require additional navigation steps; we are working to strengthen headings, labels, and keyboard paths in these views.
• Third-party embeds: content loaded from external services may not fully meet our standards.
• Android app: the Android client is in development; until release, Android users should use the web portal in a mobile browser.

We treat accessibility feedback as product input and prioritize fixes that block access to core workflows (sign-in, viewing a case, reading a document summary, messaging, and calendar deadlines).

6. Request accommodations or report a barrier

If you have trouble using any part of DocketBreeze, we want to hear from you. Please include:

• The page or feature (URL if possible)
• What you were trying to do
• The assistive technology, browser, or device you use (for example, NVDA with Firefox on Windows, or VoiceOver on iPhone)

Contact us at support@docketbreeze.com or use the contact form and choose Accessibility as the topic. We will try to respond within a few business days and, when appropriate, offer an alternative way to access the information or complete the task while we work on a fix.

7. Formal complaints (United States)

If you are not satisfied with our response, you may have the right to file a complaint with the U.S. Department of Justice or your state’s civil rights office. We encourage you to contact us first so we can try to resolve the issue directly.

8. Changes

We may update this statement as our Services and accessibility practices evolve. We will post revisions here with an updated “Last updated” date.