Moodle

Form user error "Required" won't be read by screen readers as it's not part of <label>

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.8, 1.8.1, 1.8.2, 1.8.3, 1.9
  • Fix Version/s: None
  • Labels:
    None

Description

When a user misses a value of a required control in a form, and they press the Submit button, the form control is displayed in a red box with the text "Required" (see screenshot). There are 3 problems with this:

1. As explained for previous bugs MDL-8627 and MDL-11134, in Forms mode screen readers like JAWS do not normally read text outside labels or fieldset legends, so the text "Required" is missed.
2. The single word "Required" is unsufficient for non-visual users - it's to easy to confuse with the ALT text for the red "Required" asterisk *.
3. The behaviour described is achieved using Javascript - what happens without? And, the focus is not moved to the form control missing the value. Screen reader users, and potentially ANYONE for long forms, will miss the error.

Issue Links

Activity

Hide
Nick Freear added a comment -

(Mark as blocking 1.9 accessibility meta-bug)

  • This bug is tricky - may not be fixed for 1.9 release
Show
Nick Freear added a comment - (Mark as blocking 1.9 accessibility meta-bug)
  • This bug is tricky - may not be fixed for 1.9 release
Hide
Jason Scalco Piloti added a comment -

I like to resolve this issue =)

Show
Jason Scalco Piloti added a comment - I like to resolve this issue =)
Hide
Michael de Raadt added a comment -

Thanks for reporting this issue.

We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported.

If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

Michael d;

lqjjLKA0p6

Show
Michael de Raadt added a comment - Thanks for reporting this issue. We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported. If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed. Michael d; lqjjLKA0p6
Hide
Michael de Raadt added a comment -

I'm closing this issue as it has become inactive and does not appear to affect a current supported version. If you are encountering this problem or one similar, please launch a new issue.

Show
Michael de Raadt added a comment - I'm closing this issue as it has become inactive and does not appear to affect a current supported version. If you are encountering this problem or one similar, please launch a new issue.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: