René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature]: Promote `a11y` to Stable — settle the 1.14 surface and document audit scope","articleBody":"**Pre-flight checklist**\n- [x] I searched existing issues and did not find a duplicate request.\n- [x] I explained the problem or use case, not just the desired API.\n\n**Problem or use case**\n`a11y` is **Beta** and a genuine differentiator (first-party focus management, live regions, and audits where competitors rely on third-party libraries), but its surface just expanded in 1.14.0 (`createLiveRegion`, `focusVisible`, `inert`, `scrollLock`, `autoFocus`, preference signals) and its audits are runtime-only with no documented scope. Teams adopting it for compliance need to know exactly what the audits check and that the API won't shift.\n\n**Proposed solution**\nFreeze the `a11y` API for one cycle and publish a precise audit scope: which WCAG criteria the runtime audits cover, what they cannot detect, and how results are surfaced. Add test coverage for focus trapping, live-region announcements, `inert`/`scrollLock` behavior, and the preference signals. Exit criteria: frozen surface, documented audit coverage with known limitations, tested focus/live-region behavior.\n\n**Possible API or UX shape**\n```ts\nimport { audit, createLiveRegion, focusTrap } from \"@bquery/bquery/a11y\";\n\nconst report = audit(root); // documented: which WCAG checks are/aren't covered\n// report.issues -\u003e [{ rule, element, wcag, severity }]\n```\n\n**Alternatives considered**\nPromoting without documenting audit scope — risks teams over-trusting runtime audits for compliance they don't actually cover. Continuing to expand the surface before freezing — fine for Beta, but must pause for Stable.\n\n**Relevant area**\n`a11y`\n\n**Additional context**\nWire audit results into the devtools panel (#146) so a11y issues are inspectable alongside component state. First-party a11y is a real selling point versus React/Vue/Svelte; documenting its limits is what makes it trustworthy.\n","author":{"url":"https://github.com/JosunLP","@type":"Person","name":"JosunLP"},"datePublished":"2026-06-26T21:25:38.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/142/bQuery/issues/142"}