• Resolved Nick

    (@nickbits)


    Hi,

    Using the datepicker I find that it, so far, is the only field that fails WCAG 2.1 AA. So I have several forms, on one I have inserted a datepicker field. The field displays fine but testing the form against WCAG it comes back with two errors:

    • WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.InputText.Name
    • WCAG2AA.Principle1.Guideline1_3.1_3_1.F68

    This should be fairly simple fix so looking at the code I see that datepicker is actually using two input fields:

    <div class="pikaday__container">
    <input id="nf-field-39" name="nf-field-39" aria-invalid="false" aria-describedby="nf-error-39" class="ninja-forms-field nf-element datepicker" aria-labelledby="nf-label-field-39" required="" type="hidden" value="">
    <input type="text" class="pikaday__display pikaday__display--pikaday ninja-forms-field nf-element datepicker" placeholder="">
    </div>

    One is perfectly valid but the second isn’t and is not shown in the template file. Can this be fixed?

    • This topic was modified 4 years, 8 months ago by Nick. Reason: formatting
Viewing 1 replies (of 1 total)
  • Plugin Contributor Justin McElhaney

    (@jmcelhaney)

    We have plans to update the datepicker that Ninja Forms uses in the near future. Accessibility issue is one of the reasons why.

Viewing 1 replies (of 1 total)
  • The topic ‘WCAG / accessibility on Datepicker’ is closed to new replies.