ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Accessibility: Tabindex (Feature #700)
| Status: | Open | Start date: | 2011-11-15 |
|---|---|---|---|
| Priority: | Normal | Due date: | |
| Assignee: | Romano Licker |
% Done: | 0% |
| Category: | User interface | ||
| Target version: | - | ||
| Remote issue URL: | Affected version: | unstable |
Description
The application needs to have a logical tab order.
Disabled people use the tab-key in order to navigate through the application.
However giving each single element (which can have a focus) a tabindex would do more harm than good.
If a new element is added to the application, lets say a checkbox, and the author does not give a correct tabindex, the checkbox would be the last element reachable.
Currently there are some elements having a tabindex and destroying the document tab-order completely (some are in the jstoolbar.js).
I will now try to remove all tabindex and figure out, if the taborder is than logical and accessible.
Im working on new_design/ticket/692/new-design-for-review + pull request - if someone has objections - feel free to contact me.
History
Updated by Romano Licker at 2011-11-16 10:27 am
I completed the work.
What to do now?
I worked on the branch eric used for his pull request.
I can open a pull request for that branch but that wouldn't be a logical order. Should I do it anyway?
One commit is dependent on the new design - i could extract the rest - but than we would have one loose commit.
Suggestions?
- Assignee changed from Romano Licker to Eric Davis
Updated by Romano Licker at 2011-11-16 10:27 am
- Assignee changed from Eric Davis to Romano Licker
Updated by Eric Davis at 2011-12-10 09:49 pm
Feel free to send a pull request based on the unstable branch. Once it's reviewed I'll be able to decide which version it should fit in.
Removing from 3.0. Reason: no public code and approaching 3.0 feature freeze.
- Target version deleted (
3.0.0)