E-mail List Archives
Re: SC 3.3.2 - visible labels required?
From: Maxability A11Y
Date: Dec 3, 2017 11:09PM
- Next message: Zack Davis: "Average Time to Create an Accessible PDF"
- Previous message: Sonja Weckenmann: "SC 3.3.2 - visible labels required?"
- Next message in Thread: None
- Previous message in Thread: Sonja Weckenmann: "SC 3.3.2 - visible labels required?"
- View all messages in this Thread
Hi there,
In addition to the title I recommend having the first option or the default
option as Select time or similar. This value will be visible for everyone
until the user selects a specific option.
On Mon, Dec 4, 2017 at 1:46 AM, Sonja Weckenmann < <EMAIL REMOVED> > wrote:
> Hi,
>
> I'm testing a timetable form of a local public transport site.
>
> There's a form, that consists out of two text inputs for "start" and
> "destination" and two selects for "date" and "time".
>
> The selects don't have labels. They show the actual date and time.
>
> Does WCAG (3.3.2 labels and instructions) require a visual label for the
> selects? Would it be sufficent to implement a hidden label or a
> title-attribut?
>
> Technique H65 (sufficient technique for 3.3.2) recommends a title-attribut
> when the visual design cannot accommodate the label, but what about sighted
> keyboard user?
>
> As there are (in other form elements of the site) floating labels, this
> might be a better solution? I'm not sure if it fits to the design...
>
> Thanks a lot
> Sonja
>
> > > > >
- Next message: Zack Davis: "Average Time to Create an Accessible PDF"
- Previous message: Sonja Weckenmann: "SC 3.3.2 - visible labels required?"
- Next message in Thread: None
- Previous message in Thread: Sonja Weckenmann: "SC 3.3.2 - visible labels required?"
- View all messages in this Thread