All 141 tools / International and inclusive design
Find name inputs that reject real names: short maxlength, A to Z patterns and forced first and last fields
Name field checkFreeFor developers and designers
25/day
free runs a day, no sign-in.
Before: what you give it
The example input, as typed in. You paste text, CSS, markup or notes.
<form><label>First name <input name="first_name" maxlength="20" pattern="[A-Za-z ]+" required></label><label>Last name <input name="last_name" minlength="3" required></label><select name="title" required><option>Mr</option><option>Ms</option></select></form><script>if(!/^[a-zA-Z]+$/.test(v)) err()</script>
After: what comes back
The first lines of a real run on that input. Nothing here is edited by hand.
NAME FIELD CHECK
Detected: 1 first/given field, 1 last/family field, 0 full-name fields, 0 middle-name fields, 1 title/gender field
Findings: 3 high, 3 medium, 3 low, 0 info
[HIGH] Names: maxlength 20 on <input>
Real names regularly run past 30 to 40 characters, especially with multiple family names or long transliterations.
Seen in: <input>
Fix: Allow at least 100 characters (convention) and never truncate silently.
[HIGH] Names: pattern on <input> excludes non-ASCII letters
Pattern [A-Za-z ]+ rejects accents, apostrophes, hyphens or non-Latin scripts (José, O'Brien, 张, محمد).
Seen in: <input>
Fix: Do not validate names by character class. If you must, accept letters from any script (\p{L}), marks, spaces, apostrophes, hyphens and periods.
... full output on the tool page
What you get
Detected name fields and findings on length limits, patterns, required fields and autocomplete tokens
What it cannot do
Reads pasted markup and script only; server rules and database columns are not visible.
Who it is for
- Developers
- Designers
Free and Pro
| Free | 25 runs a day per IP address, up to 100,000 characters a run. |
|---|---|
| Pro | No daily limit, 300 requests a minute, up to 200,000 characters a run. |
Use it from your assistant
The tool is called check_name_fields. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.
claude mcp add --transport http designers https://designers.allthepossibles.com/mcp
curl -X POST https://designers.allthepossibles.com/api/name-field-check -H 'content-type: application/json' -d '{"markup":"<form><label>First name <input name=\"first_name\" maxlength=\"20\" pattern=\"[A-Za-z ]+\" required></label><label>Last name <input name=\"last_name\" minlength=\"3\" required></label><select name=\"title\" required><option>Mr</option><option>Ms</option></select></form><script>if(!/^[a-zA-Z]+$/.test(v)) err()</script>"}'
Try it here
The form starts with the same example input, so you can run it first and then swap in your own.
More in international and inclusive design
- Localisation stress test
Predict how far UI strings grow in eight languages and flag the ones that overflow their space.
- Localisation readiness
Check source strings for translation problems and project how long each will be in other languages
- RTL readiness
Find the left and right CSS that will break in Arabic or Hebrew, with the logical property to use instead
- Font coverage check
Find which scripts your text needs and which listed fonts cover them, with a Noto family for each gap
- Date and number format review
Find dates, numbers, currency and units in UI text that read differently in other locales
- Text expansion planner
Plan how much longer each UI string gets in other languages and flag the ones that overflow