Accessibility work

Accessibility between releases.

The support model treats accessibility as recurring production work: automated scans, manual keyboard checks, third-party embed review, editor guidance, and regression tickets.

Remediation light table

Move from issue to pattern.

Third-party embeds can create keyboard traps.

Audit the embed, wrap it with visible instructions and focus recovery, and keep a regression note tied to the WordPress block.

WCAG 2.2 AATarget and regression standard for support work.

Representative scansCurrent-site audit findings are logged in the proposal packet.

Editor guidanceAlt text, headings, captions, transcripts, and document checks become publishing habits.

Third-party platformsSlate, Mailchimp, Localist, and embeds get wrapper-level remediation and clear escalation paths.