Legal

Accessibility statement

Effective March 1, 2025 · Last reviewed March 1, 2025

1. Commitment

Ladakh Goods LLC wants anyone to be able to read a spec sheet, compare two products, and check out. Accessibility is treated as a build requirement here, not a cleanup task. Our conformance target is Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

We don't run an overlay widget. Overlays tend to fight the underlying markup, so the work happens in the HTML and CSS instead.

2. What's implemented

• Semantic structure: one h1 per page, ordered headings, landmarks (header, nav, main, footer), and a skip link as the first focusable element.
• Keyboard operability: every control is a real button or link. Filters, quantity steppers, gallery thumbnails, the mobile menu, and the cookie banner all work from the keyboard. Nothing is hover-only.
• Visible focus: a 2px terracotta outline with offset on every focusable element, against both the cream background and white cards.
• Contrast: body text is #1b1a18 on #faf8f5 (about 15:1). Secondary text is at least 4.6:1. Buttons meet 4.5:1 in both default and hover states. Footer text was raised to pass on the dark stone background.
• Responsive: fluid from 320px up, no horizontal scroll, no fixed-width traps, and 44px minimum tap targets for icon controls.
• Text scaling: layout holds at 200% zoom and with a 200% default font size. Sizes are in relative units.
• Images: every illustration is inline SVG. Decorative ones carry aria-hidden; informative ones carry role="img" with a descriptive label.
• Motion: prefers-reduced-motion disables smooth scrolling, hover lifts, and transitions.
• Forms: every field has a persistent visible label, hints are wired with aria-describedby, errors are announced in live regions, and focus moves to the first invalid field on submit.
• Announcements: cart changes, filter result counts, and form outcomes are exposed as live regions so they aren't silent.
• Zoom and reflow: no content is lost or clipped at 400% in a 1280px viewport, and reading order matches visual order.
• Native disclosure: FAQ items use details/summary, so they work with screen readers and no JS.

3. Known gaps

Being straight about these is more useful than claiming a clean sheet:

• Product illustrations are stylized. A screen-reader user gets shape, color, and form described, but not photographic detail. Every spec that matters is in the table as text, so nothing is image-only.
• The cart is JavaScript-dependent. Local storage needs JS. With JS off, the cart page shows the empty state and the "add to cart" buttons do nothing. A no-JS notice is on the cart page.
• Suction-sound and vibration are, obviously, not conveyed. The noise figure and a plain-language comparison ("quieter than a fridge") are the substitute.
• Cookie banner focus management is not a full modal trap — it's a non-blocking region, so focus is never hijacked, but a screen-reader user may reach it late in the reading order.
• Google Fonts is a third-party request. If it's blocked, the stack falls back to Helvetica/Arial with no loss of function.
• Third-party checkout (when live) will be its own accessibility surface, outside our direct control. We'll pick a provider that publishes a VPAT.

4. Testing

Manual keyboard passes and screen-reader checks (VoiceOver on Safari and macOS, NVDA on Windows Firefox) are run on every template before release. Zoom to 200% and 400% is checked alongside. Automated checks cover contrast and landmark structure but never decide a release on their own — they miss too much.

Last full manual audit: February 2025. External audit — to schedule

5. Compatibility

Built for current versions of Chrome, Safari, Firefox, and Edge on desktop and mobile, plus iOS and Android screen readers. It should degrade sanely on older browsers; the newest CSS features (color-mix, backdrop blur) are cosmetic only.

6. Tell us about a barrier

If something blocks you, email hello@ladakhtouroperators.com with "Accessibility" in the subject. Tell us the page, what you were doing, and your setup if you know it. Screenshots help but aren't required.

We acknowledge within 2 business days and aim to fix or provide a workaround within 10. If the fix takes longer, we tell you the plan rather than going quiet.

Prefer the phone? Phone support — to confirm

7. Alternatives

Can't use the site at all? Email us and we'll take an order by message — including reading out specs, sizes, and care instructions — and send a payment link when you're ready.

8. Formal complaints

If our response doesn't resolve it, ask for the founder in the same thread. Beyond us, the route is your state's consumer protection office or, for a public entity comparison, the DOJ's ADA information line. This is a private business, so ADA Title III is the relevant frame.

9. Contact

Ladakh Goods LLC · 1123 N Orange St, Suite 204, Wilmington, DE 19801 · hello@ladakhtouroperators.com