Basic accessibility

[Chudesnov]

Preliminary Checks

• [x] I have read and understood the important section above.
• [x] I have searched existing issues and avoided creating duplicates.
• [x] I am not filing an enhancement request.
• [x] I have checked that this issue cannot be reproduced on Mozilla Firefox.
• [x] I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS.

What happened?

Upon first launching Zen Browser, the initial welcome screen displays a single button. While this button is tabbable (likely due to being implemented with built-in XUL primitives) and has a visual indicator on it, it has no visible focus styles, no programmatically accessible name and cannot be activated via keyboard (neither Space nor Enter work as expected).

Reviewing the CSS files in the Zen repository, I found no explicit focus outlines defined for any elements. In several cases, focus styles are actively removed using outline: none !important without providing accessible alternatives.

After proceeding past the welcome screen, launching the full browser interface and inspecting the settings page, I observed the following:

• Very few UI elements are accessible via keyboard.
• Those that are accessible rarely show visible focus indicators.
  (The few exceptions appear to be elements copied directly from Firefox.)
• Accessibility metadata is inconsistent or missing:
  • Using Accessibility Insights, I noticed that while some elements like buttons occasionally have accessible names, many others do not.

Please prioritize implementing proper accessibility support, including:

• Keyboard operability and visible focus styles for all interactive elements.
• Semantic labeling and appropriate attributes.

As I stated above, I am not filing an "enhancement request". These are not optional features — they are fundamental requirements for software being built in 2025.

Expected behavior

Basic support for keyboard navigation and assistive technology like screen readers or voice control.

Actual behavior

Inaccessible browser UI

Steps to reproduce

• Welcome screen: the only button has no visible focus styles, no label, can't be activated from keyboard
• Browser chrome: the only element that can be tabbed into from keyboard are the URL bar and the tab list (likely copied from Firefox), but no focus styles. "New tab", "Zen", "Back/Forward/Reload" - completely inaccessible.
• Settings page: no visible focus styles, several widgets without any keyboard accessibility or widget role (e.g. Browser Layout control in "Look and Feel".

Screenshots and videos

No response

Version

1.12.9b

What platform are you seeing the problem on?

Windows - x64

What component is this issue related to?

Other

Relevant log output if applicable

[dosubot[bot]]

Hi, @Chudesnov. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• Accessibility issues reported in Zen Browser's welcome screen and interface.
• Problems include lack of keyboard operability, visible focus styles, and consistent accessibility metadata.
• These issues affect users relying on assistive technologies.
• No comments or updates have been made on this issue yet.

Next Steps:

• Please confirm if the issue is still relevant to the latest version of the desktop repository by commenting here.
• If no updates are provided, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

[Chudesnov]

Since there was no activity on the issue I’m assuming the raised issues aren’t solved yet, so it’s relevant to the latest version.

[Chudesnov]

Looking at the latest beta, seems like the issue has been getting some fixes:

• There are now visible focus styles on most tabbable elements like buttons (not inputs though).

The rest is still relevant to the latest version:

• During onboarding, none of the buttons can be pressed from keyboard.
• Multiple UI chrome elements (menu buttons and toolbars, new tab button) and certain custom widgets in browser settings are completely inaccessible.

[dosubot[bot]]

Hi, @Chudesnov. I'm Dosu, and I'm helping the desktop team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported that Zen Browser's UI lacks key accessibility features like keyboard operability, visible focus indicators, and semantic labeling.
• Improvements were noted in the beta with visible focus styles on most buttons.
• However, keyboard activation during onboarding and accessibility of several UI elements remain insufficient.
• The issue highlights ongoing fundamental accessibility gaps that need prioritization.
• No resolution has been reached yet, and the issue has seen limited recent activity.

Next Steps:

• Please confirm if this issue is still relevant with the latest version of Zen Browser by commenting here.
• If I don’t hear back within 7 days, I will automatically close this issue.

Thank you for your understanding and contribution!

[Chudesnov]

Hi @dosubot. Nothing changed.

[dosubot[bot]]

Hi, @Chudesnov. I'm Dosu, and I'm helping the desktop team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported that Zen Browser's UI lacks key accessibility features like keyboard operability, visible focus indicators, and semantic labeling.
• Some improvements appeared in the latest beta, such as visible focus styles on most buttons.
• Despite these, many elements remain inaccessible via keyboard and lack consistent accessibility metadata.
• The issue has been marked stale twice with requests for updates, and you confirmed the problem persists with no changes observed.
• The fundamental accessibility gaps remain unaddressed.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of Zen Browser by commenting here to keep the discussion open.
• If I don’t hear back within 10 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

[Chudesnov]

None of this has been fixed, and it should not be closed as not planned or marked as stale.

[dosubot[bot]]

@mauro-balades The user Chudesnov has pointed out that the issue remains unresolved and should not have been closed as not planned, emphasizing the importance of accessibility for the Zen browser. Could you please review and assist with this?

[dosubot[bot]]

Hi @Chudesnov! I'm Dosu and I’m helping the desktop team.

I can't directly reopen issues, but I can confirm that the accessibility problems you described remain unresolved—there have been no recent fixes or merged pull requests addressing keyboard operability, visible focus styles, or semantic labeling in the Zen Browser UI. These are fundamental accessibility requirements, and your concerns are valid and well-documented. I encourage maintainers or those with repository permissions to review this issue and consider reopening it, as accessibility is essential for all users.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[dosubot[bot]]

@mauro-balades The user has requested to reopen this issue as it is still relevant despite being marked stale and closed. Could you please assist with this?