i think the chance ereactos has is to develop accessibility as part of the os instead of depending on a screenreader. when reactos does all accessibillity stuff itself it can make things accessibel that are not accessibel with screenreaders because the accessibility is built into the os itself, like graphics are sent to the gpu text should be sent to the braille display, maybe it should be built like a monochrome mode, everything should still work but the used screen is not capable of anny graphics so just the text should be sent to it.
On Thu, 15 Nov 2018, Stefan L. wrote:
Hi, you might want to take a look at the goal of ReactOS again. Out current focus should target that goal. Writing screenreader stuff should be the same task and use exactly the same OS functions as in Windows. Thus, develop screen readers for Windows (possibly replacing / extending windows' gui libraries - but that would be a completely separate project, not part of ReactOS. Once that screenreader works on Windows, put effort into fixing bugs / missing features in ReactOS to get it working. Any other solution will not be worth the time and effort you put into it.
Just my personal opinion.
Best regards, basisbit
Am Do., 15. Nov. 2018, 10:21 hat Erkin Alp Güney erkinalp9035@gmail.com geschrieben: Windows NT console API is based on Matrix TUI concept, not TTY serial (means you get to handle line buffering yourself). However, unlike userspace, we can modify setup however we like as long as it has the desired end result.
Yours, faithfully Erkin Alp _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://reactos.org/mailman/listinfo/ros-dev