SolidOS / SolidOS/solidos

Accessibility of other solid-panes elements

Open
#243 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
146
Forks
21
PR merge metrics
No merged PRs in 30d

Description

There are other panes and elements that need work, too:

IMPORTANT - some panes may only be visible once Power User is active.

Solid-panes:

TODO for each:

  • adding HTML5 and ARIA labels
  • add accessibility tests based on 'axe-core' (example here)
  • making sure it also work when resizing screen
  • making sure other accessibility features are inline with the WCAG standard (the tests will show). As example: text sizes, button sizes, keyboard focus and so on.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the listed solid-pane entry points, including src/socialPane.js, src/dashboard/basicPreferences.ts, and the directories for trustedApplications, dokieli, audio, video, slideshow, playlist, and trip. Use the profile-pane cv-card.accessibility.test.ts example and axe-core tests as a reference. Done means each pane has HTML5 and ARIA labels, accessibility coverage, responsive behavior, and WCAG-related issues addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.