💬 Vivaldi's keyboard tab navigation is broken (Claude)

Exported on: 3/31/2026, 02:01:52 PM

This is research done by Claude to solve a problem I had with Vivaldi keyboard navigation using the Haiku 4.6 model

Vivaldi’s keyboard tab navigation is broken by design on macOS

Vivaldi browser’s most consequential accessibility flaw is a default setting—not a bug. Out of the box, Vivaldi restricts Tab key navigation to form elements only, silently skipping links, buttons, and other interactive elements that every other major browser includes. On macOS, this problem compounds with the operating system’s own restrictive keyboard defaults, creating a particularly hostile experience for keyboard-only users. The issue has been tracked internally as VB-55774 since at least 2020, with community volunteers repeatedly escalating it, yet the default remains unchanged through Vivaldi 7.9 (March 2026). Recent versions show genuine progress—accessibility onboarding, caret browsing, and numerous focus-related fixes—but the fundamental design choice persists.

A deliberate default, not a traditional bug

Vivaldi’s Tab navigation problem stems from its Settings → Webpages → Webpage Focus setting, which defaults to “Focus Forms Only.” This means pressing Tab skips <a> links, <button> elements, and other non-form focusable controls. Every other major Chromium-based browser—Chrome, Edge, Brave—includes links in the tab order by default. Firefox changed its macOS behavior in version 127 (June 2024) to match Chrome. Vivaldi alone maintains this restriction.

The design choice traces back to Vivaldi’s roots in Opera and its commitment to Spatial Navigation (Shift + Arrow Keys), which moves focus directionally rather than sequentially. Vivaldi developers have framed this as offering a “better and more useful model” versus “the lowest common denominator of other browsers.” In a 2025 forum discussion, a Vivaldi developer acknowledged the tension directly: “In terms of keyboard accessibility, I’m struggling. Currently we have various concepts keyboard users should know about that are different from other browsers.”

Making matters worse, Vivaldi has two separate, confusingly named settings that appear to control the same behavior. The “Full Keyboard Access” option under Settings → Keyboard governs UI chrome focus, while the “Webpage Focus” setting under Settings → Webpages controls in-page Tab behavior. Users routinely change one setting expecting it to fix the other—multiple forum threads document this exact confusion.

The macOS double penalty

macOS imposes its own keyboard navigation limitation. By default, the operating system restricts Tab to text boxes and popup menus only. Users must enable System Settings → Keyboard → “Keyboard navigation” (or press Control+F7) to unlock full control focus. Chrome and other Chromium browsers override this OS-level restriction and include links in the tab order regardless. Vivaldi, despite using Chromium’s rendering engine, layers its own additional restriction on top.

For a macOS Vivaldi user who hasn’t changed any defaults, the experience is doubly constrained: the OS limits system-level keyboard focus, and Vivaldi further restricts webpage Tab navigation. The fix requires changing settings in both places—a requirement unique to Vivaldi among Chromium browsers on macOS. Additional macOS-specific bugs include an Option+Tab shortcut conflict (where the Option modifier is ignored), focus landing on Speed Dial search instead of the address bar when opening new windows, and early VoiceOver reports where the entire browser window was announced as simply “Vivaldi” with no interactive elements exposed.

What the community and accessibility professionals say

Community sentiment is unambiguous. The primary forum thread—“Using tab-key to navigate websites is impossible”—contains sharp pushback against the moderator response that this is “not a bug.” A senior web developer wrote that he “wasted hours on a seemingly broken website” before discovering the setting in 2023. A UK developer cited legal accessibility requirements under the Equality Act. An accessibility professional who works with blind users called Vivaldi “the least accessible among Chromium-based browsers.”

The internal volunteer bug tester known as DoctorG/GwenDragon has been a persistent advocate, stating: “Sadly Vivaldi UI is not easy to use with keyboard. Using Tab key to jump through UI is not good in means of Accessibility Standards.” She confirmed bug VB-55774—requesting the default be changed to “Focus All Controls and Links”—and noted “I try to ping devs. But no hope yet.” A related feature request on the forum was archived after receiving fewer than five votes in four years.

