Accessibility Statement

The University of Arizona Nutritional Sciences & Wellness Foods Lab is committed to making flavorarchitect.dev usable by everyone, including people who navigate by keyboard, use screen readers, need strong color contrast, or benefit from plain structure and predictable controls. Accessibility is a design requirement of this tool, not an afterthought: it was built mobile-first and audited against the Web Content Accessibility Guidelines before launch.

flavorarchitect.dev aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the standard the U.S. Department of Justice adopted in April 2024 for state and local government web content under Title II of the Americans with Disabilities Act (28 CFR Part 35, incorporating WCAG 2.1 AA as the technical floor). As a public university resource, we hold ourselves to that floor and test beyond it against the newer 2.2 success criteria.

An automated and manual audit of every screen (October 2026) found:

• Text and interface colors meet or exceed the 4.5:1 contrast minimum at desktop and phone sizes.
• Interactive controls meet the WCAG 2.2 minimum target size of 24×24 CSS pixels, with primary actions at 44×44 or larger.
• Headings run in order (one h1 per page, no skipped levels) and each page has a single main landmark.
• Icon-only buttons carry accessible names; form fields have visible labels; filters use aria-pressed toggle buttons with group labels and live-region feedback.
• Print output is scoped and readable, and no content relies on color alone to convey meaning.

WCAG 3.0 is still a W3C working draft — no site can formally conform to it yet. We track its direction and already follow several of its emerging expectations: generous touch targets, visible focus indicators, semantic structure that assistive technology can rely on, and sensory & execution filters (texture profile, spoon level, friction reducers) that support neurodivergent users in the Prototype Library.

When WCAG 3.0 reaches a stable, testable stage, we will evaluate against it and update this statement.

• AI-generated recipe text. Prototypes are generated on demand. We structure the output into labeled sections, but the wording itself is machine-generated and may occasionally vary in reading clarity.
• Older library entries. Recipes saved before the sensory filters launched have no texture or spoon-level tags yet, so they do not appear when those filters are active.
• Screen-reader field testing. Our audit combines automated scanning with manual code review. It is not a substitute for testing with users of NVDA, JAWS, or VoiceOver — if you hit a barrier, tell us (below) and we will fix it.

If you encounter an accessibility barrier on flavorarchitect.dev — or need any content in an alternative format — email alanpruitt@arizona.edu. Describe the page and what went wrong; we aim to acknowledge reports within two business days and to fix confirmed barriers as quickly as the teaching calendar allows.

Formal accessibility concerns about The University of Arizona's digital resources may also be directed to the university's Disability Resource Center and IT Accessibility team through arizona.edu.

This statement is based on an automated WCAG 2.2 AA scan of all six screens at desktop (1280px) and phone (390px) widths, plus manual review of heading order, landmarks, keyboard operation, focus visibility, target sizes, and color contrast. The audit was last run on October 8, 2026.