Although $1M doesn't go as far as it used to, this is very good news.
Congratulations and good luck in acquiring more funding as things progress!
As long as I'm writing, I'd like to mention a possible a11y-related project.
As many folks on this list may be aware, Microsoft Soundscape
I never published it and I'm not even sure I still have it, but I'll post a
note here if I find it. ISTR that the entire (Ruby?) code base was only a few
hundred lines.
-r
> On May 11, 2022, at 01:34, Sebastian Humenda wrote:
>
> ... Where can the code be found?
> On May 10, 2022, at 03:06, Sebastian Humenda wrote:
>
> Oh, so I would need to convert my computer braille to graphics before printing
> it? Never mind then and thanks for looking it up.
FWIW, I wrote some code a few years ago to do something like this on a Braille
Blazer. I used the
Thanks to Samuel and Devin for their input. As Devin said:
> Smart phones use touchscreen braille input to make typing faster. ...
> This attempts to bring this to Linux smart phones and such like that.
This is precisely my goal. I'd like to provide touchscreen braille input for
Linux smart
AFAIK, there isn't any braille screen input support for Linux, so I've been
considering trying to implement some. To be clear, I'm thinking about a
program that detects and characterizes touch events and then recognizes
gestures, and finally reports on these as Unicode sequences.
Approach
My
It's customizable and
extensible (in Lisp) and comes with a bazillion "modes" for doing various sorts
of things. OTOH, the learning curve is reputedly quite substantial. So, big
investment, but big return...
- Rich Morin
all of the common console screen readers. I realize that
the manual for each one probably documents this sort of thing, but my
impression (from you and other blind programmers) is that finding the
information isn't as easy as it should be.
- Rich Morin
andards (PEP8, POSIX ... (splitting lines
> in smaller chunks, 80 chars max, use of whitespace)) takes more time to
> learn but makes the code more accessible for everyone.
I agree. Fortunately, I tend to work on my own independent projects these
days, so I don't have to contend as much with those sorts of issues.
- Rich Morin
this feature.
However, I suspect that most users leave this turned off. So, the problem may
be difficult to recognize.
- Rich Morin
://en.wikipedia.org/wiki/Open_Telecom_Platform
- Rich Morin
> On Jan 6, 2022, at 06:53, Jeffery Mewtamer wrote:
>
> I thought the Cathedral represented proprietary software and FOSS was
> the Bazaar in that old metaphor...
Yep, my mistake. Actually, the difference is more like the BSDs and Linux.
There are only a few BSD Cathedrals (e.g., FreeBSD,
> On Jan 5, 2022, at 08:02, Jeffery Mewtamer wrote:
>
> I don't have any experience with Qemu, but assuming it can run x86
> guests on ARM hosts at all, my expectation is that a old model
> smartphone would be incapable of running Gnome or Mate within a
> virtual machine with anything
> On Jan 5, 2022, at 01:51, Jean-Philippe MENGUAL wrote:
>
> ... I prefer contributing to mainstream distros than creating a new one, as
> such maintainance may require a lot of work, the maintainers team is nearly
> always so small, so there is no future warranty for the end-user. ...
I kind
tl; dr - Here are some ideas about creating and maintaining accessible Linux
distros. Your mileage may vary, void where prohibited by law.
Some Background
To let folks know where I'm coming from, I'll start out with some background.
I'm a sighted programmer who has been working with free
from a given list,
etc.
> On Jan 2, 2022, at 17:28, Samuel Thibault wrote:
> Rich Morin, le dim. 02 janv. 2022 17:07:28 -0800, a ecrit:
>> Several of my email lists augment the Subject line with an identifying
>> prefix. I find this very useful in filtering, scanning, sorting,
Several of my email lists augment the Subject line with an identifying prefix.
I find this very useful in filtering, scanning, sorting, etc. Might we be able
to add a prefix such as "[DA] " or "[DAT] " to this list?
-r
Although I haven't seen many responses on the list, I've received some private
emails, so there seems to be _some_ interest. In any case, here are some Work
In Progress notes...
-r
# accessibility
Obviously, the definition of accessibility varies from user to user. For the
moment,
I'm intrigued by the possibility of repurposing old Android cell phones as
economical, blind-accessible portable computers. The Good News is that there
are billions of these devices out there, often available for very little money.
The Bad News is that the development efforts are quite
I've been musing about a comment Samuel Thibault made a while back:
> On Mar 2, 2020, at 07:57, Samuel Thibault wrote:
>
> Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit:
>> ... More generally, is there a better way to provide accessibility at boot
>> time?
>
The idea of detecting the presence (or absence) of a blind-related device seems
worth pursuing, even if there are some issues to be resolved.
For example, following Jude's notion of checking for a monitor, maybe Avahi and
SSH could be enabled whenever a monitor isn't found. For that matter,
Jude DaShiell said:
> If dummy was used for monitor type, the screen reader could come up talking
> without any monitor attached. ...
I can think of a couple of issues with this approach. First, there are various
reasons for leaving a monitor off a system. For example, if a RasPi is being
> On Mar 5, 2020, at 03:30, Samuel Thibault wrote:
>
> One thing I am missing in your description is: how is the system getting
> installed in your use case? Is it installed by the blind user himself,
> or by somebody else?
Ideally, the system hardware and software could be installed and
Thanks to everyone for considering these questions, offering suggestions, etc.
Here are some comments and clarifications.
I don't know all the ins and outs of preseeding, etc. So, I'll talk about use
cases. I'm mostly looking for a way to make freshly installed systems (e.g.,
PC, RasPi)
In another forum, I've been told that Orca is a rather heavyweight solution for
providing boot-time speech generation. It was recommended that I consider
Fenrir, instead. So, recasting my question, what would it take to make these
changes to the default Debian installation?
- include Fenrir,
> On Feb 24, 2020, at 10:26, Samuel Thibault wrote:
>
> Actually, we already had this idea in the past :)
>
> See the "Accessibility archive section?" section of
> https://wiki.debian.org/accessibility-devel
> (probably there are more to put there nowadays)
>
> I don't remember any reason for
> On Feb 24, 2020, at 08:15, Alex ARNAUD wrote:
>
> Which sections are you referring to? On packages.debian.org I'm seeing only
> "main", "contrib" and "non-free" sections.
Sorry, I seem to have pasted in the wrong URL. Please try this one, instead:
https://packages.debian.org/stable/
-r
I have some (probably naive) notions on improving the turnkey accessibility of
Debian and downstream distributions such as Raspbian and Ubuntu. Can folks let
me know whether any of these are feasible, already in place, etc?
The first notion has to do with the initial accessibility of the
I recently wrote the following note to debian-...@lists.debian.org:
> The Debian "List of sections" pages (eg, https://packages.debian.org/stable)
> have no section for accessibility. Please consider adding one, listing such
> packages as BRLTTY, Emacspeak, and Orca. If it helps, I'd be happy
Thanks, Samuel, for forwarding this. If nothing else, it prompted me to
join this mailing list!
I'd like to follow up with a request for help in documenting the kinds of
major dependencies that exist among the a11y-related packages (eg, brltty,
emacspeak, espeak-ng, espeak-ng-data, espeakup,
29 matches
Mail list logo
