• Resolved Michael

    (@whispardesign)


    Hello,

    We are gettting a few critial fails on ADA scans as follows for the login page using the [swpm_login_form] shortcode:

    <input?type=”checkbox”?id=”swpm-password-toggle-checkbox”?data-state=”password-hidden”>

    Explanation:

    Provide an accessible name for <code>input</code> elements with the label element whenever an on-screen label is present. The label element’s value is then explicitly associated with the relevant form field using the for and id attributes. Use of the label element provides an added benefit as it increases the target area that users can click to focus the form field. In certain instances, however, it is impractical or ‘undesirable’ to use an explicit label for a form field; this is largely driven by the fact that the value between the opening and closing label tags must, by definition, be a block of displayed text.

    When on-screen text is not available or can not programmatically be contained in a label (such as when a field is placed in a data table with a column label and a row label) – authors can use another method to provide an accessible name such as by using the title, aria-label, or aria-labelledby attribute to provide the label. The aria-labelledby attribute must contain one or more IDs of elements that label the form field. The <code>aria-label</code> attribute should only be used when on-screen labels can not be used. Authors should place the string that labels the form field in the aria-label attribute.

    Since this is core to your plugin – can you advise how to correct this?

    Best,

    Michael

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support mbrsolution

    (@mbrsolution)

    Hi, are you currently using the Form Builder addon?

    Kind regards.

    Thread Starter Michael

    (@whispardesign)

    No addon – just the default login screen https://joannek1.sg-host.com/panel-login/

    Plugin Support mbrsolution

    (@mbrsolution)

    Thank you for providing more information. I have submitted a message to the developers to investigate further your findings.

    Kind regards.

    Plugin Author wp.insider

    (@wpinsider-1)

    Thank you. I have made some changes to the login form for this which should be helpful. It will be released in a few days.

    In the meantime, you can download an updated copy of the plugin from our site and try it. Let me know if this makes any difference:

    https://simple-membership-plugin.com/wp-content/uploads/simple-membership.zip

    If you want to try this update, first delete the currently active copy of the plugin then upload and activate the above mentioned one. You won’t lose any data (members, payments, buttons, settings etc.) in the process so it is safe to do this.

    Thread Starter Michael

    (@whispardesign)

    Thanks for taking care of this so quickly – will keep you posted on rescan results.

    Plugin Support mbrsolution

    (@mbrsolution)

    @whispardesign, have you tested the new version? Can you let us know if your issue is now resolved?

    Thank you.

    Thread Starter Michael

    (@whispardesign)

    Still working on testing – will keep you posted.

    On another issue – we have pages set to member only but the advanced custom fields still show – only the “text” content is not available for viewing.

    Example

    Plugin Support mbrsolution

    (@mbrsolution)

    @whispardesign, this could be related to the theme in your site. Please check one of WordPress default themes like Twenty Twenty-Two. Let me know what happens.

    Thank you.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘ADA Compliance – Login Buttons’ is closed to new replies.