Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    It won’t be supported because in most cases it is harmful to accessibility.

    Thread Starter frank tredici

    (@frank13)

    Really. Never heard that before. Do you have authoritative support for that?

    I have a simple 2 element form and all I want to do is have the focus auto placed on the first element — both on the form and in the form’s sequential listing.

    Didn’t want to have to implement more javascript to make it happen when it is a formal html attribute on the input tag.

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Even if there was an authoritative citation for it, that would kinda be missing the point. You don’t need someone to tell you authoritatively that it is bad for accessibility. We can just discuss it.

    The issue is when you move the focus automatically. It’s the equivalent of automatically moving your mouse into the field because the developer has decided easier for you to type.

    Thread Starter frank tredici

    (@frank13)

    Thanks for chiming in @andrew. No need for discussion, I fully understand the mechanics of autofocus. I was just surprised to hear the developer’s view on autofocus and its relationship to accessibility, usability and 508 compliance. I’ve been designing and developing websites since 1996 and that’s the first time I’ve ever heard that autofocus violates accessibility standards.

    If the plugin author wishes not to extend the plugin with the suggested feature, that’s not a problem. I can achieve it via javascript or otherwise write my own hook into the plugin to add autofocus for my own personal use. I was simply offering a suggesiton for a void in what is, for the most part, a fairly decent web form generator plugin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin Enhancement Suggestion — "autofocus"’ is closed to new replies.