W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2001

Re: form controls: mandatory status

From: Charles McCathieNevile <charles@w3.org>
Date: Sun, 9 Dec 2001 03:08:16 -0500 (EST)
To: "Mirabella, Mathew J" <Mathew.Mirabella@team.telstra.com>
cc: "'W3C WAI Web Content Accessibility Guidelines list'" <w3c-wai-gl@w3.org>
Message-ID: <Pine.LNX.4.30.0112090230140.13312-100000@tux.w3.org>

there are a couple of approaches I would combine.

First idea is that it is important for everyone to be able to find things
that are mandatory, not just non-visual users. So hiding the information
doesn't seem a great idea.

Second is that screenreader users in particular try to reduce the number of
punctuation marks they have to listen to.

Third, they are one of the groups that commonly navigates just the active
elements of a page (such as links and labels).

So I would be inclined to use something like

  <p><label for="username">Username (required):</label>
  <input name="username" id="username" type="text" value="" size="30" accesskey="u" />
I would be inclined to use CSS to add something like a backgrouond that
signified things which are required, but not to rely on it, since the
information that this field is required is an important part of the content
of the page.

Note that this is also required to conform to the WCAG checkpoint

  12.4 Associate labels explicitly with their controls. [Priority 2]
    For example, in HTML use LABEL and its "for" attribute.

I would argue that not having the information that something is required in
the label fails this requirement.



On Fri, 7 Dec 2001, Mirabella, Mathew J wrote:


  A query and item for discussion.  How to indicate the mandatory status of
  form controls to users in a visual and non-visual way.

Received on Sunday, 9 December 2001 03:08:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:39 UTC