Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(home): make the decorative capability strip truly unreachable, not just untabbable
nirholas82f0af95d5d6
diff --git a/pages/home.html b/pages/home.htmlindex acae30654..7ab7c8b8e 100644--- a/pages/home.html+++ b/pages/home.html@@ -363,12 +363,14 @@</section><!-- ── CAPABILITY STRIP ───────────────────────────────────────────── -->-<!-- tabindex="-1" is load-bearing: the strip clips a wider-than-viewport track- with overflow:hidden, and Chrome puts every such scroll container in the tab- order. That made an aria-hidden decorative marquee keyboard-focusable, so- keyboard users landed on a stop screen readers announce as nothing at all- (axe aria-hidden-focus). The negative tabindex opts the scroller out. -->-<div class="capability-strip" id="capability-strip" aria-hidden="true" tabindex="-1">+<!-- No tabindex here on purpose: the strip is decorative and aria-hidden, so it+ must be unreachable, and `tabindex="-1"` does not achieve that. It only+ removes the element from sequential navigation while leaving it+ programmatically focusable, which axe still reports as aria-hidden-focus.+ The strip stays out of the tab order because its CSS clips with+ `overflow: clip` rather than `hidden`, so it never becomes the scroll+ container Chrome would make focusable. See public/home.css. -->+<div class="capability-strip" id="capability-strip" aria-hidden="true"><div class="cap-fade cap-fade--l"></div><div class="cap-track"><div class="cap-inner">diff --git a/public/home.css b/public/home.cssindex d5401f7a5..03079107b 100644--- a/public/home.css+++ b/public/home.css@@ -344,7 +344,13 @@/* ── CAPABILITY STRIP ──────────────────────────────────── */.capability-strip {position: relative;- overflow: hidden;+ /* clip, not hidden: `overflow: hidden` makes this a scroll container, and+ Chrome puts every scroll container in the tab order. That handed+ keyboard users a stop inside an aria-hidden decorative marquee, which+ screen readers announce as nothing at all. `clip` crops identically+ without creating a scroller, so the strip is neither tabbable nor+ focusable and needs no tabindex to opt out. */+ overflow: clip;border-top: 1px solid var(--hairline);border-bottom: 1px solid var(--hairline);background: var(--surface-0);