WCAG baseline
If ANCHOR becomes a state public entity/service, the DOJ Title II web/mobile rule makes WCAG 2.1 Level AA the technical baseline for covered state/local web content and mobile apps, subject to the rule’s details and exceptions.
Digital public service
The website is a door.
If a musician cannot find the rehearsal, complete the form, read the event information, operate the Music Port or understand what data is being requested, the program has created an access barrier before the person reaches music.
Production standard
Accessible by default. Preferences on top.
Large text, low-stim and reduced-motion controls are useful personal preferences. They do not replace semantic HTML, keyboard access, labels, contrast, captions, predictable focus, accessible forms and assistive-technology compatibility.
Vendor responsibility
A public entity cannot assume a contractor’s portal is somebody else’s accessibility problem. Procurement needs accessibility requirements, testing and remediation terms.
Privacy minimization
Public artist information, program administration and sensitive access information should be separate data domains with different visibility and retention.
Offline / weak signal
Event packets, critical contacts, access rider and instrument assignment should remain usable when a rural venue has weak connectivity.
Current DOJ rule: state and local government web content and mobile apps generally must meet WCAG 2.1 Level AA on the compliance schedule set by the 2024 Title II rule. Entities of 50,000 or more people have an April 26, 2027 compliance date; smaller entities and special district governments generally have until April 26, 2028. DOJ fact sheet ↗
A preference toggle can make a good interface better. It cannot make inaccessible code compliant.