WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: <ul> for form layout?

for

From: Jonathan Avila
Date: Aug 10, 2017 12:16PM

  • Next message: Lovely, Brian (CONT): "aria-relevant question"
  • Previous message: Birkir R. Gunnarsson: "Re:
      for form layout?"
    • Next message in Thread: None
    • Previous message in Thread: Birkir R. Gunnarsson: "Re:
      I'm with you Birkir, I don't want to hear a bunch of list and list items unless they add some value. Agree it's not a failure if other content is marked up correctly -- but I feel like a lot of people add list markup specifically to benefit screen reader users when in fact many of them may find the extra verbosity not helpful. So the value versus verbosity overload must carefully be considered with any markup that is not needed for conformance.

      Jonathan

      Jonathan Avila
      Chief Accessibility Officer
      Level Access, inc. (formerly SSB BART Group, inc.)
      (703) 637-8957
      <EMAIL REMOVED>
      Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
      Looking to boost your accessibility knowledge? Check out our free webinars!

      The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

      -----Original Message-----
      From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
      Sent: Thursday, August 10, 2017 2:06 PM
      To: WebAIM Discussion List < <EMAIL REMOVED> >
      Subject: Re: [WebAIM] <ul> for form layout?

      Yeah, I totally see what you're sayng there.
      It is definitely not a user blocker or an outright violation. It's just a judgment call of verbiage vs. important info.
      I wouldn't fault it , but would bring it up as a decision to be made.
      The important thing is not to get fooled into thinking that putting the label and input in the same list item is enough to associate the label with the form field.

      I've seen people think that in the past, so I am always careful to point it out.


      On 8/10/17, Graham Armfield < <EMAIL REMOVED> > wrote:
      > For me, I think it's a valid use of an unordered list, and pretty much
      > every form I've created uses <ul> and places the label + input pairs
      > inside an <li> tag. It is, after all, a collection of related items -
      > in this case, form fields.
      >
      > If the screen reader announces that it's a list and tells the user how
      > many elements are in the list - ie how many form fields, that seems to
      > me to be useful information. If my form consists of 5 elements the
      > user may have a different expectation as to how long the form is going
      > to take compared to if there were 15 or more elements.
      >
      > When using this construct I always ensure that any hidden fields are
      > kept outside the <ul>.
      >
      > Regards
      > Graham Armfield
      > > > archives at http://webaim.org/discussion/archives
      > >


      --
      Work hard. Have fun. Make history.