E-mail List Archives

Re: Should disabled elements receive tab focus

for

From: Steve Faulkner
Date: Oct 28, 2016 3:23AM


native HTML interactive elements are implemented to not be focusable when
the disabled fattribute is set.

Adding tabindex="0" to a disabled button (for example) does not include it
in the focus order (because it is disabled).

suggest following platform interaction conventions is the right thing to
do.

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

On 28 October 2016 at 10:07, Mallory < <EMAIL REMOVED> > wrote:

> Disabled controls are not in the tab list. Someone suddenly breaking
> that pattern in one
> place would be extremely confusing. If I can focus on it, it should Do
> Stuff for me. If you
> let me focus on it, then it had better well Do Something when I click
> it.
>
> That some users choose to use tab for everything is not a good reason to
> make breaking
> changes. I know users who only use a mouse to click each form field; by
> the above logic,
> it would be a good thing to use auto-focus to save them some trouble.
> And of course that
> is a bad idea for many reasons.
>
> Readonlys, on the other hand, while not editable, do live in the tab
> list (because I can
> still for example select and copy that text).
>
> _mallory
>
> On Fri, Oct 28, 2016, at 01:08 AM, Thomas Lee McKeithan II wrote:
> > I differ. I believe that disabled buttons/controls should be in the tab
> > order providing the user an accurate representation of what's presented
> > on the page visually.
> >
> >
> > Respectfully,
> > Thomas Lee McKeithan II | Optum Technology Solutions
> > Electronic Accessibility Engineer, UX Design Studio (UXDS)
> > MD018, 6220 Old Dobbin Lane, Columbia, MD, 21045, USA
> >
> > T +1 443-896-0432
> > M +1 202-276-6437
> > <EMAIL REMOVED>
> > www.optum.com
> >
> >
> >
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > Behalf Of Moore,Michael (Accessibility) (HHSC)
> > Sent: Thursday, October 27, 2016 12:43 PM
> > To: WebAIM Discussion List
> > Subject: Re: [WebAIM] Should disabled elements receive tab focus
> >
> > If the button is disabled then it should not be included in the tab ring.
> > Screen reader users can find the button using standard reading controls.
> > Just make sure that it is in the proper location in the reading order for
> > the page.
> >
> > Mike Moore
> > Accessibility Coordinator
> > Texas Health and Human Services Commission Civil Rights Office
> > (512) 438-3431 (Office)
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > Behalf Of Ajay Sharma
> > Sent: Thursday, October 27, 2016 11:39 AM
> > To: <EMAIL REMOVED>
> > Subject: [WebAIM] Should disabled elements receive tab focus
> >
> > Hello and Greetings,
> >
> >
> > Looking for some expert advice on the case where it is desired by the
> > screen reader users that tab focus should go on disabled button and
> > screen reader should announce it's name, role and state which is
> > disabled. But doing so would affect the usability of keyboard only users
> > as the tab focus would land on non interactive element.
> > There are certain instances where the disabled control gets tab focus
> > both in the case of web and desktop applications, but there is no spec or
> > guideline that directly address to this issue.
> >
> > So, please share your thoughts on it and I'd greatly appreciate if there
> > is some specs are already there.
> >
> > Best Regards,
> > Ajay
> > > > > > at http://webaim.org/discussion/archives
> > > > > > > > at http://webaim.org/discussion/archives
> > > >
> > This e-mail, including attachments, may include confidential and/or
> > proprietary information, and may be used only by the person or entity
> > to which it is addressed. If the reader of this e-mail is not the
> > intended
> > recipient or his or her authorized agent, the reader is hereby notified
> > that any dissemination, distribution or copying of this e-mail is
> > prohibited. If you have received this e-mail in error, please notify the
> > sender by replying to this message and delete this e-mail immediately.
> > > > > > > > > > > > >