Story #44912

Exploration: Accessible Neos Content Editing Module

Added by Sebastian Kurfuerst almost 9 years ago. Updated almost 9 years ago.

Status:
Accepted
Priority:
Must have
Category:
Content Editing
Target version:
Start date:
2013-01-29
Due date:
% Done:

63%

Estimated time:
(Total: 0.00 h)

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

Task #44926: Define roles for navigational landmarksAcceptedPatrick Broens2013-01-29

Actions
Task #44927: Define roles for document structureAcceptedPatrick Broens2013-01-29

Actions
Task #44929: Define roles for widgetsAcceptedPatrick Broens2013-01-29

Actions
Task #44930: Check if parts marked as widget need HTML markup changesAcceptedPatrick Broens2013-01-29

Actions
#1

Updated by Sebastian Kurfuerst almost 9 years ago

  • Assignee set to Patrick Broens
#2

Updated by Sebastian Kurfuerst almost 9 years ago

  • Status changed from New to Accepted
#3

Updated by Sebastian Kurfuerst almost 9 years ago

  • Subject changed from Explore responsive Neos backend to Exploration: Accessible Neos Content Editing Module

Also available in: Atom PDF