mahara-contributors team mailing list archive

[Kristina Hoeppner <1860600@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In Mahara 19.10 we introduced the new grid layout and have an accessible
layout option available that allows the screenreader to use it without
drag and drop. This accessible layout option is currently available on
personal pages, but not group, institution, and site pages.

The accessible layout option also needs to be available in the other
areas.

Proposal:

Scenario 1:

Paula has her preferences set to use an accessible layout. When she
creates a group page, the page is automatically created in an accessible
layout. She can though overrule that option in the "Advanced" options of
the page.

Petra is a fellow group member who has the permission to edit group
pages. When she edits the page that Paula created, the page continues to
be in the accessible layout. She can use drag and drop to place blocks
onto the page, but the blocks are full-width, i.e. instead of clicking
the "Add" button, she can drag and drop, but the rest of the page layout
stays accessible with full-width blocks.

Scenario 2:

Petra creates a group page in a normal layout, ignoring the "Accessible
layout" option in the page settings.

Paula, who has accessibility options turned on, sees a modal when she
goes into edit mode of the group page alerting her to the fact that the
page was not created in an accessible layout and that blocks can be not
full width.

When she places blocks onto the page, the "Add" button is clickable
(rather than drag and drop) and puts a full-width block onto the page
either at the start or the bottom as she determines.

Petra can change the width of the block when she edits the page.

---

Are these scenarios doable? Scenario 2 would also be one for template
pages when a person with accessibility option set to "Yes" edits a
template page.

** Affects: mahara
     Importance: Wishlist
         Status: Triaged


** Tags: accessibility

-- 
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/1860600

Title:
  Make accessible layout available on group, institution, and site pages

Status in Mahara:
  Triaged

Bug description:
  In Mahara 19.10 we introduced the new grid layout and have an
  accessible layout option available that allows the screenreader to use
  it without drag and drop. This accessible layout option is currently
  available on personal pages, but not group, institution, and site
  pages.

  The accessible layout option also needs to be available in the other
  areas.

  Proposal:

  Scenario 1:

  Paula has her preferences set to use an accessible layout. When she
  creates a group page, the page is automatically created in an
  accessible layout. She can though overrule that option in the
  "Advanced" options of the page.

  Petra is a fellow group member who has the permission to edit group
  pages. When she edits the page that Paula created, the page continues
  to be in the accessible layout. She can use drag and drop to place
  blocks onto the page, but the blocks are full-width, i.e. instead of
  clicking the "Add" button, she can drag and drop, but the rest of the
  page layout stays accessible with full-width blocks.

  Scenario 2:

  Petra creates a group page in a normal layout, ignoring the
  "Accessible layout" option in the page settings.

  Paula, who has accessibility options turned on, sees a modal when she
  goes into edit mode of the group page alerting her to the fact that
  the page was not created in an accessible layout and that blocks can
  be not full width.

  When she places blocks onto the page, the "Add" button is clickable
  (rather than drag and drop) and puts a full-width block onto the page
  either at the start or the bottom as she determines.

  Petra can change the width of the block when she edits the page.

  ---

  Are these scenarios doable? Scenario 2 would also be one for template
  pages when a person with accessibility option set to "Yes" edits a
  template page.

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