Skip to content

Accessibility at Crop Help

Inclusive by default. We design, build, and test for access—and keep improving with real feedback.

Read our accessibility statement Share accessibility feedback

We aim for WCAG conformance and continuous improvement.

Accessibility statement

Commitment & principles

WCAG 2.2 AA

Crop Help is committed to providing equitable access to our website, programs, and services. We design, build, and test for accessibility from the start and improve continuously with community feedback. Our approach is grounded in dignity, independence, integration, and equal opportunity.

  • Accessibility considered at strategy, design, content, and engineering stages.
  • Support for assistive technologies and inclusive interaction patterns.
  • Ongoing training for staff and contributors whose work affects accessibility.
Scope
Marketing site, documentation, and in-product interfaces
Audit cadence
Quarterly self-assessments; interim fixes as issues are discovered
Last updated

Standards & conformance

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. Conformance is currently self-assessed using a mix of automated testing, expert reviews, and assistive technology checks.

Methods used

  • Automated checks (color contrast, landmarks, names/roles/values)
  • Manual keyboard testing (tab/shift-tab, Enter, Space, Esc)
  • Screen reader spot-checks
  • Real-user feedback from learners, families, and partners

Assistive tech (sample)

  • VoiceOver (Safari, iOS)
  • NVDA (Firefox/Chrome)
  • JAWS (Chrome)
  • TalkBack (Android)

Supported browsers

  • Current and previous major versions of Chrome, Safari, Firefox, and Edge

We honor reduced-motion preferences, provide visible focus rings, aim for ≥ 4.5:1 text/UI contrast, and target 44×44px minimum hit areas where applicable.

How we build for access

Design

  • Semantic hierarchy and clear headings
  • Theme-aware tokens for color and elevation
  • Readable typography and spacing
  • Motion kept subtle; alternatives when motion conveys meaning

Content

  • Descriptive links and alt text for meaningful images
  • Captions or transcripts for time-based media
  • Plain-language first; glossary where needed
  • Language metadata and programmatic labels

Engineering

  • Keyboard operability and logical tab order
  • Names/roles/values via native HTML first, ARIA where appropriate
  • ARIA live regions for important status messages
  • Continuous linting and CI checks for regressions

Accommodations, disruptions, & third-party content

Reasonable accommodations

  • Alternate formats (large print, accessible PDF, text-only) upon request
  • Support persons and service animals welcome at our venues (where permitted by the host facility)
  • Program materials available in advance on request

Disruptions & notices

  • We post planned/unplanned disruption notices with alternatives and expected duration
  • We update notices as circumstances change

Third-party & legacy content

  • Some third-party embeds and older PDFs may not fully meet WCAG 2.2 AA
  • We evaluate alternatives and remediate high-impact issues first

Roadmap

Q4 2025

  • Caption audit for legacy videos
  • Contrast pass on archived blog templates

Q1 2026

  • PDF accessibility remediation playbook
  • Expanded AT test matrix and scripted journeys

We update this roadmap as work ships and new priorities emerge.