troubleshooting accessibility errors wcga 2.1

  • hi, doing some tests with mauve ++ I found these errors in the contact form:

    Criterion: 1.1.1 1.3.1 3.3.2 4.1.2 Tech: H44
    Using label elements to associate text labels with form controls.

    in these lines:

    <textarea cols="40" rows="10" class="wpcf7-form-control wpcf7-textarea" autocomplete="on" aria-invalid="false" name="textarea-970"></textarea>
    <input size="40" class="wpcf7-form-control wpcf7-text wpcf7-validates-as-required" autocomplete="name" aria-required="true" aria-invalid="false" value="" type="text" name="your-name">
    <input type="hidden" name="_wpcf7" value="10828">
<input type="hidden" name="_wpcf7_version" value="5.7.6">
<input type="hidden" name="_wpcf7_locale" value="it_IT">
<input type="hidden" name="_wpcf7_unit_tag" value="wpcf7-f10828-p10432-o1">
<input type="hidden" name="_wpcf7_container_post" value="10432">
<input type="hidden" name="_wpcf7_posted_data_hash" value="">

    Criterion: 1.3.1 4.1.2Tech: ARIA16
    Using aria-labelledby to provide a name for user interface controls

    in these lines:

    <input type="hidden" name="_wpcf7" value="10828">
<input type="hidden" name="_wpcf7_version" value="5.7.6">
<input type="hidden" name="_wpcf7_locale" value="it_IT">
<input type="hidden" name="_wpcf7_unit_tag" value="wpcf7-f10828-p10432-o1">
<input type="hidden" name="_wpcf7_container_post" value="10432">
<input type="hidden" name="_wpcf7_posted_data_hash" value="">

    is there any way to fix them too?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    Where can we see the website in question?

    Thread Starter 00lessio

    (@00lessio)

    this is the link of the page

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    See Editing form template

    What content do you have in the Form tab panel?

    Thread Starter 00lessio

    (@00lessio)

    hi, this is the content of the form.

    <label for="nome" class="w-48"> Il tuo nome e cognome
[text* text-716 id:nome placeholder "Nome e cognome"]</label>

<label for="email" class="w-48 pl"> La tua email
    [email* your-email autocomplete:email] </label>

<label for="testo-disservizio">Descrivi il disservizio 
[textarea textarea-970 autocomplete:on]</label>
[acceptance acceptance-496]Dichiaro di aver letto la <a href="/privacy-policy">privacy policy</a> e acconsento al trattamento dei miei dati in merito  alla segnalazione [/acceptance]



[submit "Invia"]

    In the name field I tried to insert the for attribute and the id, and from inspect I see it but from mauve ++ it’s like it’s not there

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    <label for="email" class="w-48 pl"> La tua email
    [email* your-email autocomplete:email] </label>

    The label element refers to email, but the email* form-tag has no id option.

    Likewise,

    <label for="testo-disservizio">Descrivi il disservizio [textarea textarea-970 autocomplete:on]</label>

    the textarea form-tag has no id option corresponding to <label for="testo-disservizio">.

    Other parts look good.

    See this FAQ for details > Can I add text labels to input fields?

    Thread Starter 00lessio

    (@00lessio)

    this partially solved my problem, now the first error is gone but this is still the case

    Criterion: 1.3.1 4.1.2Tech: ARIA16
    Using aria-labelledby to provide a name for user interface controls

    in these lines:

    <input type="hidden" name="_wpcf7" value="10828"> 
<input type="hidden" name="_wpcf7_version" value="5.7.6"> <input type="hidden" name="_wpcf7_locale" value="it_IT"> <input type="hidden" name="_wpcf7_unit_tag" value="wpcf7-f10828-p10432-o1">
<input type="hidden" name="_wpcf7_container_post" value="10432">
<input type="hidden" name="_wpcf7_posted_data_hash" value="">
    Plugin Author Takayuki Miyoshi

    (@takayukister)

    Those are hidden fields that are excluded from the DOM tree, so they never are “user interface controls” necessary to be labeled.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘troubleshooting accessibility errors wcga 2.1’ is closed to new replies.