The "Ask AI" control in the docs header (docs.sentry.io) is rendered as a styled div instead of a native <button>, which excludes it from the tab order and makes it unreachable via keyboard navigation or assistive technologies.
Replacing it with a native <button> (or adding role="button" + tabindex="0" + keyboard event handlers as a fallback) restores standard focus behavior.
- Reproduction: tab through the docs header — the Ask AI control is skipped entirely
- Quick verify: open DevTools, temporarily swap the
div to a button → element becomes keyboard-focusable as expected
- Fix: use a native
<button> element; avoid ARIA role workarounds when a semantic element fits
Action taken on behalf of Lamberto Asghedom.
The "Ask AI" control in the docs header (
docs.sentry.io) is rendered as a styleddivinstead of a native<button>, which excludes it from the tab order and makes it unreachable via keyboard navigation or assistive technologies.Replacing it with a native
<button>(or addingrole="button"+tabindex="0"+ keyboard event handlers as a fallback) restores standard focus behavior.divto abutton→ element becomes keyboard-focusable as expected<button>element; avoid ARIA role workarounds when a semantic element fitsAction taken on behalf of Lamberto Asghedom.