mahara-contributors team mailing list archive

[Kristina Hoeppner <1262483@xxxxxxxxxxxxxxxxxx>]

>From bug#1261242:

Currently, form errors are usually shown with a notification at the top of the page and specific errors beside each form element. For people using screen readers this is not optimal since the errors do not show up when tabbing through the page.
Either errors should be grouped in a list at the top of the page, or each explanation should be linked to the relevant input using aria-describedby.

Affects latest master (using Orca 3.4.2)

(WCAG Level A)

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

Title:
  Forms should consistently have errors above the top-level heading

Status in Mahara ePortfolio:
  New

Bug description:
  If you submit a form with validation errors, most of the time a message comes up above the <h1> on that page warning you that there are errors. However a few pages do not have this feature and only have error messages beside the invalid inputs.
  Consistency is important to users of screen readers, who may assume that a form has submitted correctly if the error message does not appear where they expect.
  All pages need to be checked, but so far the Create Group form and the Profile (Content -> Profile) form do not report errors at the top of the page.

  Affects latest master

  (WCAG Level A)

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