Skip to content
ENالعربية

R073: Identity fields missing autocomplete tokens

Name, email, phone and address inputs, recognised by their name, id or label in English or Arabic, that lack autocomplete, so Arabic users retype details the browser could fill.

The check

Id
R073
Category
Forms
Default severity
low

When it fires

  1. lowmedium confidence

    A visible text, email or phone input with no autocomplete has a name, id or label saying it holds a name, email, phone, mobile, address or city, in English or in Arabic (اسم، بريد، هاتف، جوال، عنوان، مدينة). The match is a word pattern, so it reports at medium confidence.

    Fix: Add the matching autocomplete token, such as autocomplete="email".

What it leaves alone

Fields that already carry any autocomplete value, including off, and input types other than text, email and phone. Up to five per page.

Broken, then fixed

before.html
<input type="email" name="email">
after.html
<input type="email" name="email" autocomplete="email">

Check it by hand

Run [...document.querySelectorAll('input:not([autocomplete])')].map((i) => [i.type, i.name, i.id]) in the DevTools console to list the inputs with no autocomplete token.

What the report shows you

Each R073 finding carries the fields below that apply to it, so you can see why it fired without rerunning the scan.

name
The input's name.
id
The input's id.
label
The text of its label.
type
The input's type: text, email or tel.

Components that pass it by construction

These Ritla UI components satisfy R073 by how they are built. Used as documented, they do not bring this defect onto your page.

More forms checks

Does your page trip R073?

Paste a URL. Ritla renders the page on desktop, tablet and mobile, runs every check, and shows the top issues with screenshot evidence.

Scan a page freeBrowse the checks