Viewing 8 replies - 1 through 8 (of 8 total)
  • This is because input type email isn’t in HTML4 specification. It’s a specification from HTML5, but the validator work’s on HTML4 standard and will show the error when validating forms with input type email.

    Using input type=”email” for email addresses is better than using type=”text” because then users of (iPad/iPhone, Android) will have the correct keyboard come up for entering an email address. The keyboard will have the @ symbol and .com on it.

    There will be no problems with any older browsers, they all treat type=”email” as type=”text” anyway.

    So there is an advantage to using input type=”email” for email addresses, Mobile Accessibility. The only disadvantage is the validator. Sometimes the validator falls on the wrong side of these kind of issues.

    Thread Starter drunkfox

    (@drunkfox)

    Thans a lot for your quik reply!
    Ciao.

    I don’t want to hijack this topic, but I don’t like the fact that the captcha images are the no-go validating point. Why aren’t there any widths and heights on any of those images?It takes only a few seconds to implement this.
    After every update I need to go and change the plugin files of every site to get them validated again… I’d really love to see this solved.

    siteoptimo,

    Can I see a URL to your form please?

    Hi Mike,

    The URL doesn’t matter, I was to quick with my question in this topic (sorry).
    It isn’t a w3c validation problem, but an accessibility issue.
    Every image should have fixed dimensions with width and height attributes to be completely accessible. I’d want the plugin to output images with those attributes.
    I think it makes more sense, no?

    Kind regards and thank you for your answer.

    If you are determined to validate with the current validators, I did notice an easy work around; just use a text field with label “Email” and appropriate regex (an easy google). Unless Mike can see an issue I think that works.

    siteoptimo, this is fixed for the next update version.

    That’s great. Great work Mike. Kudos for making fs contact form the best contact form available.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘[Plugin: Fast Secure Contact Form] W3C validation error’ is closed to new replies.