From OpenStreetMap Wiki
Jump to navigation Jump to search

Hi, I see a difference between "targeting at blind users" and "working for blind users". The language of the screenreader is not an attribute of the software. We should have a column for the available languages for the softwares though. --Lulu-Ann 14:51, 16 November 2010 (UTC)

So you are suggesting to replace the "Targeted at blind users" with a "working for blind users" column? Can be done. What about the wheelchair users column? --Tordanik 17:35, 16 November 2010 (UTC)
No, I want to add the column. There is software designed for blind users that works perfectly, and there is software that is not designed for blind users but can be used if you learn a few hotkeys or configure your screenreader with alternative texts for few graphics (e.g. Skobbler). That's a difference. --Lulu-Ann 10:23, 18 November 2010 (UTC)
That's possible, but we need to retrieve that information from somewhere. Currently, there is a single accessibility=blind/wheelchair/... parameter for Template:Software2. We would probably need two different parameters to feed the two columns. I can imagine separating the "software is useable by audience x" and "software is specifically targeted at / designed for the needs of audience x". Do you have suggestions for the parameters? If yes, I recommend that you add them to Template talk:Software2. --Tordanik 14:08, 2 December 2010 (UTC)
I see different columns for blind and wheelchair users:

Wheelchair: Designed for Wheelchair users=yes/no Blind: Accessible for blind users without screenreader: completeley / good / poor / no Accessible for blind users with screenreader: completely / good / poor / no I don't like the soft skale, though... Sounds to me like a smoothness devirate ;-) --Lulu-Ann 13:37, 3 December 2010 (UTC)

Regarding screenreader languages: Will a screenreader always work equally well with all languages? Or are there platforms where software can/needs to provide hints about pronunciation etc.? Just using the existing (non accessibility-specific) languages column would easy. --Tordanik 17:35, 16 November 2010 (UTC)
No, you need to install voices, and a voice only works fine for one language. If there is no voice available for one language, the screenreader can hardly be used for it, because the pronounciation is totally messy and the exeption dictionary is empty/wrong. So there is usually a welldefined list of working languages. How about adding a link to the screenreader's webpage? --Lulu-Ann 10:23, 18 November 2010 (UTC)

New column: Platform


we need a column platform for the differen devices / operating systems.

--Lulu-Ann 08:43, 24 November 2010 (UTC)

Hi, I'm quite busy currently, so please be patient if I need some time reply to a posting. Adding a column that has already been defined is rather straightforward, though: [1] --Tordanik 21:32, 25 November 2010 (UTC)