JuliaPluto/Pluto.jl

Add ARIA attributes to tab buttons

Open

#3274 opened on Jun 20, 2025

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Julia (5,295 stars) (329 forks)batch import
accessibilityfrontendgood first issue

Description

This is about the buttons to toggle the pages in the live docs / status panel - which I also discussed in #3273. I decided to make this one a separate issue because you can tackle them independently.

From what I can see, these controls are <button> elements without any further semantics encoded (through a role or ARIA attributes). That indicates that you can push them, but there is no encoding that these buttons have an active/inactive status, or that they control a different part of the page. You can see these things visually, but it's not clear for assistive technologies.

Solution: the way these interactions are programmed matches the disclosure pattern. Set the aria-expanded and aria-controls attributes based on the state of the widget and this is good to go!

Contributor guide

Tech stack
htmlcssjavascript
Domain
accessibilityfrontend
Issue type
accessibility
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic HTMLARIA attributes knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Examine the button elements in the live docs/status panel. Implement aria expanded and aria controls attributes following the disclosure pattern. See discussion in #3273 for additional context.