E-mail List Archives
Re: Disabled button
From: Birkir R. Gunnarsson
Date: May 10, 2018 6:46AM
- Next message: lynn.holdsworth@gmail.com: "Re: Is this Navigation or a Menu? How should it work?"
- Previous message: Steve Faulkner: "Re: Disabled button"
- Next message in Thread: None
- Previous message in Thread: Steve Faulkner: "Re: Disabled button"
- View all messages in this Thread
Just make sure to differentiate between disabled and read only.
A form field that has pre populated values use readonly to make it
fully discoverable.
For a button that is ninactive, disabled is good.
On 5/10/18, Steve Faulkner < <EMAIL REMOVED> > wrote:
>>
>> For disabled buttons, we need to provide focus ??
>
>
> The platform conventions are that for native HTML controls that can be
> disabled and are disabled are not keyboard focusable. There is no
> requirement in WCAG 2/2.1 for disabled controls to be focusable.
>
>
> --
>
> Regards
>
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
>
> On 10 May 2018 at 10:36, Kakarla Meharoon < <EMAIL REMOVED> > wrote:
>
>> Hi,
>>
>> For disabled buttons, we need to provide focus ??
>> >> >> >> >>
> > > > >
--
Work hard. Have fun. Make history.
- Next message: lynn.holdsworth@gmail.com: "Re: Is this Navigation or a Menu? How should it work?"
- Previous message: Steve Faulkner: "Re: Disabled button"
- Next message in Thread: None
- Previous message in Thread: Steve Faulkner: "Re: Disabled button"
- View all messages in this Thread