mahara-contributors team mailing list archive

[Jono Mingard <jonom@xxxxxxxxxxxxxxx>]

My current thinking is that we should do a JS-based solution rather than
trying to modify the non-js editor, but not rely on ARIA attributes
(since not only are they badly supported, they can stop parts of the JS
from running properly in some screen readers).

IMO we should make the block types selectable with the keyboard and have
a popup when Space/Enter is pressed which displays the places they can
be put ("Row 1 Column 1", "Row 3 Column 2", etc), and have a button next
to the Edit button for each content block (called "Move" or something)
which brings up the same menu and allows the block to be moved. After
these changes the rest of the editor should be quite accessible (once
alt texts and suchlike are sorted out)

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1262933

Title:
  Drag-and-drop page editor is not keyboard-accessible

Status in Mahara ePortfolio:
  New

Bug description:
  Currently the drag and drop page editor cannot be used with the keyboard. This is a major accessibility problem for people who rely on the keyboard and are unable to use a mouse easily.
  There are two options for making this accessible: Implement keyboard drag-and-drop using ARIA and Javascript or display the non-js editor for screen reader users (and make that accessible)

  It seems that ARIA drag-and-drop attributes are not well supported
  among most screen readers but a mostly-JS approach (like in
  http://dev.opera.com/articles/view/accessible-drag-and-drop/) can work
  well.

  Affects latest master

  (WCAG Level A)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1262933/+subscriptions