You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2018. It is now read-only.
Frankly, you might be missing out on significant markets consisting of both content publishers and content viewers when you leave out blind and visually impaired users (among other users with different disabilities); and
That's because a lot of educational / academic, entertainment / recreational, job / productivity and other work / school-related content are specifically produced for users like us. Plus:
Many of us globally also spend a lot of time and resources viewing online / offline content on a daily basis ...
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I cannot use the Windows GUI wallet without sighted assistance.
I'm a completely blind JAWS For Windows, NVDA (Non-Visual Desktop Access) and VoiceOver (iOS / Mac OSX) user and AI developer; and
I have a couple of solutions to propose:
Provide a Windows command line wallet, similar to what Electroneum has (among other Cryptonight coins based on Monero); or
Integrate accessibility into your QT-based Windows GUI wallet, as discussed in detail here: http://doc.qt.io/qt-5/accessible.html
Frankly, you might be missing out on significant markets consisting of both content publishers and content viewers when you leave out blind and visually impaired users (among other users with different disabilities); and
That's because a lot of educational / academic, entertainment / recreational, job / productivity and other work / school-related content are specifically produced for users like us. Plus:
Many of us globally also spend a lot of time and resources viewing online / offline content on a daily basis ...
The text was updated successfully, but these errors were encountered: