[Fernando]
[...]
> Our focus is usually on keeping things very low-cost, in order to get great
> technology into the hands of the blind in developing countries. Since
> Braille displays are so expensive, we have not done |Braille in the past.
>
> But we could change this if we could get contribu
No problem. Since our work will be based on ARCH, there is a good chance
that what has been done for other distros will also work on ours.
Fernando
On 05/01/2017 04:09 AM, Linux for blind general discussion wrote:
[Fernando]
[...]
Our focus is usually on keeping things very low-cost, in
Sounds great! Thanks. Please join our list in oder to receive download
links when they become available.
Thanks,
Fernando
On 04/30/2017 03:22 PM, Linux for blind general discussion wrote:
I have a Braille display, so I could test.
___
Blinux-l
I'm already on the list. :) I await those links! :)
--
Sent from Discordia using Gnus for Emacs.
Email: r.d.t.pra...@gmail.com
Long days and pleasant nights!
Linux for blind general discussion writes:
> Sounds great! Thanks. Please join our list in oder to receive download
> links when they bec
Hello,
This is Samuel.
Linux for blind general discussion, on dim. 23 avril 2017 22:38:30 -0400, wrote:
> further the experience of blindness is not required to program accessible
> installers etc.
I believe it is, and that it's the main reason for lacking accessibility
features in installers et
ping
On 4/30/17, Amanda Lacy wrote:
> I didn't have good luck with Vinux so decided to go with something
> more mainstream. I have a bootable DVD and I managed to boot from it.
> I heard the drum sound which indicates Ubuntu has started. BRLTTY also
> started and gave me its useless 'screen not i
Hello, this is Samuel,
Christopher, on ven. 21 avril 2017 20:05:04 -0500, wrote:
> I also think that custom distributions is just part of the Linux ecosystem.
> How many custom distributions are there out there to satisfy every niche?
Sure.
> I don't think this should be any different for the bl
Hello, this is Samuel,
Kyle, on dim. 23 avril 2017 17:18:17 -0400, wrote:
> Debian even unstable takes parts of 2 or 3 different versions and
> tries to fit them together.
Well, that is not supposed to happen. I checked the MATE uploads, in the
past year uploads have been made coherently in unsta
Hello, this is Samuel,
Kyle, on dim. 23 avril 2017 18:45:32 -0400, wrote:
> backports is still not kept up-to-date with the latest improvements,
> and is still a larger gap between the running version and the upstream
> developer, where bug reports are most effective.
That's not necessarily so.
Hello, this is Samuel,
Kyle, on lun. 24 avril 2017 07:35:02 -0400, wrote:
> The main problem is that [Arch] already have a brltty package, but
> the brltty-minimal package is needed in order to make it work without
> pulling in lots of unneeded dependencies. This will always need to be
> in a sepa
Hello, this is Samuel,
Chris, on lun. 24 avril 2017 07:48:29 -0700, wrote:
> Frankly, my preference is not to have to type random incantations at a
> boot prompt. I call this "type and pray". Power up the box, try to
> guess when it boots,
You don't need to guess thanks to the boot menu beep.
Hello, this is Samuel,
Tony, on mer. 26 avril 2017 03:26:56 -0700, wrote:
> As I understand it, it isn't the fault of Speakup that it took so long to
> get to staging and is still there. The kernel developers were absolutely
> opposed to including it and wouldn't help at all.
That's not exactly r
Hello, this is Samuel,
Eric Oyen, on mar. 18 avril 2017 08:23:34 -0700, wrote:
> here is one thing that might be distro independent: create an
> accessibility package set.
As mentioned by others in the thread, doing it as a distribution of
binaries will lead to a lot of problems. Having it as a
Hello, this is Samuel again, last time for today, sorry I'm answering
all of this at once, I was in vacation last week while you were all
discussing furiously :)
Eric Oyen, on mar. 18 avril 2017 08:23:34 -0700, wrote:
> This would include the [...] config files needed to make any distro
> accessi
Samuel writes:
> Chris, on lun. 24 avril 2017 07:48:29 -0700, answered:
>> Yeah, brltty-minimal cuts out a lot of dependencies you don't want or
>> need on a console-only CD.
>
> Ok, but couldn't Arch include a brltty-minimal package? For the people
> who want a minimally-installed system, that m
Hello, it's Samuel,
Chris, on lun. 01 mai 2017 10:58:33 -0700, wrote:
> As for point 1, you're always going to have to do some research as a
> blind person if you want to install any Linux distro.
Well, not necessarily, if it's done right, i.e. the documentation for
accessibility is in the expect
Did people actually complain about the beep? If so, I'm starting to
think the sighted end-users aren't willing to make any compromise at
all for the benefit of their blind peers.
Though, while we're on the subject, is there any technical reason the
beep couldn't be replaced with a prerecorded mess
Samuel writes:
> for instance, because I documented how to test the speech-enabled
> installer on https://wiki.debian.org/DebianInstaller/Accessibility ,
> some debian-installer people do test it before releasing.
Yay!
>> What I am saying is that if a distro is going to make releases
>> with bui
According to Samuel
# I'm not saying that things are happening rightly ATM, but saying that
# things just always go that way in Debian is misleading, it's only MATE
# maintainers which seemingly don't proceed as they are supposed to.
Unfortunately this is far from my experience, as the first time
Hello,
Jefferey, on lun. 01 mai 2017 18:26:42 +, wrote:
> Did people actually complain about the beep?
Yes. The debian-boot people did complain that when they test images,
they'd keep getting beeps along all the tests. The compromise was then
found to include the beep only on the release imag
Chris, on lun. 01 mai 2017 11:27:22 -0700, wrote:
> Samuel writes:
> > https://wiki.debian.org/DebianInstaller/Accessibility
>
> The braille case is a little more difficult. For a couple years when
> I was developing Talking Arch, I didn't have access to a braille
> display.
That's not a problem
Samuel Thibault, on lun. 01 mai 2017 21:16:16 +0200, wrote:
> But if nobody had complained, it wouldn't.
And by "complain", I don't mean "babble about it on some random mailing
list or IRC channel somewhere on the Internet", but a proper report on
the debian-accessibility list. I'm really amazed
According to Chris
# When I maintained Talking Arch, I tested every release with at least one
# boot to make sure that it came up talking. I'm sure Kyle and Kelly do
# the same.
Absolutely. In fact, I build the TalkingArch iso after being sure my
working copy is in sync with the upstream Archis
Fair point about the need for communication with the proper channels,
but that also requires that people know about the proper channels.
Perhaps I'm guilty of not doing due diligence in seeking out the
proper channels, and perhaps whoever organizes the Debian website is
guilty of not putting the in
Luke Yelavich here, reply inline.
> The technical reason is merely that it needs implemeting withing
> syslinux: that requires sound drivers and whatnot, while the BIOS itself
> provides the support for beeps. So it's feasible, just needs to be done.
We also have to keep the move to UEFI in mind
Jeffery, on lun. 01 mai 2017 20:32:29 +, wrote:
> I would like a link to the subscribe page for the Debian Accessibility
> List.
https://lists.debian.org/debian-accessibility/
Samuel
___
Blinux-list mailing list
Blinux-list@redhat.com
https://www.r
Samuel here,
Luke, on mar. 02 mai 2017 06:36:14 +1000, wrote:
> Luke Yelavich here, reply inline.
> > The technical reason is merely that it needs implemeting withing
> > syslinux: that requires sound drivers and whatnot, while the BIOS itself
> > provides the support for beeps. So it's feasible,
Someone on the Linux for Blind General Discussion List hosted by
RedHat made a good point about the need for the users of accessibility
tools to communicate with the developers of those tools, and figured
it could use it's own thread both on the originating list as well on
IAVIT's Tech Talk.
So, i
Thanks for the link to the Debian Accessibility List. I have now
subscribed to that list.
--
Sincerely,
Jeffery Wright
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.
___
Hello, this is Samuel,
Linux for blind general discussion, on lun. 01 mai 2017 20:49:59 +, wrote:
> So, if you know of any mailing lists for specific accessibility
> projects to allow users and developers to discuss features, issues,
> bugs, etc., please share any information you can, such as
There was talk about removing the drums in Ubuntu. People were finding
this annoying when they were booting off of a CD in a class room,
library or meeting. Once I pointed out that this was important to the
blind to know when they can log on, the discussion ended. It had nothing
to do with the
31 matches
Mail list logo
