Story #44912
Exploration: Accessible Neos Content Editing Module
| Status: | Accepted | Start date: | 2013-01-29 | ||
|---|---|---|---|---|---|
| Priority: | Must have | Due date: | |||
| Assigned To: | Patrick Broens | % Done: | 63% |
||
| Category: | Content Editing | Spent time: | - | ||
| Target version: | Sprint February 2013 | ||||
| Story points | - | ||||
| Velocity based estimate | - |
Description
As a user with disabilities, I want an accessible Neos Content Editing Module in order to interact with the website. This task is about exploring the steps towards a more accessible Neos.
DoD is an answer to the following question:
- What do we need to change in order to improve accessibility? What are easy-to-fix things in this area?
- Which general guidelines should we adhere to when creating new JavaScript parts in the Content Module?
- What needs to be done in the remaining Neos backend (f.e. Management Module) to make it accessible?
- How can keyboard shortcuts help with Accessibility?
Subtasks
History
#1 Updated by Sebastian Kurfuerst over 2 years ago
- Assigned To set to Patrick Broens
#2 Updated by Sebastian Kurfuerst over 2 years ago
- Status changed from New to Accepted
#3 Updated by Sebastian Kurfuerst over 2 years ago
- Subject changed from Explore responsive Neos backend to Exploration: Accessible Neos Content Editing Module