What does this mean?

To comply with WCAG 2.1, fields must identify what their purpose is programmatically. If done correctly, this allows browsers to help users fill in forms with known information, such as their name and email address.

This is accomplished via the autocomplete attribute, which should be set to a supported value wherever appropriate, e.g.

<label for="name">First Name</label>
<input id="name" type="text" autocomplete="given-name">

For fields where autocomplete is not appropriate, e.g. due to security, or the field not matching the specification, the specific field should be ignored.

See how to use HTML 5.2 attributes for more information.

91.6% done

How close this website is to fixing this issue.

HTML Found on page Issues
<input data-drupal-selector="edit-title" type="text" id="edit-title" name="title" value size="30" maxlength="128" class="form-text"> 3
<input id="fieldyusli" name="cm-f-yusli" aria-label="Organisation / University" type="text" maxlength="200"> 1
<input id="fieldName" name="cm-name" aria-label="Name" type="text" maxlength="200"> 1
<input data-drupal-selector="edit-last-name" type="text" id="edit-last-name" name="last_name" value size="30" maxlength="128" class="form-text"> 1
<input data-drupal-selector="edit-title" type="text" id="edit-title--2" name="title" value size="30" maxlength="128" class="form-text"> 1
<input id="fieldEmail" name="cm-djvht-djvht" aria-label="Email" class="js-cm-email-input" required type="email" maxlength="200"> 1
8 distinct issues were found in the sample of 125 web pages.
More results from London School of Hygiene & Tropical Medicine