Board.KolibriOS.org

Dear KolibriOS Team

I am very nicely surprised by the fact that such a complex project like developing a new operating system from scratch based on such creative ingenuity.

I installed Kolibri and I can tell you, that as an avid visually impaired computer user, I pride myself on having the fastest systems on the market, but I have never been more impressed by the speed of any other Operating System than I was by Kolibri.

With the aid of a sited person I was able to successfully use the text editing application and partially play a few games.

I and millions of handy cap people would greatly enjoy the lovely features of Kolibri, if accessibility standards could be implemented.

I am shore that if such standards are included, the open source assistive teknology community wood quickly create specific software for Kolibri, or modify existing applications so that they can work with it.

I would like to test some accessibility features soon and help debug the operating system in all aspects.

If You implement accessibility many users would be extremely happy because of it and later, what about trying to implement some hot keys for controlling The
User interface and for controlling The Explorer?

Thank you very much, I am ready to contribute.

Please, tell your ideas or show concepts.

Leency wrote:Please, tell your ideas or show concepts. Also, you can run http://kolibri-n.org/files/KolibriN.7z to see some improvements.

Thank you for such a positive response. I have emailed several open source assistive technology groups for assistance. Hope they respond as quickly as you have. The following are resources and sum basic guidelines for making accessibility possible.
I am not a programmer but I can help in other areas. So please don’t hesitate to let me no.

Standards
Full keyboard and mouse access of all system operation that requires user interaction.
Key combinations used within an application should
Be consistent throughout the application
Standard keyboard navigation functionality should be maintained.
Interface Objects, Elements and Labels
Applications should use standard controls that provide clear, correct and concise object information.
Microsoft Active Accessibility (MSAA) should be used to provide object information.
Font, Size and Color
Applications should provide a variety of display options (e.g., font, size, and color and background selection).
Patterned backgrounds should be disabled when a Windows high-contrast setting is selected.
Font, size or color alone should not be used to convey information.
Audio Alerts
Applications should allow the user to choose visual cues for audio alerts.
Applications may provide an Option in the application's user preferences or another means of activating visual cues for audio alerts.
Volume Control
Applications should provide a volume control option for its own audio output.
System volume settings should be accessible with keyboard commands.
Animations and Multimedia
Video presentations should be accompanied by text and/or audio descriptions of the visual content.
Audio presentations should be accompanied by text captioning.
The equivalent accessible alternatives for an animation or multimedia presentation (i.e., text captioning and/or audio description) should be synchronized with the presentation.
An option for disabling animations or multimedia presentations should be provided.
The ability to access animations and multimedia presentations should not be required in order to use an application.
Blinking Elements and Marquees
An option should be available that allows the user to disable or adjust the frequency of blinking screen elements.
An option should be available that allows the user to disable or adjust the rate at which screen elements scroll.
Response Times
Important messages should be displayed until the user closes them.
The user should be alerted when a process is about to time-out. One or more of the following options should be provided.
•A method for indicating that more time is needed.
•A method for the user to adjust the time interval.
•A non-time dependent alternative.
Documentation
Application help files should contain accessibility information, including such topics as keyboard navigation and user preference settings. Note: Documentation on standard system keyboard navigation is optional.
Accessibility" should be included as both a keyword search and help topic item.
Keyboard Shortcuts" or a similar entry should be included as both a keyword search and help topic item.
The keyboard shortcut for a menu command should be documented within the menu, following the command.
Instructions for completing a task should include information for both mouse and keyboard users.
Documentation should be available in an accessible electronic format.

Resources for accessible API

Microsoft Active Accessibility client
http://msdn.microsoft.com/en-us/library/ms971310.aspx
JAVA Access Bridge
http://www.oracle.com/technetwork/java/index.html

IAccessible2 |
http://www.linuxfoundation.org/collabor ... ccessible2

UI Automation
http://msdn.microsoft.com/en-us/library/ms747327.aspx

Other Resources

Guidelines for Developing Accessible Interfaces and Interactive Environments:
http://www.imsglobal.org/accessibility/ ... /sec8.html

Mozilla Accessibility Project:
http://www.mozilla.org/access/

ZenKEY
http://zenkey.sourceforge.net/

WWAAC Web Browser
http://www.wwaac.eu/

AT-SPI
https://developer.gnome.org/at-spi-cspi/stable/

Software Oats
http://www.oatsoft.org/Software/listing ... entContent

Accerciser — oats:
http://www.oatsoft.org/Software/accerci ... entContent

The AGRIP Project:
http://agrip.org.uk/

Leency wrote:Please, tell your ideas or show concepts.

Helow, In order for a OS to be accessible, it must implement accessible APIs.
In my experience, i have found the multy platform Accessible2, to be the best but you will have to diside whitch of the fallowing API ssutes Kolibri.
In short, the OS most provide full keybord access to the OS funshions and provide screen reader suport thrue accessible API, sutch as the following.

Note, all Resources provided have full implementation guides.

Resources for accessible API

Microsoft Active Accessibility client
http://msdn.microsoft.com/en-us/library/ms971310.aspx
JAVA Access Bridge
http://www.oracle.com/technetwork/java/index.html

IAccessible2 |
http://www.linuxfoundation.org/collabor ... ccessible2

UI Automation
http://msdn.microsoft.com/en-us/library/ms747327.aspx

Hello. I looked at these APIs, and none of them are suitable for Kolibri. I think that most realistic and best solution should be completely new API specially for Kolibri.

SoUrcerer wrote:Hello. I looked at these APIs, and none of them are suitable for Kolibri. I think that most realistic and best solution should be completely new API specially for Kolibri.

Hmm. That, needs a lot of work in resourch. If nun of the APIs i provided can not be ported to Kolibri, guess knew branch is required. How can we do this and how fast can it get going!