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

Supporting accessibility technologies #1285

Open
andydotxyz opened this issue Sep 4, 2020 · 4 comments
Open

Supporting accessibility technologies #1285

andydotxyz opened this issue Sep 4, 2020 · 4 comments
Labels
Accessibility Issues relating to accessibility, such as colorblind users, hard-of-sight users, etc. future Features that might take a while to be sheduled help wanted Extra attention is needed

Comments

@andydotxyz
Copy link
Member

This needs to be fleshed out - how do we do it, what's the minimum etc?

@Zireael07
Copy link

The minimum imho is supporting a basic preexisting screen reader such as ORCA for the visually impaired, and having a visual bell (e.g. flashing the top bar or the entire screen) for the hearing impaired.

@andydotxyz
Copy link
Member Author

I agree with the screen reader requirement.
Not sure about visual bell - as we don't have any sounds built in...

@Zireael07
Copy link

Oh, if you don't have any sounds/terminal beep, then it's fine not to have visual bell as that means everyone is on exactly the same footing :P

@Bluebugs
Copy link
Contributor

One of the project to keep an eye on is https://github.com/AccessKit/accesskit which even if it does introduce a new non go dependencies would make it more doable than doing it from 0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility Issues relating to accessibility, such as colorblind users, hard-of-sight users, etc. future Features that might take a while to be sheduled help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants