CesiumGS/cesium

'Data Attribution' link is not accessible using accessible using keyboard in map screen in windows.

Closed

#13,670 opened on Aug 4, 2026

View on GitHubContributor guide
 (1 comment) (1 reaction) (0 assignees)JavaScript (3,324 forks)batch import
category - widgetsgood first issuetype - bug

Repository metrics

Stars
 (11,758 stars)
PR merge metrics
 (Avg merge 15d 12h) (23 merged PRs in 30d)

Description

What happened?

'Data Attribution' link is not accessible using accessible using keyboard in map screen in windows. 'Data Attribution' link should be accessible using keyboard tab key in map screen in windows.

https://github.com/user-attachments/assets/6b38438a-5592-4808-acef-aaa34db9e889

Reproduction steps

  1. Open the URL: Sandcastle | CesiumJS in edge/chrome browser.
  2. Map screen will open.
  3. Press tab key to navigate on the page.
  4. Verify whether 'Data Attribution' link is accessible using accessible using keyboard in map screen in windows or not.

Sandcastle example

https://sandcastle.cesium.com/standalone.html#c=bY1BawIxEIX/ypCTlpLg2exS8Cr0UPA0l5gd69DZiWSyK/bXF7VCCx7f4/ve4/FUaoMXSAYbMp5GONQyArp8S+jWqKi5qDWYmc5UoQOl8y/td7du8eA3RVtipYpuuUZ1ry5auwj1qABvfH+bqiy8D43Gk6RGFvZT/qLms9lViuGhxIFn4KF7sg5ZklmH7jCJfPA3oetjGHj+p0lJA+vn+0xV0uWKHFf99l5672M4rp5YrRTZp/pn8Qc

Environment

Browser: Edge (Version 150.0.4078.96), Chrome (Version 150.0.7871.182) CesiumJS Version: 1.143.0 Operating System: Windows 11 version 25H2 (OS Build 26200.8893)

AI acknowledgment

  • I used AI to generate this issue report.
  • (If the above is checked) I have reviewed the AI-generated content before submitting.

Contributor guide

Research direction
Inspect the CesiumJS source code to locate where the Data Attribution link is rendered. Identify why it is not reachable via keyboard, focusing on focus management and tabindex attributes. Use the reproduction steps to trace the issue in the rendered DOM.
Tech stack
javascript
Domain
frontendaccessibility
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75