When the Form Doesn't Fit

The Barrier Is in the Design

A form that requires a phone number, with no alternative, excludes deaf people who do not use voice telephony. A field limited to thirty characters cannot hold the double-barrelled surnames common in Welsh and Irish communities, nor hyphenated names from many other traditions — and it may also fail to hold the full legal name of a disabled person, such as one with a long string of given names or a name containing characters the form rejects. A date-of-birth field that crashes if a screen reader user tabs through it differently from a mouse user blocks the application entirely. None of these problems involve a human operative making a discriminatory choice. The discrimination is baked into the form before anyone opens it.

Time limits are among the most reliably harmful design choices. A session that expires after fifteen minutes may be adequate for a non-disabled user completing a short form without interruption. For someone who uses augmentative and alternative communication, takes longer to process text, or needs to stop and rest, fifteen minutes is the form's decision that the application is over. The same logic applies to CAPTCHA: the standard distorted-text and image-recognition variants are routinely inaccessible to blind users and people with certain cognitive profiles, and audio alternatives are frequently unintelligible even to people without a hearing impairment.

Paper forms carry their own structural failures. Fixed boxes that cannot expand, instructions that assume the applicant can write at speed, a return deadline that requires a printer and a postbox, a signature requirement that cannot be met by someone without fine motor control — each of these is a point of exclusion embedded in the administrative design. The form is not neutral; it encodes assumptions about the bodies and circumstances of its users.

Required-field logic is the final common mechanism. A form that will not submit without a middle name, a National Insurance number acquired through a particular route, or a contact address that conforms to a rigid postcode lookup excludes people whose lives do not match the model. Every unnecessary required field is a policy choice that narrows who can complete the process.

Fixing this is partly technical — testing with real users who have a range of access needs — and partly editorial: asking, at the point of commissioning, what this field is actually for.