Skip to content

fix(website): expose loading progress and errors to screen readers - #148

Open
arpanjot-coding wants to merge 1 commit into
NanoForge-dev:mainfrom
arpanjot-coding:fix/loader-accessibility
Open

arpanjot-coding wants to merge 1 commit into
NanoForge-dev:mainfrom
arpanjot-coding:fix/loader-accessibility

Conversation

@arpanjot-coding

Copy link
Copy Markdown

What does this PR do?

Give the loading page a descriptive title, expose loading steps as status updates, and keep the accessible progress value in sync with the progress bar from the first download. Use a persistent alert region so a download error is available to assistive technology even when the visible error panel starts hidden.

Closes #142.

How do you test this PR?

  • Ran website lint, the workspace build, and workspace unit tests in Node 26 Docker.
  • Verified the built page in Chromium with two fixture downloads. Checked the accessible title, status and progress, then confirmed a failed download appeared in the alert and visible error panel.

@github-actions github-actions Bot added the app:website Related to website app label Nov 11, 2026
@arpanjot-coding

Copy link
Copy Markdown
Author

The Tests workflow for current head 8bfee7cee91f is waiting for maintainer approval (action_required).

Please approve this external-contributor workflow run so the repository checks can verify the current changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

app:website Related to website app

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(loader-website): the loading page is titled Title and gives screen readers no status

1 participant