Accessibility Statement

Our Commitment

The James Stanfield Company builds curriculum for learners with a wide range of abilities. We are committed to making stanfield.com and the Stanfield platform usable by as many people as possible, including students, teachers, parents, and administrators who rely on assistive technology.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C. These guidelines explain how to make web content more accessible to people with visual, motor, auditory, and cognitive disabilities.

Measures We Take

Accessibility is considered during design reviews, not bolted on after launch.
Pages are built from semantic HTML — headings, lists, landmarks, and form labels — so assistive technology can announce structure correctly.
Public pages are periodically tested with automated tools (axe-core, Lighthouse) and manual keyboard + screen-reader passes.
Engineers review accessibility as part of shipping new features, and regressions are treated as bugs.

Keyboard Navigation

All interactive elements — links, buttons, form fields, menus, and dialogs — can be reached and operated using a keyboard alone. Specifically:

Tab moves forward through interactive elements; Shift + Tab moves backward.
Enter and Space activate links and buttons.
Escape closes dialogs and menus.
A visible focus outline is shown on the currently focused element. We do not suppress the browser's focus ring.
Focus is not trapped in menus or overlays without an explicit way out.

Screen Reader Support

Stanfield is tested with modern screen readers, including:

VoiceOver on macOS and iOS (Safari)
NVDA on Windows (Firefox and Chrome)
TalkBack on Android (Chrome)

To support assistive technology we use:

Page titles that describe the page's purpose.
A single <h1> per page plus a meaningful heading outline.
Landmark regions (<header>, <nav>, <main>, <footer>) so users can jump between sections.
Descriptive text for every meaningful image via alt attributes. Decorative images use empty alt="" so they are not announced.
Form fields with associated <label> elements and error messages linked via aria-describedby.
ARIA attributes only where native HTML cannot express the pattern (for example, aria-expanded on disclosure buttons and aria-current on the active nav item).

Color and Contrast

Text is tested against the WCAG 2.1 Level AA contrast ratios:

4.5:1 for body text (all text 18px and below, or below 14px bold).
3:1 for large text (at or above 18px regular, or 14px bold).
3:1 for interactive component boundaries and meaningful UI icons.

Color is never the only way we convey information. Links are underlined on body copy, error states combine color with text, and required fields are marked in words as well as color.

Media and Captions

Stanfield is a digital-only curriculum. Our entire video library is closed-captioned for students who are deaf or hard of hearing, and captions are the default viewing experience for teachers delivering lessons in a live classroom.

Responsive and Zoom

Pages reflow cleanly down to 320 px wide without horizontal scrolling, and text can be zoomed to 200% in the browser without loss of content or functionality.

Student Experience

The student join flow is PIN-based and avoids timed interactions wherever possible. Student-facing activities are designed for large touch targets, simple navigation, and a reading level appropriate to the program. If a student uses an assistive device paired with a district Chromebook or iPad, Stanfield renders in the same supported browsers the device already uses.

Known Limitations

We are transparent about areas where we are not yet where we want to be. At the time of this update, known limitations include:

A small number of legacy blog posts contain images whose alt text is the filename rather than a description. We are working through the archive as we encounter them.
Some embedded third-party content (for example, payment and survey widgets) inherits accessibility from the vendor. We select vendors who publish their own accessibility conformance reports, but we cannot always modify their markup directly.
PDF handouts and printable materials produced by the Plus toolkit target the same standards as the web app, but older imported PDFs have not all been remediated. Let us know if you need an accessible copy of a specific document and we will prioritize it.

Compatibility

Stanfield is designed to work with the current and previous major release of Chrome, Firefox, Safari, and Edge. It is not designed for Internet Explorer.

Standards We Follow

WCAG 2.1 Level AA
Section 508 of the Rehabilitation Act (U.S. federal accessibility standard, which incorporates WCAG 2.0 AA)
FERPA and COPPA for student data handling, described in our Privacy Policy

Feedback

If you encounter a barrier using Stanfield, or if you need information in an alternative format, please tell us. We aim to acknowledge accessibility reports within two business days.

Email: hello@stanfield.com
Contact form: https://stanfield.com/contact

Please include the page URL, the browser and assistive technology you were using, and a description of the problem. That detail helps us reproduce and fix the issue quickly.

Enforcement

This statement describes our ongoing commitment, not a legal guarantee. We welcome feedback from anyone who finds barriers, and we treat accessibility reports with the same seriousness as any other bug report.