Azure / Azure/aks-desktop

[BUG] [a11y] Create Project stepper buttons not fully visible at 200% text resize

Open
#469 0 comments 0 reactions 0 assignees View on GitHub
a11y bug triage
Dominant language
TypeScript
Stars
102
Forks
25
Avg merge
1d 4h
Merged PRs (30d)
22

Description

## Description

At 200% text resize, the Create Project page step buttons (e.g., Access, Review) are not fully visible, making it difficult for low-vision users to see or interact with step navigation controls.

## Environment

- AKS Desktop Version: 0.1.0-alpha
- Headlamp Version: 0.38.0
- OS: Windows 11 Enterprise version 24H2 (Build 26567.1000)
- Display Resolution: 1280x768
- Text Size: 200% (Settings > Accessibility > Text Size)

## Repro Steps

1. Set display resolution to 1280x768
2. Set text size to 200% (Settings > Accessibility > Text Size)
3. Launch AKS Desktop and log in
4. Navigate to Home > Projects tab
5. Click "Create Project" > "AKS Managed Project"
6. Observe the stepper buttons (Access, Review) on the New Project page

## Actual Behavior

At 200% resize, Create Project page step buttons (Access, Review) are not fully visible.

## Expected Behavior

At 200% resize, all step buttons should remain fully visible, readable, and reachable without loss of content or functionality.

## User Impact

Low-vision users who rely on text resizing cannot clearly see or interact with step navigation controls, making it difficult to understand progress or navigate between steps in the Create Project flow.

## MAS Reference

MAS 1.4.4 – Resize Text

## Related Issues

- #417 — search bar color changes at high zoom (different component)
- #404 — resource tab components overlap at high zoom (different page)

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in AKS Desktop on Windows 11 at 1280x768 with 200% text size, following the listed Home > Projects > Create Project > AKS Managed Project steps. Inspect the New Project stepper containing Access and Review, and verify that all buttons remain fully visible, readable, and reachable without loss of functionality.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.