Accessibility Statement

Our commitment

AOQ Consulting, LLC wants Sealpair to be usable by everyone, including people who use assistive technology like screen readers, screen magnifiers, voice control, or keyboard-only navigation. We treat the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, as our target — this statement describes where things stand, not a claim of full or certified conformance.

What we've done

• A "skip to main content" link at the top of every page for keyboard users.
• Semantic HTML throughout — real headings in order, real <button>/<a>/<label> elements rather than styled <div>s standing in for them, and every form field associated with a visible label.
• Decorative icons and glyphs are hidden from screen readers so they don't add noise around text that already says the same thing.
• Form and upload errors are announced to screen readers as they appear, not just shown visually.
• Visible focus indicators on every interactive element, for people navigating by keyboard.
• Toggle-style buttons (like the photo/video/audio switch on the upload form) expose their pressed state to assistive technology, not just via color.

Known limitations

• The photo annotation tool (circling damage on a photo) is a pointer/touch drawing surface with no keyboard-operable equivalent yet. Annotating a photo currently requires a mouse, trackpad, or touchscreen.
• Downloaded PDF reports are generated for print/visual layout and haven't been separately tested for PDF accessibility (tagged structure, reading order for screen readers).
• We haven't run a full color-contrast audit against every text/background combination in the app; most of the interface uses Tailwind's default palette at weights chosen for readability, but we can't yet claim every combination meets WCAG AA contrast ratios.

We're working through these as ongoing improvements rather than treating this as a finished project.