Accessibility Statement

1. Commitment and scope

This Statement covers the public website, intake, free identification, analysis result, checkout handoff, secure order page, download and revision interfaces that MyLegalDocs AI directly controls. It also explains the limits affecting user uploads, mandatory government forms, generated DOCX/PDF files and third-party payment or linked websites.

The goal is effective access to the same core information and service, while recognizing that an individualized accommodation may be necessary where a technical barrier cannot be corrected immediately.

2. Legal and technical framework

The U.S. Department of Justice states that businesses open to the public must provide people with disabilities equal access to the goods and services they offer and communicate effectively where the Americans with Disabilities Act applies. DOJ web guidance identifies keyboard access, headings, sufficient contrast, zoom, text alternatives, error explanation, manual testing and a barrier-reporting path as relevant practices. DOJ Guidance on Web Accessibility and the ADA ↗

For private businesses, DOJ's Title III guidance describes general nondiscrimination, effective-communication and reasonable-modification duties but does not impose the federal-agency Section 508 standard on every private website. ADA Title III business guidance ↗

Section 508 applies to information and communication technology developed, procured, maintained or used by federal agencies. Its standards can provide useful technical guidance, but MyLegalDocs AI does not claim that Section 508 directly governs this private service merely because it links to federal courts or agencies. U.S. Access Board ICT and Section 508 Standards ↗

WCAG is used as a technical reference. It does not replace the controlling legal analysis and this Statement is not a certification. W3C Web Content Accessibility Guidelines 2.2 ↗

4. Keyboard navigation and visible focus

Users should be able to reach navigation, form fields, upload controls, disclosures, consent controls, buttons and links with standard keyboard commands. Focus should move in a logical order and remain visible. No core transaction should require a precision pointer gesture or drag-and-drop operation.

If focus is lost, trapped or obscured, report the page, control and browser. Include the keyboard command used and whether a screen reader was active.

5. Screen readers, labels and page structure

Controls are intended to have programmatic labels, and visual headings are intended to correspond to semantic heading structure. Progress states and important instructions should be available as text. Decorative imagery should not carry essential information.

Automatically extracted text from an uploaded scan may contain recognition errors. A screen reader's ability to read a user-supplied image or third-party PDF depends on the accessibility of that source file.

6. Vision, text resizing, zoom and color

The layout is designed to reflow at common mobile widths and browser zoom levels without making horizontal scrolling necessary for ordinary text content. Information should not be conveyed by color alone, and focus, required-field and error states should include text or shape cues.

Very large zoom, browser reader modes, user stylesheets and operating-system contrast settings can expose defects in complex layouts. A user who encounters clipped text or an unreachable control should request a correction or alternative.

7. Motion, timing and cognitive accessibility

Animations are decorative or explanatory and should not be necessary to understand or complete the transaction. Reduced-motion preferences are used where supported. The service avoids automatic recurring charges and attempts to explain each stage in plain language.

Security and payment sessions may expire. If a disability-related barrier prevents completion within a session, contact support for a reasonable alternative. A legal or court deadline is not extended by a website accommodation request.

8. Forms, instructions and error handling

Form fields should include visible instructions and machine-readable labels. Errors should identify the affected field and explain how to correct it. A user should not have to infer an error from red color alone.

The platform may reject unsupported files, excessive sizes, invalid email addresses, missing consent or unlawful service requests. These messages are part of the functional workflow and should remain understandable to assistive technology.

10. Third-party services and official resources

Stripe payment pages, email clients, linked court or agency websites, official forms, browser translation, reader modes and downloaded office/PDF software are controlled by third parties. MyLegalDocs AI cannot alter those interfaces directly.

A third-party limitation does not end the support inquiry. The service will identify the responsible interface and, where reasonably possible, offer an alternative route for the part it controls. It cannot change a mandatory government filing method or act as the government entity.

13. How to report a barrier

Email contact@mylegaldocsai.com with the subject “Accessibility Barrier.” Include:

• the page or workflow step;
• the task you were trying to complete;
• device, operating system and browser;
• assistive technology and version, where relevant;
• keyboard or gesture used;
• a concise description of the barrier and preferred contact method.

Do not send payment credentials or unnecessary case facts. Use an order identifier instead of attaching legal documents unless a secure method is requested.

14. Response and remediation process

A report is reviewed to determine whether the barrier is in the platform, a generated file, a user-supplied source or a third-party service. The response may provide an immediate workaround, request limited diagnostic information, create a correction task or provide a reasonable alternative.

Priority is based on whether the barrier blocks intake, payment, secure access, download or revision; the number of affected users; security; and whether a legal deadline is involved. The platform does not promise a fixed remediation time for every defect, but it will not treat a barrier report as resolved merely because an automated scan passes.

15. No unsupported conformance claim

The service does not state that it is “ADA certified,” because the ADA does not create a general private website certification issued by the Department of Justice. It does not state blanket WCAG 2.1 AA or WCAG 2.2 AA conformance without a documented audit covering the claimed scope.

Individual features may be designed and tested against WCAG success criteria. Any future conformance statement must identify the version, level, pages or workflows tested, date, methodology and known exceptions.

16. State-law and federal-program caveats

State disability, civil-rights, consumer and public-accommodation laws may create obligations or remedies in addition to the ADA. Their coverage differs by jurisdiction and facts. This Statement does not limit a mandatory right or represent that one federal standard displaces state law.

The 2024 DOJ Title II web and mobile rule applies to state and local government entities, not automatically to this private software service. Likewise, Section 508 governs federal-agency ICT and certain federal contexts. If the service is later provided under a government contract or program, additional contractual or statutory accessibility requirements may apply.

17. Changes and ongoing testing

The statement version and update date appear at the top. Accessibility is reviewed when core forms, navigation, pricing, checkout, order status, downloads or revisions change. Desktop and mobile behavior should be tested together. Material known limitations and remediation priorities may be updated without reducing a mandatory legal right.

18. Contact

Accessibility reports and requests for a reasonable alternative should be sent to contact@mylegaldocsai.com. Contractual operator details are available only in the Terms of Service and are not repeated on this page.