Notable community discussions include threads on DEV Community where developer Ingo Steinke documented wasting hours debugging what he thought was his own code, only to discover Vivaldi’s non-standard default. No significant Reddit coverage was found—the conversation lives overwhelmingly on Vivaldi’s own forum. Screen reader users report that Vivaldi’s React-based UI architecture (the entire browser chrome is rendered as HTML/CSS) means assistive technology cannot reliably distinguish browser controls from web page content, a fundamental architectural challenge that Chrome and Edge avoid by using native platform UI elements.

Recent improvements signal a shift

Despite the persistent default issue, Vivaldi has made measurable accessibility progress in versions 6.0 through 7.9:

• March 2026 (Snapshot 3969.3): A new onboarding step explicitly asks whether the user needs assistive technology or keyboard-only access, letting them set “keyboard focus goes to all controls and links” during initial setup (VB-115238). This effectively acknowledges the default is wrong for accessibility users, though it doesn’t change the default itself.
• December 2025 (Snapshot 3882.3): Caret browsing support was finally implemented (VB-7520, one of the oldest open bugs), enabling cursor-based text navigation within web pages.
• Vivaldi 7.9 (March 2026): Fixed redundant tab stops in navigation (VB-125801), keyboard tab traversal failures in the tab bar (VB-125606), and inability to focus Start page navigation buttons (VB-104363).
• Vivaldi 7.8 (early 2026): Added caret browsing as a dedicated setting and fixed tab cycling in full-screen mode (VB-122344).

How to fix it now and report issues effectively

The immediate workaround requires two settings changes. First, navigate to Settings → Webpages → Webpage Focus and select “Focus All Controls and Links.” You must close and reopen any existing tabs—reloading alone is insufficient. Second, go to Settings → Keyboard → Full Keyboard Access and select “Focus All Controls.” On macOS, also enable System Settings → Keyboard → “Keyboard navigation” at the OS level. Additionally, Vivaldi’s Spatial Navigation (Shift + Arrow Keys) and Quick Commands (F2 or ⌘E) provide alternative keyboard-driven navigation. The F6/Shift+F6 shortcut cycles focus between the webpage, bookmarks bar, tab bar, and address bar.

For reporting bugs, Vivaldi uses a private Jira-based tracker. Submit reports through vivaldi.com/bugreport/ or via Help → “Report a Problem” within the browser. A confirmation email provides a VB-XXXXX tracking number. Since the tracker is not publicly searchable, check bug status by posting in the forum thread at forum.vivaldi.net/topic/27450/. The most effective reporting approach combines forum discussion first (to confirm the issue and gather community support) with a formal bug report that includes the specific WCAG success criterion being violated, exact reproduction steps, cross-browser comparison evidence, and system details. Volunteer moderators like DoctorG can escalate confirmed issues internally.

WCAG standards Vivaldi’s default violates

Vivaldi’s “Focus Forms Only” default directly conflicts with several Web Content Accessibility Guidelines criteria. WCAG 2.1.1 (Keyboard, Level A)—the most fundamental accessibility requirement—mandates that “all functionality of the content is operable through a keyboard interface.” When Vivaldi’s default prevents Tab from reaching links, users cannot activate those links via keyboard alone. WCAG 2.4.3 (Focus Order, Level A) requires a meaningful, logical focus sequence; skipping interactive elements disrupts this. WCAG 2.4.7 (Focus Visible, Level AA) requires visible focus indicators, which are moot when focus never reaches certain elements. The W3C HTML specification itself states that <a> elements with href attributes should be “sequentially focusable”—Vivaldi’s default overrides this expectation. European standard EN 301 549 and U.S. Section 508 both reference WCAG Level AA compliance for software including browsers.

Conclusion

Vivaldi’s keyboard accessibility problem is paradoxical: the browser offers more keyboard customization than any competitor, yet its default configuration is the least accessible among Chromium browsers. The core issue—VB-55774, changing the default Tab focus behavior—has remained unresolved for over five years despite clear community consensus, developer acknowledgment, and standards violations. The March 2026 accessibility onboarding step represents a pragmatic compromise, surfacing the setting for users who need it without changing the default for everyone. For users encountering Tab navigation skipping on macOS today, the fix is straightforward but undiscoverable without community guidance. The trajectory is positive—caret browsing, onboarding improvements, and steady bug fixes demonstrate investment—but Vivaldi’s architectural choice to build its UI as a web application creates structural accessibility challenges that incremental fixes alone cannot fully resolve.