On Tue, Aug 29, 2017 at 09:31:43AM +0200, Olivier Fourdan wrote:
> Hi,
>
> I would like to revive this keyboard accessibility discussions started
> before here [1], more specifically about slowkeys, stickykeys and
> bouncekeys.
>
> We can choose to add support for those either client side or serv
Hi,
I would like to revive this keyboard accessibility discussions started
before here [1], more specifically about slowkeys, stickykeys and
bouncekeys.
We can choose to add support for those either client side or server side.
The general consensus was it would better be server side (fwiw, I
com
Hi,
On 11 March 2016 at 09:31, Pekka Paalanen wrote:
> On Fri, 11 Mar 2016 15:46:21 +1000
> Peter Hutterer wrote:
>> On Thu, Mar 10, 2016 at 01:43:13PM -0500, Matthias Clasen wrote:
>> > I would like to discuss strategies for implementing accessibility
>> > features in Wayland that will be neede
On Fri, Mar 11, 2016 at 02:13:03PM +0800, Jonas Ådahl wrote:
> Hi,
>
> On Fri, Mar 11, 2016 at 06:51:35AM +0100, Timofonic wrote:
> > Please consider mandatory high contrast option with custom colors. I prefer
> > black background and green foreground, it's a lie better for Mr eyes
> > because c
>
> Btw. Matthias guessed an implementation would belong in xkbcommon, but
> that is also used client-side. How does that fit in with server-side
> accessibility implementation?
This is where I would really hope for Daniel Stone to chime in...
___
waylan
On Fri, Mar 11, 2016 at 12:51 AM, Timofonic wrote:
> Please consider mandatory high contrast option with custom colors. I prefer
> black background and green foreground, it's a lie better for Mr eyes because
> clear colors really tire me.
>
> Text-To-Speech and braille devices should be very serio
On Fri, Mar 11, 2016 at 03:46:21PM +1000, Peter Hutterer wrote:
> On Thu, Mar 10, 2016 at 01:43:13PM -0500, Matthias Clasen wrote:
> > Anyway, I'd like to hear people's thoughts about this topic.
>
> fwiw, I fully agree that this need to be implemented on the compositor side.
> Client-side first i
On Fri, Mar 11, 2016 at 06:51:35AM +0100, Timofonic wrote:
> Please consider mandatory high contrast option with custom colors. I prefer
> black background and green foreground, it's a lie better for Mr eyes because
> clear colors really tire me.
>
> Text-To-Speech and braille devices should be
On Fri, 11 Mar 2016 15:46:21 +1000
Peter Hutterer wrote:
> On Thu, Mar 10, 2016 at 01:43:13PM -0500, Matthias Clasen wrote:
> > Hi,
> >
> > I would like to discuss strategies for implementing accessibility
> > features in Wayland that will be needed for a fully featured desktop.
> > There's a wh
Hi,
On Fri, Mar 11, 2016 at 06:51:35AM +0100, Timofonic wrote:
> Please consider mandatory high contrast option with custom colors. I prefer
> black background and green foreground, it's a lie better for Mr eyes because
> clear colors really tire me.
There is no way for a compositor to enforce
Please consider mandatory high contrast option with custom colors. I prefer
black background and green foreground, it's a lie better for Mr eyes because
clear colors really tire me.
Text-To-Speech and braille devices should be very seriously very taken in
consideration too, please. I know many
On Thu, Mar 10, 2016 at 01:43:13PM -0500, Matthias Clasen wrote:
> Hi,
>
> I would like to discuss strategies for implementing accessibility
> features in Wayland that will be needed for a fully featured desktop.
> There's a whole list of individual items, but for now I'd like to
> focus on keyboa
Hi,
I would like to discuss strategies for implementing accessibility
features in Wayland that will be needed for a fully featured desktop.
There's a whole list of individual items, but for now I'd like to
focus on keyboard accessibility features, ie roughly the feature that
traditionally labeled
13 matches
Mail list logo
