6. Accessibility Statement (Preliminary Working Draft)
6.1 Accessibility Target
[LEGAL OPERATOR NAME], doing business as BiteShark aims to make local food-spot discovery, account sign-in, pickup pagers, vendor tools, policy pages, and administration screens usable for everyone, using the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our ongoing design and engineering target.
6.2 Practices Implemented in the Current Staging Build
- Keyboard navigation, modal containment & visible focus: Interactive buttons, mode tabs, links, policy skip-links, form controls, and admin checklists are operable by keyboard with visible focus indicators. Modal dialogs (
role="dialog",aria-modal="true") place initial focus inside the dialog, trapTab/Shift+Tabwhile locking background content viainert, supportEscapedismissal where safe, provide named close buttons, and restore focus to the invoking control upon close. - Programmatic labels, field validation & understandable date entry: Registration, event inquiry, onboarding, and age-eligibility forms pair inputs with programmatic labels, required-field instructions,
aria-invalidstates, androle="alert"error summaries rather than relying on color or opaque calendar widgets. - Status text beyond color & non-repetitive live regions: Open/closed states (“● OPEN”, “◐ EST. OPEN”, “○ CLOSED”), outcome banners (“⏳ Working”, “💾 Saved locally”, “✓ Saved to account”, “📨 Submitted for review”, “⚠ Outcome uncertain”), moderation tags, and readiness stages pair text labels and symbols with color. Pickup pager polling updates timestamps quietly without repeating
aria-liveannouncements every poll cycle unless order status changes. - List-view alternative to interactive maps: Discovery provides a full text List view alongside the interactive Leaflet map so users do not need to pan or tap map pins to browse or filter Sonoma County food spots.
- Zoom, narrow-screen reflow & reduced motion: Discovery, booking dialogs, sign-in/signup forms, policy pages, and admin workspaces reflow on narrow mobile viewports (320px–375px) and at 200% browser zoom, and honor
prefers-reduced-motion: reduceacross CSS transitions, map fly-to animations, and sample-order auto-advance.
6.3 Honest Testing Status & Known Limitations
- Third-party map canvas: Interactive Leaflet / OpenStreetMap map tiles can be harder to navigate with screen readers than structured lists; we recommend switching to the List view toggle for assistive-technology navigation while we continue improving map-marker announcements.
- Vendor-submitted text & attachments: Uploaded vendor onboarding documents and user-written reviews may not always include complete alt text or accessible PDF structure.
6.4 Reporting Accessibility Barriers
Signed-in users on staging can report accessibility issues through Profile → Support & issues. Before public rollout, BiteShark will publish a dedicated, sign-in-free accessibility feedback email address and response target so anyone encountering a barrier can request assistance without needing an account.
[UNRESOLVED — CONFIRMATION REQUIRED] Pre-Launch Accessibility Work
- Manual assistive-technology testing: Complete structured manual testing with desktop and mobile screen readers (VoiceOver, NVDA/TalkBack), high-contrast modes, and reduced-motion settings across all primary customer and vendor journeys, and remediate discovered defects.
- Unauthenticated accessibility contact channel: Confirm [LEGAL OPERATOR NAME] and publish a monitored email/contact method for users who cannot complete sign-in due to an accessibility barrier.
- Legal review: Review statement language and remediation commitments with counsel prior to public rollout.