HEALTHY LITTLE COOKS, LLC UNIVERSAL DIGITAL ACCESSIBILITY STATEMENT & SAFE HARBOR CLEARANCE
EFFECTIVE DATE: July 18, 2026
LAST MODIFIED: July 18, 2026
SECTION 1: COMMITMENT TO ACCESSIBILITY AND COMPLIANCE BENCHMARKS
1.1 Core Mandate
Healthy Little Cooks, LLC (“the Company,” “we,” “us,” or “our”) is fundamentally committed to ensuring digital accessibility, inclusion, and equal user-experience utility for all individuals, including those with visual, auditory, motor, or cognitive disabilities. We firmly believe that our digital portals should be fully usable and easily navigable by every parent, child, and community coordinator regardless of assistive technology configurations.
1.2 Technical Conformance Standards
To satisfy this commitment, the Company actively builds, audits, and remediates its consumer storefronts, submission nodes, and member portals to align tightly with the Web Content Accessibility Guidelines (WCAG) 2.2, Level A and Level AA success criteria. These international technical parameters dictate that web content must be:
Perceivable: Information and user-interface components must be presented in formats readable via assistive technology or screen readers.
Operable: Portals must be entirely navigable and interactive utilizing a keyboard alone, voice commands, or secondary assistive hardware.
Understandable: Operational pathways, form inputs, and error messages must be clear, predictable, and simple to correct.
Robust: The underlying software architecture must maintain native compatibility with contemporary web browsers and screen-reading platforms.
SECTION 2: ADAPTIVE CORE PORTAL SCOPE & COMPATIBILITY MATRICES
This policy governs all digital endpoints maintained across our primary systems, including but not limited to HealthyLittleCooks.com, HLCMembers.com, and all child directories containing parent dashboards, video submission forms, host site setups, and public online voting modules.
2.1 Native Assistive Technologies Supported
The Platform is engineered to maintain functional compatibility with prevailing industry-standard accessibility combinations, including:
- Screen Readers: Native operation alongside JAWS, NVDA (Windows frameworks), and Apple VoiceOver (macOS and iOS architectures).
- Keyboard-Only Infrastructure: System-wide interactive components built to allow full tab-indexing, focus indication visual guides, and interactive button firing without the structural requirement of a mouse or trackpad.
- Visual Adaptations: Layout elements engineered to withstand browser text magnification scaling up to 200% without structural text clipping, overflow blocks, or critical layout breakdown.
SECTION 3: SYSTEM LIMITATIONS AND PLANNED REMEDIATION WAVES
Despite our continuous code-level development protocols, the dynamic environment of a multimedia tournament platform means that minor, transient accessibility limitations can occasionally manifest. We actively track, isolate, and address these issues.
3.1 Known Transactional Limitations
Users may encounter structural friction points across these distinct vectors:
- User-Generated Video Payloads: Section 4 of the Official Competition Rules permits parents to independently record and transmit 2-minute video files of minor child cooking sessions. Because these assets are uploaded externally by the public, they may initially lack synchronized, human-reviewed closed captioning data or audio descriptions.
- Dynamic Data Visualizations: Real-time data tables displaying regional public voting volumes, localized bracket leaderboards, or specific administrative scorecards may occasionally conflict with linear reading-order patterns utilized by vintage screen readers.
- Sponsor Assets: Third-party corporate sponsor logos, brand badges, or external payment processor components may be subject to layout parameters managed outside our proprietary source code environment.
3.2 Dynamic Remediation Action Schedule
The Company conducts recurring manual and automated software engineering audits to trace accessibility anomalies. Remediation tickets generated by these checks are injected into our standard product development sprints to ensure constant, fluid improvement of input field tagging, color contrast optimization, and ARIA label implementation.
SECTION 4: PRE-LITIGATION SAFE HARBOR FEEDBACK PATHWAY
4.1 Formal Notice, Grievance, and Resolution Process
If you encounter a technical barrier, accessibility roadblock, or navigational limitation that impairs your ability to register an account, upload a recipe submission, vote for a finalist, or purchase retail items, you are granted a direct, immediate communication track to bypass legal friction and secure immediate administrative support.
- Primary Contact Channel: Email our dedicated internal accessibility clearing desk at: accessibility@healthylittlecooks.com.
- Required Disclosure Content: To help our small team resolve the barrier quickly, please include: (1) your full contact name; (2) the specific page URL where the barrier was encountered; (3) a brief description of the operational issue; and (4) the specific browser and assistive software platform you were utilizing.
4.2 Corporate SLA Response Commitment
Upon receipt of an accessibility barrier report, our administrative team will review the issue and contact you within five (5) business days. We will provide an alternative, manual means of secure access—such as manually processing a recipe submission via email or casting a validated public vote on your behalf—while our developers work to resolve the code-level issue.