@{
    ViewData["Title"] = "Accessibility Statement";
}

<div class="container py-5" style="max-width:860px">

    <h1 class="h3 fw-bold mb-1"><i class="bi bi-universal-access me-2 text-primary"></i>Accessibility Statement</h1>
    <p class="text-muted small mb-4">Last Updated: April 9, 2026</p>

    <p class="lead mb-4">
        Powder Coating Logix is committed to making our platform accessible to all users, including those with
        disabilities. We believe that every person running a powder coating business deserves full access to
        the tools that help them succeed.
    </p>

    <section class="mb-5">
        <h2 class="h5 fw-bold border-start border-primary border-3 ps-3 mb-3">Our Commitment</h2>
        <p>
            We strive to conform to the <strong>Web Content Accessibility Guidelines (WCAG) 2.1, Level AA</strong>,
            published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content
            more accessible to people with disabilities, including visual, auditory, physical, speech, cognitive,
            language, learning, and neurological disabilities.
        </p>
    </section>

    <section class="mb-5">
        <h2 class="h5 fw-bold border-start border-primary border-3 ps-3 mb-3">What We've Done</h2>
        <ul>
            <li class="mb-1"><strong>Semantic HTML:</strong> We use proper heading hierarchy, landmark elements (<code>&lt;nav&gt;</code>, <code>&lt;main&gt;</code>, <code>&lt;footer&gt;</code>), and ARIA attributes to convey structure to screen readers.</li>
            <li class="mb-1"><strong>Keyboard navigation:</strong> Core workflows can be completed using keyboard navigation alone.</li>
            <li class="mb-1"><strong>Color contrast:</strong> Text and interactive elements meet minimum contrast ratios against their backgrounds.</li>
            <li class="mb-1"><strong>Focus indicators:</strong> Visible focus outlines are preserved on interactive elements.</li>
            <li class="mb-1"><strong>Form labels:</strong> All form inputs have associated labels and descriptive error messages.</li>
            <li class="mb-1"><strong>Responsive design:</strong> The application adapts to different screen sizes and supports browser zoom up to 200% without loss of functionality.</li>
            <li class="mb-1"><strong>Alternative text:</strong> Images that convey information include descriptive alt text.</li>
            <li class="mb-1"><strong>Bootstrap 5:</strong> Our UI framework includes built-in accessibility features that we build on.</li>
        </ul>
    </section>

    <section class="mb-5">
        <h2 class="h5 fw-bold border-start border-primary border-3 ps-3 mb-3">Known Limitations</h2>
        <p>
            We are actively working to improve accessibility across all areas of the application. Some areas
            that we know are not yet fully conformant include:
        </p>
        <ul>
            <li class="mb-1"><strong>Complex charts and graphs</strong> (in Reports) — visual data is not yet accompanied by tabular data alternatives. We plan to add data table equivalents in a future release.</li>
            <li class="mb-1"><strong>Drag-and-drop interfaces</strong> (Job Priority Board, Oven Scheduler) — these currently lack keyboard-accessible equivalents. Workarounds exist via the standard list views.</li>
            <li class="mb-1"><strong>PDF exports</strong> — generated PDFs (invoices, work orders) are not currently tagged for screen reader accessibility.</li>
            <li class="mb-1"><strong>Third-party components</strong> — the Stripe payment element and some calendar widgets are third-party and may not fully conform to WCAG 2.1 AA.</li>
        </ul>
    </section>

    <section class="mb-5">
        <h2 class="h5 fw-bold border-start border-primary border-3 ps-3 mb-3">Assistive Technology Compatibility</h2>
        <p>
            We test the core application with the following assistive technologies:
        </p>
        <ul>
            <li>NVDA with Firefox (Windows)</li>
            <li>VoiceOver with Safari (macOS and iOS)</li>
            <li>Keyboard-only navigation (Chrome, Edge, Firefox)</li>
        </ul>
        <p class="small text-muted">
            Other combinations may work but have not been formally tested.
        </p>
    </section>

    <section class="mb-5">
        <h2 class="h5 fw-bold border-start border-primary border-3 ps-3 mb-3">Need Help?</h2>
        <p>
            If you experience any accessibility barriers while using Powder Coating Logix, or if you need
            content in a different format, please contact us:
        </p>
        <address class="ps-3">
            <strong>Powder Coating Logix — Accessibility</strong><br />
            Email: <a href="mailto:support@powdercoatinglogix.com">support@powdercoatinglogix.com</a><br />
            Subject line: <em>Accessibility Request</em>
        </address>
        <p>
            We aim to respond to accessibility requests within <strong>2 business days</strong>.
            Please describe the barrier you encountered and what you were trying to do — this helps us
            prioritize fixes and provide an immediate workaround where possible.
        </p>
    </section>

    <section class="mb-5">
        <h2 class="h5 fw-bold border-start border-primary border-3 ps-3 mb-3">Formal Complaints</h2>
        <p>
            If you are not satisfied with our response to your accessibility request, you may contact the relevant
            supervisory authority in your jurisdiction. In the United States, the Department of Justice Civil Rights
            Division handles ADA-related complaints.
        </p>
    </section>

    <section class="mb-5">
        <h2 class="h5 fw-bold border-start border-primary border-3 ps-3 mb-3">Ongoing Improvement</h2>
        <p>
            Accessibility is not a one-time checkbox — it is an ongoing commitment. We review and improve
            accessibility with each release. If you notice a regression or have a suggestion, please let us know.
        </p>
    </section>

    <hr />
    <p class="text-muted small text-center mt-4">
        &copy; @DateTime.UtcNow.Year Powder Coating Logix &nbsp;&middot;&nbsp;
        <a asp-controller="Home" asp-action="TermsOfService" class="text-decoration-none">Terms of Service</a> &nbsp;&middot;&nbsp;
        <a asp-controller="Home" asp-action="Privacy" class="text-decoration-none">Privacy Policy</a>
    </p>

</div>