E-mail List Archives
Thread: Disabled button
Number of posts in this thread: 3 (In chronological order)
From: Kakarla Meharoon
Date: Thu, May 10 2018 3:36AM
Subject: Disabled button
No previous message | Next message →
Hi,
For disabled buttons, we need to provide focus ??
From: Steve Faulkner
Date: Thu, May 10 2018 4:17AM
Subject: Re: Disabled button
← Previous message | Next message →
>
> 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 ADDRESS REMOVED = > wrote:
> Hi,
>
> For disabled buttons, we need to provide focus ??
> > > > >
From: Birkir R. Gunnarsson
Date: Thu, May 10 2018 6:46AM
Subject: Re: Disabled button
← Previous message | No next message
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 ADDRESS 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 ADDRESS REMOVED = > wrote:
>
>> Hi,
>>
>> For disabled buttons, we need to provide focus ??
>> >> >> >> >>
> > > > >
--
Work hard. Have fun. Make history.