![]() Moderator ![]()
|
Yesterday we discussed the state of KDE Accessibility. There were great and productive discussions for two hours straight, the first hour is summarized in this post, the second hour was more technical, educating developers about accessibility APIs and and tools for testing.
We really need more people help testing and discussing what is needed. And of course we need people interested in defining solutions and then implementing them. Topics are very broad and this post is just a start to get some thoughts out. We will need separate threads for all sub-topics later on. We want to use the forum to attract new people, then blog and e-mail about it. The forums are a great place to start though. Ideally we'll have a job-board which allows to post "things to do" that are of a limited scope to invite people to come along. Everything below is the list of things we discussed:
We have some junior jobs that would benefit everyone greatly:
Accessibility improvements for screen reader users:
If you think things are missing, please add them to this thread. Should you be interested in working on some of this, let's start a new thread to keep this one manageable. |
![]() Registered Member ![]()
|
Some comments to your checklist pages:
[1] During the Akademy workshop we noticed that applications often do not run in full size. The text is misleading and should be has been changed.
Last edited by Heiko Tietze on Wed Oct 08, 2014 8:11 am, edited 1 time in total.
|
![]() KDE Developer ![]()
|
The website was/is old and broken. I took a quick look and with some help from ingo in #kde-www got it working again with the new theme etc. I also fixed the menus a bit for the navigation so everything isn't under one "KDE Accessibility Project" menu anymore, since just above the menu it says KDE Accessibility anyway. Some more work on content could definitely be done though.
I also started an rsync of svn to my machine so I can test the svn -> git conversion rules I just put together and requested a git repo for the site once that's ready and such. Frederik, Anyone who was at the workshop, Could you give a bit more detail about the junior jobs? I.e. what's required to install in order to test those things, how to test, who to e-mail/ping on irc to get things fixed, etc. I have been running plasma-next for a month or so, but am not sure what to do to test accessibility features besides install orca, run it, and see what works, what doesn't etc. Is there something a bit more detailed than that somewhere? |
![]() KDE Developer ![]()
|
accessibility.kde.org content is coming from git kde:websites/accessibility-kde-org repo now. All content and history has moved and old svn content replaced with a README file pointing to the new location.
|
Registered users: bartoloni, Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]