Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tooltips are neither dismissible nor hoverable (WCAG 1.4.13)

Open Beginner friendly
  • Is something wrong?
#15,411 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
accessibility, frontend

Research direction

Start in resources/js/bootstrap/statamic.js, where floating-vue is registered, and check its tooltip theme configuration and the library's supported options. Verify the global tooltip behavior against the sidebar's “Toggle Nav” tooltip on /cp/dashboard: Escape dismisses it, the pointer can move onto it without it disappearing, and it has role="tooltip".

Written by the indexing model from the issue text.

Description

accessibility
Bug description

Tooltips in the CP are shown on hover but cannot be dismissed with Escape and cannot be hovered, which fails two of the three conditions in WCAG 2.1 SC 1.4.13 Content on Hover or Focus (Level AA).

Measured against the sidebar's "Toggle Nav" button on /cp/dashboard:

1.4.13 condition Result
Dismissible — can be removed without moving pointer or focus FAIL — Escape does nothing
Hoverable — pointer can move onto the tooltip without it disappearing FAIL — it vanishes
Persistent — stays until dismissed, focus moves, or it stops being valid PASS — still visible after 4s 
{ "tooltipShown": true, "role": null, "text": "Toggle Nav",
  "cls": "v-popper__popper v-popper--theme-tooltip v-popper__popper--shown",
  "dismissibleByEscape": false, "hoverable": false, "persistentAfter4s": true }

The tooltip also carries no role="tooltip", so it isn't announced as one.

Tooltips come from floating-vue (v-tooltip), registered in https://github.com/statamic/cms/blob/v6.31.0/resources/js/bootstrap/statamic.js#L10. Both failing conditions are configurable there rather than requiring per-call-site changes.

This matters more than usual in Statamic's CP because tooltips are sometimes the only text alternative for an icon-only control — see the status indicator issue I'm filing alongside this, where v-tooltip is the sole carrier of "Published" / "Draft" / "Scheduled" / "Expired".

How to reproduce
  1. composer create-project statamic/statamic, log in
  2. Hover the sidebar collapse button in the global header until the tooltip shows
  3. Press Escape — the tooltip stays
  4. Hover the tooltip itself — it disappears
Suggested fix

floating-vue supports both:

  • register a global hideOnTargetClick/Escape handler, or set instantMove plus an onKeydown that hides on Escape
  • set the tooltip theme's disposeTimeout / pointer-events so the popper is hoverable rather than pointer-events-none

Adding role="tooltip" on the popper would also let assistive technology announce it correctly.

Environment

Environment
Laravel Version: 13.30.1
PHP Version: 8.4.23
Composer Version: 2.10.2
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 0
License Key: Not set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.31.0 PRO
Installation

Fresh statamic/statamic site via CLI

Additional details

Found during a WCAG 2.1 AA audit of a vanilla composer create-project statamic/statamic install with no addons and no custom code. Tested with axe-core 4.x on Chromium 153 at 1440x1000, plus manual keyboard traversal. Source references point at v6.31.0.

Dominant language
PHP
Stars
4.9k
Forks
647
Avg merge
1d 8h
Merged PRs (30d)
100

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from statamic/cms

All issues in statamic/cms

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.