Accessibility Statement
Nexture AI LLC
Effective Date: September 28, 2026
This document was last reviewed and updated on the effective date above.
Brand notice. This service is offered publicly under the name MiaSure. "MiaSure" is a trade name of Nexture AI LLC, the Wyoming limited liability company that operates the Service and is your contracting party under this document. Any reference herein to "Nexture AI," "the Company," "we," "us," or "our" means Nexture AI LLC operating as MiaSure.
Nexture AI LLC is committed to ensuring that the MiaSure platform is usable by insurance professionals and their clients regardless of ability, and regardless of whether they navigate with a mouse, a keyboard, a screen reader, magnification, or another assistive technology.
1. Conformance Status
MiaSure is designed and tested against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C).
Current status: partially conformant. "Partially conformant" means that most of the platform meets the WCAG 2.1 Level AA success criteria, and that we have identified, documented, and are actively remediating the areas that do not. We publish this status honestly rather than claiming full conformance, because an overstated accessibility claim is itself a barrier: it tells a user that a problem they are experiencing does not exist.
The conformance target applies to the authenticated MiaSure web application and its public marketing and legal pages.
2. Measures We Take
Accessibility is enforced in our engineering process, not only reviewed at release:
- Automated gates in continuous integration. Two blocking checks run on every change. One checks that the text and interface colour pairings in our design system meet the WCAG AA contrast ratios (4.5:1 for body text, 3:1 for large text and for the boundaries of interface controls). The other checks our source code for the most common keyboard, naming, and focus defects: interactive elements that cannot be reached or operated by keyboard, icon-only controls without an accessible name, and dialogs that do not manage focus. Automated checks cannot detect every barrier, which is why we also test manually (Section 6).
- Keyboard operability. Functionality is designed to be available from a keyboard alone, without requiring specific timings for individual keystrokes. Pages are designed to offer a "Skip to main content" link as the first focusable element. Dialogs are designed to keep focus inside them while open, close on Esc, and return focus to the control that opened them.
- Assistive technology support. The platform is designed so that images convey their meaning through text alternatives, decorative graphics are hidden from assistive technology, controls expose an accessible name and role, and page structure uses real landmarks and headings.
- Colour independence. The platform is designed so that colour is not the sole means of conveying information, indicating an action, or distinguishing a visual element: status is carried by text, an icon, or a shape in addition to colour, so that the platform remains usable with colour vision deficiencies.
- Design system enforcement. Colours are defined once as design tokens and validated centrally, which makes it harder for an individual screen to depart from the accessible palette.
3. Technical Specifications
Accessibility of MiaSure relies on the following technologies to work with your web browser and any assistive technologies you use: HTML, WAI-ARIA, CSS, and JavaScript. The platform is tested on current versions of Chrome, Edge, Firefox, and Safari.
4. Known Limitations
Despite our efforts, some limitations remain. We list them so that you are not left guessing:
- PDF exports are not tagged. When you generate a deliverable in MiaSure — a Summary of Insurance, comparison, program review, or report — exporting it to PDF may not produce a complete tagged-PDF structure, so the PDF is not the best format for use with a screen reader. For the deliverables you create, an accessible version is available without a request: the deliverables you generate are also available as a web page inside the platform, and that web view — not the PDF — is the format this statement covers. It is navigable by keyboard and readable by assistive technology. The same deliverable can also be exported to Word (.docx) or Excel (.xlsx), which preserve heading and table structure.
This commitment is limited to deliverables that you generate in your own MiaSure account. It does not extend to a deliverable that another MiaSure user shares with you, nor to any file sent to you outside the platform. Sharing transmits the exported PDF, not the underlying web view, so a deliverable you receive from someone else is an ordinary document that we have no ability to alter. If you need an accessible version of a deliverable that was shared with you, ask the MiaSure user who produced it — from their own account they can supply the web view, or the Word or Excel export, which is the accessible source this statement covers. - Complex data tables. Some dense policy-data tables and schedules support keyboard navigation but do not yet implement a full grid interaction pattern. The underlying data is available through alternative views.
- Third-party components. Certain interface components and embedded third-party services are not fully under our control. We track their accessibility defects with their vendors and replace components where remediation is not forthcoming.
- Internal engineering tools. Diagnostic pages restricted to our own engineering staff are out of scope for this statement and are not accessible to customers.
- Criteria not yet fully evaluated. We have not yet completed an evaluation of the platform against the following WCAG 2.1 success criteria, and some screens may not meet them: 1.4.10 Reflow (use at 320 CSS pixels wide without two-dimensional scrolling), 1.4.12 Text Spacing (no loss of content when letter, word, line, and paragraph spacing are increased), and 2.3.3 Animation from Interactions (a Level AAA criterion we nonetheless aim to support by honouring the operating-system "reduce motion" setting). Some authentication screens, the share and client-portal screens, and the insured-client screens are not yet included in our automated post-release accessibility checks.
- Uploaded source documents. Insurance documents that you upload are third-party content. Where a source PDF is a scanned image without a text layer, we extract its content so the data becomes accessible in the platform, but the original file remains as its issuer produced it.
5. Feedback and Requests
We welcome your feedback on the accessibility of MiaSure. If you encounter a barrier, or need information or a deliverable in an alternative accessible format, please contact us:
- Email: [email protected] (please include "Accessibility" in the subject line)
- Responsible individual: David Hughes, President, Nexture AI LLC
- Postal: Nexture AI LLC, 1521 Alton Rd. PMB 106, Miami Beach, FL 33139, United States
Please tell us the page or feature involved, what you were trying to do, and the assistive technology and browser you were using. We aim to acknowledge accessibility reports within 5 business days and to provide a remediation plan or an accessible alternative within 30 days. Reports of barriers that prevent access to core functionality are treated as priority defects.
6. Assessment Approach
Nexture AI LLC assessed the accessibility of MiaSure by the following approaches:
- Self-evaluation, including a full internal audit of interactive controls, text alternatives, and colour contrast completed on August 2, 2026.
- Automated conformance testing enforced continuously in our build pipeline, as described in Section 2.
- Manual keyboard-only and screen-reader testing of primary workflows.
We have not yet commissioned an independent third-party accessibility audit. When we do, we will publish the resulting report and, where requested for procurement, an Accessibility Conformance Report (ACR) based on the Voluntary Product Accessibility Template (VPAT).
7. Applicable Standards and Regulations
This statement is made with reference to the following frameworks. Their applicability depends on your jurisdiction and the nature of your organisation:
- Americans with Disabilities Act (ADA), Titles II and III (United States). US courts have widely treated commercial websites and web applications as subject to the ADA's accessibility obligations, with WCAG 2.1 Level AA applied as the practical benchmark.
- Section 508 of the Rehabilitation Act (United States). Applies where a federal agency procures the Service. Section 508 incorporates WCAG 2.0 Level AA by reference; conformance is evidenced through a VPAT-based ACR, available on request.
- Section 504 of the Rehabilitation Act (United States). May apply to recipients of federal financial assistance.
- European Accessibility Act, Directive (EU) 2019/882. Obligations for covered services took effect on 28 June 2025. The harmonised European standard EN 301 549 incorporates WCAG 2.1 Level AA.
- Accessibility for Ontarians with Disabilities Act (AODA), Ontario, Canada, and the Accessible Canada Act.
- Equality Act 2010 (United Kingdom), which requires reasonable adjustments for disabled users.
Note on state-level requirements. Certain US states impose additional obligations on insurance producers and on entities serving state agencies. Where you are contractually or statutorily required to demonstrate accessibility conformance for a procurement, contact us for a current ACR.
This statement is informational and does not constitute legal advice. It does not create warranties beyond those set out in the Terms of Service, and it does not waive any limitation of liability contained in them.
8. Enforcement and Escalation
Accountability for our accessibility programme sits with David Hughes, President of Nexture AI LLC. If you contact us about an accessibility barrier and are not satisfied with our response, you may escalate to [email protected] marked for his attention. Users in jurisdictions with a statutory enforcement body may also contact that body directly; nothing in this statement limits your rights under applicable law.
9. Changes to This Statement
We review this statement at least annually, and whenever a significant change to the platform affects its accessibility. The effective date at the top of this page reflects the most recent review.