Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Accessibility status/instructions in Wiki #32

Open
bitbinge opened this issue Mar 22, 2024 · 1 comment
Open

[FEATURE REQUEST] Accessibility status/instructions in Wiki #32

bitbinge opened this issue Mar 22, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@bitbinge
Copy link

bitbinge commented Mar 22, 2024

Is your feature request related to a problem? Please describe.
Yes. Fedora (& by proxy Ultramarine) does not have a good guide for accessibility (including workarounds for Wayland).

Describe the solution you'd like
If inline with the goals of Ultramarine, I would like to contribute to this documentation, and ideally, for common concerns, work with Ultramarine developers to incorporate sane defaults for accessibility. With little effort we can highlight what works and what does not, and why.

Describe alternatives you've considered
N/A.

Additional context
Good examples of accessibility guides are the Accessibility section in the Ubuntu Desktop Guide and the Accessibility page in the Debian wiki.

@bitbinge bitbinge added the enhancement New feature or request label Mar 22, 2024
@lleyton
Copy link
Contributor

lleyton commented Mar 22, 2024

This is definitely within our goals! Would love to discuss more in the Discord, Matrix, or this issue. :)

To start off, which defaults do you think would benefit accessibility?

@madonuko madonuko transferred this issue from Ultramarine-Linux/triage Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants