WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Required Fields and Username / Password on a Website

for

From: Srinivasu Chakravarthula
Date: Jul 24, 2012 3:43AM

Hi Jeevan,
I got your point. If we have this indication "off-screen" or with
"aria-required", is that available to all the users? No, the information
would only be available to screen reader or text only browsers only.

Again, if user is having learning disability, not necessary, he / she
should know the both user name / password are mandatory.

Thanks,
-Srini

On Tue, Jul 24, 2012 at 3:05 PM, Jeevan Reddy < <EMAIL REMOVED> >wrote:

> Hi Srini,
> You are right, but the required fields are meant to tell the user
> to fill certain fields among many to get the access, but in sign in
> widget has default mandatory fields known to everyone. To enhance
> accessibility without compramising on design i suggest to use screen
> off or aria method.
>
> On 7/24/12, Srinivasu Chakravarthula < <EMAIL REMOVED> > wrote:
> > Hi Jeevan and others,
> > If we decide to include indication, it "must" be visible. Putting the
> same
> > as off-screen or aroa-required would be helpful to users with vision
> > impairment, but the indication would be more helpful to those having
> > cognitive disabilities.
> >
> > Thanks,
> > -Srini
> >
> > On Tue, Jul 24, 2012 at 12:03 PM, Jeevan Reddy
> > < <EMAIL REMOVED> >wrote:
> >
> >> L,
> >> Though the user name and password fields default required, for the
> >> common user point of you, including visible required field indicator
> >> is good option.
> >> For the conformance view, you can either offscreen the "*/required" or
> >> use Aria-Required property in case design doesn't prompt you to use
> >> visible indicators.
> >>
> >> On 7/24/12, Elle < <EMAIL REMOVED> > wrote:
> >> > All:
> >> >
> >> > We're redesigning our website, and there's discussion about whether
> any
> >> > indication of required fields is necessary for "username" and
> password"
> >> to
> >> > sign into the member portal. All the Section 508 and WCAG 2.0
> >> > documentation I see seems to state that it's a violation if you don't
> >> > indicate "this field is required" by either an asterisk, an image,
> text
> >> > (ex. "required"), or grouping like fields together by validation.
> >> However,
> >> > the WCAG content seems more for multiple form fields. On the
> >> > Section508.gov website, the Search text input field responds like a
> >> > required field (it has a validation / error prompt if you hit Submit
> >> > without entering text), but there is no indication that Search is a
> >> > required field to successfully Submit. My UX team is telling me that
> >> > Username and Password are obviously required if you want to sign in on
> >> > a
> >> > website, and that even an asterisk is unnecessary. So, my questions
> >> > are:
> >> >
> >> >
> >> > 1. Is it necessary (to meet conformance requirements) to have an
> >> > asterisk next to Username and Password for a sign-in widget on a
> >> > website?
> >> > 2. If the guidance text ** Required* exists near the top of the
> >> > page,
> >> > can we remove it from a similar sign-in widget on the left rail?
> >> >
> >> >
> >> > Thanks very much,
> >> > Elle
> >> > > >> > > >> > > >> >
> >>
> >>
> >> --
> >> Best Regards,
> >> Jeevan Reddy,
> >> Accessibility Consultant,
> >> Onya Digital Solutions Pvt Ltd,
> >> Bangalore, India.
> >> > >> > >> > >>
> >
> >
> >
> > --
> > Regards,
> >
> > Srinivasu Chakravarthula - Twitter: http://www.twitter.com/VasuTweets
> > Website: http://www.srinivasu.org | http://www.learnaccessibility.org
> >
> > Let's create an inclusive web!
> > > > > > > >
>
>
> --
> Best Regards,
> Jeevan Reddy,
> Accessibility Consultant,
> Onya Digital Solutions Pvt Ltd,
> Bangalore, India.
> > > >



--
Regards,

Srinivasu Chakravarthula - Twitter: http://www.twitter.com/VasuTweets
Website: http://www.srinivasu.org | http://www.learnaccessibility.org

Let's create an inclusive web!