ReactOS accessibility

[Ali Savas]

Good evening everyone,

I know that this topic has been discussed here before, but I think it's
better if the topic is brought to mind every now and then so that it
doesn't get forgotten.

What is the current state of ReactOS accessibility? Even though ReactOS
is not yet accessible in its current form, how much attention is being
paid to the accessibility of ReactOS during development?

In addition to keyboard usability, it is also important to provide
information about MSAA, UIA and more. These and similar things can be
built in after the fact, but this can be very costly to retrofit
depending on the application or user interface. Therefore, it is even
more important to consider from the beginning that in the future the
user interface or the application must be accessible.

Here the cooperation with the NVDA project offers itself.

With kind regards
Ali

[Mark Jansen]

Hello,

As far as I know there are no efforts in progress to work on accessibility.

This is a complex subject, and it requires both NT knowledge (for the 
integration),
as well as knowledge about accessibility, and how tools related to it 
work (or are supposed to work).

Ideally someone with knowledge about accessibility could look into this.
Currently this is the only way I see this progressing.

Regards,

Mark

On 05-Jan-21 20:06, Ali Savas wrote:
>   Good evening everyone,
>
>  I know that this topic has been discussed here before, but I think it's
>  better if the topic is brought to mind every now and then so that it
>  doesn't get forgotten.
>
>  What is the current state of ReactOS accessibility? Even though ReactOS
>  is not yet accessible in its current form, how much attention is being
>  paid to the accessibility of ReactOS during development?
>
>  In addition to keyboard usability, it is also important to provide
>  information about MSAA, UIA and more. These and similar things can be
>  built in after the fact, but this can be very costly to retrofit
>  depending on the application or user interface. Therefore, it is even
>  more important to consider from the beginning that in the future the
>  user interface or the application must be accessible.
>
>  Here the cooperation with the NVDA project offers itself.
>
>  With kind regards
>  Ali
>
>
>  _______________________________________________
>  Ros-general mailing list
>  Ros-general(a)reactos.org
>  http://reactos.org/mailman/listinfo/ros-general

[wyattcjackson2006]

I don't know much about accessibility, but I do think we need to make sure we can use
the desktop (at very least the React menu), control panel, file manager, and other system
utilities that one might need to use without a mouse, accessible with the keyboard. I
think we should also get an onscreen keyboard for ReactOS as well for when the mouse
works, but not the keyboard.Minecraftchest1Minecraftchest1.wordpress.comSent from my
T-Mobile 4G LTE Device
-------- Original message --------From: Mark Jansen <mark.jansen(a)reactos.org> Date:
1/13/21  5:52 AM  (GMT-06:00) To: ros-general(a)reactos.org Subject: Re: [ros-general]
ReactOS accessibility Hello,As far as I know there are no efforts in progress to work on
accessibility.This is a complex subject, and it requires both NT knowledge (for the
integration),as well as knowledge about accessibility, and how tools related to it work
(or are supposed to work).Ideally someone with knowledge about accessibility could look
into this.Currently this is the only way I see this progressing.Regards,MarkOn 05-Jan-21
20:06, Ali Savas wrote:> Good evening everyone,>> I know that this topic has been
discussed here before, but I think it's> better if the topic is brought to mind
every now and then so that it> doesn't get forgotten.>> What is the current
state of ReactOS accessibility? Even though ReactOS> is not yet accessible in its
current form, how much attention is being> paid to the accessibility of ReactOS during
development?>> In addition to keyboard usability, it is also important to
provide> information about MSAA, UIA and more. These and similar things can be>
built in after the fact, but this can be very costly to retrofit> depending on the
application or user interface. Therefore, it is even> more important to consider from
the beginning that in the future the> user interface or the application must be
accessible.>> Here the cooperation with the NVDA project offers itself.>> With
kind regards> Ali>>> _______________________________________________>
Ros-general mailing list> Ros-general(a)reactos.org>
http://reactos.org/mailman/listinfo/ros-general____________________________…
mailing [e-mail]://reactos.org/mailman/listinfo/ros-general