• Resolved BeHeard

    (@beheard)


    ADA help please – screen reader or accessibility API issue with forms as all input areas read out as “input” rather than the field label,
    So a user has no concept of what part of the form they are at or what input is required.

    This textinput element does not have a name available to an accessibility API. Valid names are: label element, title undefined, aria-label undefined, aria-labelledby undefined.

    This form field should be labelled in some way. Use the label element (either with a “for” attribute or wrapped around the form field), or “title”, “aria-label” or “aria-labelledby” attributes as appropriate.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter BeHeard

    (@beheard)

    Also not picking up the submit button
    This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute “submit” or “image”, or BUTTON elements with type “submit” or omitted/invalid.

    Plugin Support Mane Grigoryan

    (@manegr)

    Hi dear @beheard ,
    Thanks for your inquiry.

    The form maker construct does not allow to have label elements and does not have submit type, but other attributes can be added with additional attributes. Note that the title attribute can be set with placeholder option. Here is a screenshot.

    Best Regards, Mane

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘form fields for accessibility API’ is closed to new replies.