Accessibility needs ONKEYPRESS handler

  • Really like your contact form plugin. But when I run a Compliance/Accessibility checker (SortSite Standard) on my site it has an issue with the code supplied by your short code. Specifically it states: All ONCLICK handlers should have an equivalent ONKEYPRESS handler.

    The code that is highlighted is:
    Refresh Image

    Would it be possible to add an onpress handler into this?

    Thanks in advance, Matt

    • This topic was modified 8 years, 2 months ago by Matthew Welch.
Viewing 15 replies - 1 through 15 (of 15 total)

  • Hi, thank you for your findings and sharing this with us. The plugin developer will investigate further your suggestion.

    Kind regards

    Thread Starter Matthew Welch

    (@matthew-welch)

    Thanks. I also got a “This LABEL refers to a non-existent control.”

    “This happens when the FOR attribute doesn’t exactly match a control ID, or targets a control NAME instead of a control ID.”

    <label style=”text-align:left;” for=”fscf_field3_4″>Please select the presentation you are interested in. You may select more than one.<span style=”text-align:left;”>*</span></label>

    Does this mean there is no field “fscf_field3_4” that the label is referring to? Is this something we could have messed up creating the form? If, so how can it be fixed?

    Thanks again.

    Hi, can you share the URL with the contact form?

    Thread Starter Matthew Welch

    (@matthew-welch)

    https://ehsdhicap.govassist.org/community-education/request-a-presentation/

    The field that is causing this issue in your case is the following.

    Please select the presentation you are interested in. You may select more than one.*

    How did you add the above sentence? Can you also provide a screen capture.

    Thank you

    Thread Starter Matthew Welch

    (@matthew-welch)

    I will be able to contact the person who created the form next week. Not sure how to provide screen capture since I don’t see attachments here or ability to paste an image. But it would be the same as what you see from the url. (unless you are asking for something else).

    Thanks

    Hi, go to Plugins -> FS Contact Form -> Fields. How was the sentenced I mentioned above added in the Fields tab?

    Thank you

    Thread Starter Matthew Welch

    (@matthew-welch)

    From our person who did the edits
    “Ok, now I see what I did. That wasn’t one of the default fields, so I clicked the blue button on the right of the Fields tab that says Add New Field. Then it makes you type in the name you want for that field, so I put that sentence in as the field name.”

    Okay, then it makes sense your current issue. Please remove that field and your issue will be resolved. If that fixes your issue can you mark this support thread as resolved.

    Thank you

    Thread Starter Matthew Welch

    (@matthew-welch)

    Well, there is a need for that text to be displayed near the checkboxs. We are very new to your product. What is the proper way to do it?
    Thanks

    Hi, yes I understand what you mean. When you add a new field it has two extra areas for you to add some text or HTML.

    1. HTML before form field:
    2. HTML after form field:

    Use one of the above to add the text you mentioned.

    Kind regards

    • This reply was modified 8 years, 2 months ago by mbrsolution.
    Thread Starter Matthew Welch

    (@matthew-welch)

    Are you saying that the use of Field Type: checkbox-multiple should be avoided in the case? That I should remove that field and add separate new fields, one for each checkbox? And then for the first one add text in the HTML before form field:?

    Hope this makes sense.

    Also, this would be very much different from the original start of this thread. The accessibility checker wants an ONKEYPRESS handler whenever there is and ONCLICK event.

    Thank you.

    Hi, I am not really sure how to answer your question any further. The plugin developer will investigate further your issue.

    Kind regards

    Thread Starter Matthew Welch

    (@matthew-welch)

    Any update on this?

    Adding both onclick AND onkeypress is really not needed:
    https://www.w3.org/TR/WCAG20-TECHS/SCR20.html

    Although onclick is in principle a mouse event handler, most HTML and XHTML user agents also process this event when a native HTML control (e.g. a button or a link) is activated, regardless of whether it was activated with the mouse or the keyboard. In practice, therefore, it is not necessary to duplicate this event when adding handlers to natively focusable HTML elements.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Accessibility needs ONKEYPRESS handler’ is closed to new replies.