Re: Alternative defaults for visually impaired users? (was: [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?))

[Eli Zaretskii]

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: jonas@bernoul.li, samologist@gmail.com, emacs-devel@gnu.org,
>  karthikchikmagalur@gmail.com, visuweshm@gmail.com, raman@google.com
> Date: Sun, 22 Dec 2024 09:29:00 +0000
> 
> Richard Stallman <rms@gnu.org> writes:
> 
> >   > I guess that Emacsspeak already provides some good defaults for blind,
> >   > thanks to T.V. Raman's continuous dedication.
> >   > But maybe we want things to be available in vanilla Emacs as well?
> >
> > It depends what "available" means.  If it means having a package
> > that would install suitable different bindings and settings, it sounds
> > fine in principle -- but does Raman want to maintain them that way?
> > It might be a bigger change for him than for users of his work.
> 
> No, I did not mean a package. I meant support and maintenance in Emacs
> core. IMHO, these features are too important for third-party package that
> might be abandoned.
> 
> The initial input about alternative defaults may come from Raman,
> Samuel, or other interested users who had to customize Emacs in similar
> ways.
> 
> >                                                                       Not
> >   > just for blind, but also settings with large font sizes.
> >
> > I have a feeling that the changes for large fonts would be totally
> > dissimilar to those for screen reading.  I'm not an expert, though,
> > bu does anyone actually _know_ whether they have much in common?
> 
> I do not think that they have much in common in terms of specific
> changes to Emacs defaults. What might be common is the way to enable
> accessibility defaults - I have specific API design in mind, but do not
> want to discuss it before I see how the general idea is received.

We do want to have accessibility features in Emacs, if that is what
you are asking.  (In some cases we already do: e.g., see the
Windows-specific variable w32-use-visible-system-caret, which aims
specifically at aiding screen-reading software.)