Make JD accessible to the disabled.
|Revision:||13662||Resolution:||To be discussed|
We recieved Feedback from a user on facebook that JD is currently not accesible to the disabled. Let's check how much effort would be required to fix this issue.
Wie akzeptiert man die AGB´s? ich öffne mit click auf die DLC Jdownloader und warte bis die entgrüption vollständig abgeschlossen ist. ich markiere den Fiele, und drücke Alt+S oder eingabe. dann muss man die AGB´S akzeptieren- wie geht dies mit der Tastatur unter dem Screenreading-Programm Jaws?
https://www.facebook.com/jdownloader/posts/177725235605378 (9th comment) by Florian Schwab.
Updated by drbits over 2 years ago
- Category changed from General to GUI
Related to discussion http://board.jdownloader.org/showpost.php?p=134287&postcount=31
This is part of an old issue about making JDownloader follow the regulations for supporting the disabled. The regulations in the US (ADA) and the EU are similar. W3C has links to recommendations. The following are all normal guidelines.
Note: If the highlight is moved to a grid space, menu item, a tab, or a tree item, a screen reader will read that location. For edit boxes, the label of the edit box is usually read, followed by the contents of the edit box.
If the cursor is moved to text, the screen reader will read the text (line by line or paragraph by paragraph, depending on settings).
For those using a mouth-stick or other mobility device, the keyboard is set to make Ctrl and Alt (Command and Apple) keys "Sticky". So instead of clicking on Ctrl+Enter, the user would click on Ctrl, Enter, Ctrl. This is part of why no controls can be graphic pointer (rodent) only. Some users use Rats instead of Mice (Rats are foot controlled).
These recommendations were originally made over a year ago as part of the menu update recommendations. There have been several users requesting easier navigation and screen reader compatibility.
Make sure that in all dialogues (including Jelsoft forms) accept Enter (Return) for OK (Accept, Continue, usw) and Esc for Cancel (Reject, Brechen, usw). Space should substitute for Enter. Right-Arrow, then Enter or Space should substitute for Esc.
All commands (including those in the context menu and toolbar) must be in the menus.
The first menu must be accessible with Alt+space (or Apple+Space). Right and left arrows move between menus (or open and close submenus), up and down arrows move to the previous or next item in a menu. All toggles should have a checkbox. Selecting (or toggling) a menu item should be available with Enter (Space should also work).
The menus should probably be converted to a more normal layout (JDownloader, Edit, View, Tools, Settings (possibly), Help).
The grids should allow changing row with up and down arrows. Right and left arrows open and close child levels (currently just the Links). Tab (Shift+Tab) move between columns (for sorting and for screen readers). Ideally, Enter in an editable grid item (such as package name) will allow editing it. Alt+Enter (Apple+Enter) Will open or close the Properties pane. Ctrl+Enter (Command+Enter) will switch to the Info Pane to allow screen reader access. Ctrl+F10 (Command+F10) opens the context menu with the first item highlighted.
Ctrl+Tab (Command+Tab) and Ctrl+Shift+Tab (Command+Shift+Tab) should move between tabs.
Controls for the Settings tree should be similar to the controls for the grids (arrows move up and down, left and right open/close submenus and move). Page_Up/Page_Down should move between the Settings tree and the corresponding Settings page.
The user should be able to navigate the settings page using the Tab/Shift+Tab keys to move left and right, and the arrows to move between lines.
The Ctrl+Arrow keys are normally reserved for mouse cursor emulation. Ctrl+Delete is normally reserved to clear a field. (Command key can substitute for the Ctrl key).
Additional recommended changes
The current text magnification is too limited. It should be changed to a range of 50% to 1600%. Those who are "visually impaired" but not "blind" usually have large, panning desktops. The text magnification should apply to the entire program (including the scroll bars, separators, and so on). It is like a magnifying glass held in front of the display. The JD window should be extensible to 2400 by 2400 pixels if the desktop is large enough.
There should be an easy way to subscribe to a Captcha-Response service that responds to all Captchas that JD cannot solve on its own (not just reCaptcha). Captchatrader does this, I do not know about other services. This is like buying premium on a host. The plugin should be downloaded and installed and the UserName and Password should be made available to the plugin, just as they are for Premium hosts. Maybe they could be listed as a separate section in the accounts list. (I am not talking about Earning Captcha Points, but purchase only)
All parts of the program display should be readable in tritone (such as Black, 33% gray, and White or variants based on a hue). A style should be provided that provides tritone and allows the user to select the three colours. Part of this is visibility, and part is for screen readers.
Priority should rise with each Major release. Should be scheduled for release in version 1.2.0 (next+2) or by 1 year after release of version 1.0.0.
Updated by raztoki about 2 years ago
Its been asked that jDownloader supports the ability for the visually impaired and software which supports their needs for example http://www.nvda-project.org/ which ports text to audio.
Additionally I think we need to support audio capture challenges as an alternative method to image challenges as visually impaired could find a images unsolvable (especially with recaptcha current shadowing practices)
Updated by jiaz over 1 year ago
Also check if we can make it work with JAWS