Re: Bug#855446: debtags: Adding more accessibility tags
Hello, Enrico Rossi, on lun. 20 févr. 2017 11:08:57 +0100, wrote: > and accessibility::screen-reader which is already present? > > there is accessibility::speech These are completely different: accessibility::screen-reader and accessibility::speech are for tools which *provide* accessibility, while accessible-with would be meant to mark packages which can be *made* accessible, precisely with those tools. Far from all packages can be made accessible. But of a lot of packages can. For a blind person, trying packages at random to see which ones can be used is a pain, so it makes sense to have a mark to just directly get them. > One way or another, do you already have a list of possible tags to be > created? This is to be discussed with debian-accessibility, thus the Cc of the original but report and this mail. Samuel
Re: Bug#855446: debtags: Adding more accessibility tags
Hi Samuel, Have you considered to use just the facet without the "accessible-with"? > users would like to have accessibility::accessible-with::foobar tags for > applications. like accessibility::foobar instead? > More precisely, these are the kinds of tags that can be thought of: > > to describe whether the package is technically accessible: > - accessibility::accessible-with::at-spi > which can for example be basically applied to all gtk, qt, and java > graphical applications. That wouldn't necessarily mean usability, just > that technically the content of the application is available to screen > readers. and accessibility::screen-reader which is already present? > to describe whether the package is actually accessible via some medium: > - accessibility::accessible-with::braille > - accessibility::accessible-with::speech there is accessibility::speech I mean I'm not against the accessible-with, only I see some possible duplication or unnecessary complication here. One way or another, do you already have a list of possible tags to be created? Thanks Bye E. -- GPG Key: 4096R/F2133176 2010-10-19 Enrico Rossi
Bug#854295: brltty-espeak: crashes while emitting speech
Samuel Thibault schrieb am 13.02.2017, 10:52 +0100: >Sebastian Humenda, on Mon 13 Feb 2017 10:47:33 +0100, wrote: >> I haven't encountered any issues yet. It is rather hard to say whether it is >> fixed, because the bug is hard to reproduce. However, there have been no >> further crashes so far. > >Ok, we can wait more, no pb :) No crashes, I think it's safe. Thanks Sebastian signature.asc Description: PGP signature
Re: debtags: Adding more accessibility tags
Samuel Thibault, on sam. 18 févr. 2017 11:50:11 +0100, wrote: > to describe whether the package is technically accessible: > - accessibility::accessible-with::at-spi I'm thinking that this should perhaps rather be accessibility::accessible-via::at-spi so as to mark that this is really different from > - accessibility::accessible-with::orca-braille > - accessibility::accessible-with::orca-speech > - accessibility::accessible-with::brltty-braille > - accessibility::accessible-with::brltty-speech > - accessibility::accessible-with::speakup-speech > - accessibility::accessible-with::yasr-speech since in the first case it's just a technical thing which does not assert any actual usability (which could be set by scripts when it for instance uses a gtk ui), while the second really means somebody tested it. Samuel
Speech Dispatcher cutting off the end of phrases while using Flite
Hello, I notice that while using Orca with Speech Dispatcher and Flite, the end of most phrases are cut off. It usually cuts off the second half of the last word spoken. I was just wondering if anyone has noticed this before and knows of a fix if one exists. Thanks.
