Weekly signal

Agentic AI and traditional accessibility work moved from parallel tracks to the same checklist this week: vendor guidance and platform launches are making assistive‑tech signals (the accessibility tree, semantic HTML, stable layouts) first‑class inputs for browser and device agents. This has immediate product and legal effects — Apple shipped a major agentic‑AI platform at WWDC while warning EU users they’ll get a delayed Siri AI because of DMA rules, and security tooling for agent "skills" arrived to protect accessible workflows from malicious plug‑ins.

What changed

1. Google formally codified how browser agents should read sites (the web.dev “Build agent‑friendly websites” guidance) and the industry quickly framed the checklist as the accessibility audit for agents. The guidance emphasizes the accessibility tree, semantic HTML, stable layouts, and clear labels — the same signals assistive tech needs.

2. Apple’s WWDC announced Siri AI / Apple Intelligence and system features that explicitly target accessibility: improved VoiceOver/Magnifier exploration, natural‑language Voice Control, on‑device generated subtitles, and Vision Pro wheelchair control — but Apple also posted an EU update saying Siri AI for iPhone/iPad will be delayed in the EU due to Digital Markets Act constraints. That split matters for accessibility rollouts by geography.

3. OpenAI published a high‑level plan (June 8) focused on broad access and on June 11 announced an acquisition (Ona) that expands persistent, customer‑controlled execution for long‑running agents — a technical foundation for deploying persistent assistive agents in enterprise and product settings.

4. NVIDIA released an open scanner (SkillSpector) for agent skills to detect vulnerabilities and malicious patterns in installable skills — a practical guardrail for skills that could otherwise misuse accessibility APIs or control assistive workflows.

What to do with it

• Treat agent‑readability as accessibility: run one combined audit (WCAG + web.dev agent checklist) on your top pages and interaction paths. Start with buttons, labels, focus order, and the accessibility tree.
• If you ship agent skills or plugins, add SkillSpector or similar scanning into CI before publishing or installing third‑party skills. Vet any skill that touches assistive APIs or system control.
• For product teams shipping assistive agents or agent integrations, map regional regulatory constraints (e.g., Apple’s EU DMA delay) to release plans and accessibility commitments; EU users may not get the same agent features on iPhone/iPad at launch.
• For accessibility teams: prioritize integrations with persistent agent runtimes (Codex/Ona, MCP endpoints) so remediation agents and continuous QA can run safely in scoped environments.