Skip to content
Sanding Space
Sanding Space
Introduction
  • Principles
    • Sand the Back
    • Details Compound (coming soon)
    • Taste Is Trainable (coming soon)
    • Prototype in the Material (coming soon)
    • Every State Is Designed (coming soon)
    • Speed Is a Feeling (coming soon)
    • Honor the Platform (coming soon)
    • Know When to Stop (coming soon)
  • Foundations
    • Spacing Is a Scale (coming soon)
    • Concentric Corners (coming soon)
    • Optical Alignment (coming soon)
    • A Type Scale (coming soon)
    • Line Length and Leading (coming soon)
    • Perceptual Color (coming soon)
    • Contrast Is Not a Checkbox (coming soon)
    • Depth in Light and Dark (coming soon)
    • Icons Match the Text (coming soon)
  • Interaction
    • Button Press (coming soon)
    • Hover Is a Hint (coming soon)
    • The Safe Triangle (coming soon)
    • Hit Targets Are Bigger Than They Look (coming soon)
    • Focus Is a State Too (coming soon)
    • The Keyboard Is an Input (coming soon)
    • Inputs That Don't Fight You (coming soon)
    • Disabled Buttons Explain Nothing (coming soon)
    • Undo Beats Confirm (coming soon)
  • Motion
    • Motion Has a Job (coming soon)
    • Timing: Duration and Easing (coming soon)
    • Enter and Exit Aren't Mirrors (coming soon)
    • Grow From the Source (coming soon)
    • Springs Can Be Interrupted (coming soon)
    • Things Don't Teleport (coming soon)
    • Edges Should Give (coming soon)
    • Reduced Motion Isn't No Motion (coming soon)
    • Animate the Cheap Properties (coming soon)
  • Components
    • Toast (coming soon)
    • Dropdown Menu (coming soon)
    • Tabs (coming soon)
    • Drawer (coming soon)
  • Systems
    • Tokens Have Layers (coming soon)
    • Theming Without Rewriting (coming soon)
    • Components Are APIs (coming soon)
    • Composition Over Configuration (coming soon)
    • Variants, Not Overrides (coming soon)
    • Density Is a Mode (coming soon)
    • Behavior and Style Are Separate (coming soon)
    • Catch It Before It Ships (coming soon)
  • Product
    • Defaults Are Decisions (coming soon)
    • Empty States Are Onboarding (coming soon)
    • Progressive Disclosure (coming soon)
    • Write the Interface (coming soon)
    • Make the Common Path Fast (coming soon)
    • Never Lose Work (coming soon)
    • The URL Is State (coming soon)
    • Ship Behind a Flag (coming soon)
ResourcesAbout
Sanding Space
Introduction
  • Principles

    How should I think?

    • Sand the Back
    • Details Compound (coming soon)
    • Taste Is Trainable (coming soon)
    • Prototype in the Material (coming soon)
    • Every State Is Designed (coming soon)
    • Speed Is a Feeling (coming soon)
    • Honor the Platform (coming soon)
    • Know When to Stop (coming soon)
  • Foundations
    • Spacing Is a Scale (coming soon)
    • Concentric Corners (coming soon)
    • Optical Alignment (coming soon)
    • A Type Scale (coming soon)
    • Line Length and Leading (coming soon)
    • Perceptual Color (coming soon)
    • Contrast Is Not a Checkbox (coming soon)
    • Depth in Light and Dark (coming soon)
    • Icons Match the Text (coming soon)
  • Interaction
    • Button Press (coming soon)
    • Hover Is a Hint (coming soon)
    • The Safe Triangle (coming soon)
    • Hit Targets Are Bigger Than They Look (coming soon)
    • Focus Is a State Too (coming soon)
    • The Keyboard Is an Input (coming soon)
    • Inputs That Don't Fight You (coming soon)
    • Disabled Buttons Explain Nothing (coming soon)
    • Undo Beats Confirm (coming soon)
  • Motion
    • Motion Has a Job (coming soon)
    • Timing: Duration and Easing (coming soon)
    • Enter and Exit Aren't Mirrors (coming soon)
    • Grow From the Source (coming soon)
    • Springs Can Be Interrupted (coming soon)
    • Things Don't Teleport (coming soon)
    • Edges Should Give (coming soon)
    • Reduced Motion Isn't No Motion (coming soon)
    • Animate the Cheap Properties (coming soon)
  • Components
    • Toast (coming soon)
    • Dropdown Menu (coming soon)
    • Tabs (coming soon)
    • Drawer (coming soon)
  • Systems
    • Tokens Have Layers (coming soon)
    • Theming Without Rewriting (coming soon)
    • Components Are APIs (coming soon)
    • Composition Over Configuration (coming soon)
    • Variants, Not Overrides (coming soon)
    • Density Is a Mode (coming soon)
    • Behavior and Style Are Separate (coming soon)
    • Catch It Before It Ships (coming soon)
  • Product
    • Defaults Are Decisions (coming soon)
    • Empty States Are Onboarding (coming soon)
    • Progressive Disclosure (coming soon)
    • Write the Interface (coming soon)
    • Make the Common Path Fast (coming soon)
    • Never Lose Work (coming soon)
    • The URL Is State (coming soon)
    • Ship Behind a Flag (coming soon)
ResourcesAbout
Principles

Sand the Back

Why the parts nobody asks for are the parts people feel.

Before you read on, fill in both forms above. Use your keyboard if you can. Click a label. Paste a phone number with spaces in it. Press Enter instead of reaching for the button. Submit one empty, then fix it.

From the front they're the same form. Same fields, same colors, same spacing. A screenshot of either one would pass a design review. But one of them fights you and the other gets out of the way, and you probably felt which was which before you could say why.

There is no wall

#

The cabinet maker sands a side that will face a wall for the rest of its life. Interfaces don't have a wall. Every side of what we build faces somebody. Turn the one below around and see for yourself.

The person who never touches a mouse lives on the back of your form. So does the person using a screen reader, the one on a train with a single bar of signal, the one who pasted their details from a notes app, the one who came back to the page and expected it to remember them. For them it isn't the back. It's the only side there is.

That's why I don't think of this work as polish. Polish sounds optional. The back of an interface is just the part your team doesn't look at, and someone else lives there every day.

Why people feel it

#

Most people won't notice that clicking a label focuses its input. They'll notice when it doesn't, and even then they won't report it. They'll just trust the product a little less.

I think that's the real cost. Every interface is evidence about the people who made it. When a form throws away what you typed because one field was wrong, you don't only lose the text. You learn something about the team behind it, and you start to wonder what else they didn't check. If they were careless here, where I can see it, what about the places I can't see, where my data, my money and my messages are?

Try finishing the small task below. It works. Notice how you feel about it anyway.

The sanded version earns the opposite. Nothing in it is impressive on its own. It simply never asks you to work around it, and after a while you stop bracing. That's the feeling people describe as "it just works", and it's built almost entirely out of things nobody asked for.

Finding the back

#

The hard part isn't the sanding. It's finding the back, because by definition it's the side you don't look at.

A few habits help me turn the cabinet around. I put the mouse away and use what I built with only a keyboard. I turn on the screen reader, even if I use it badly. I throttle the network and reload. I paste things instead of typing them. I go back, refresh, open a second tab. I make it fail on purpose and read what it tells me. Almost every time, there's a rough edge waiting.

None of this needs its own project or a ticket. It's ten minutes before you call something done.

Usage

#

The back is mostly made of things the platform already gives you, so most of the work is not throwing them away. Four places to start, in React and Tailwind.

A form that works without a mouse. A real <form>, so Enter submits. A real <label>, so clicking it focuses the field. Field types that bring up the right keyboard and let the browser fill them in. An error that says how to fix it, sits next to its field, and never erases what was typed.

TypeScript
<form noValidate onSubmit={submit} className="flex flex-col gap-3">
  <label htmlFor="email" className="text-sm font-medium">Email</label>
  <input
    id="email"
    name="email"
    type="email"
    autoComplete="email"
    value={email}
    onChange={(e) => setEmail(e.target.value)}
    aria-invalid={error ? true : undefined}
    aria-describedby={error ? "email-error" : undefined}
    className="h-10 rounded-lg border px-3 aria-invalid:border-red-500"
  />
  {error && (
    <p id="email-error" className="text-xs text-red-500">
      Enter an email like ana@example.com.
    </p>
  )}
  <button type="submit" className="h-10 rounded-lg bg-black text-white">
    Sign up
  </button>
</form>

On submit, move focus to the first field that failed, and leave every value where it was.

Accept what people paste. People paste phone numbers with spaces, dashes and brackets. Clean the value up instead of rejecting it.

TypeScript
const digits = phone.replace(/[^\d+]/g, "");
const valid = /^\+?\d{7,15}$/.test(digits);
TypeScript
<input
  type="tel"
  inputMode="tel"
  autoComplete="tel"
  value={phone}
  onChange={(e) => setPhone(e.target.value)}
/>

A button you can feel and find. A visible focus ring for the keyboard, a 44px target for a thumb, a small press for the hand. Keep the button's label while it works, so the button doesn't change size and screen readers keep its name.

TypeScript
<button
  type="submit"
  disabled={pending}
  className="inline-flex h-10 items-center gap-2 rounded-lg px-4 outline-none
    focus-visible:ring-2 focus-visible:ring-offset-2
    pointer-coarse:min-h-11 active:scale-[0.97] motion-reduce:active:scale-100
    disabled:opacity-60"
>
  Sign up
  {pending && <Spinner aria-hidden className="size-4 animate-spin" />}
</button>

Remember what they typed. Coming back to the page, refreshing, or a failed request shouldn't cost anyone their draft.

TypeScript
function useDraft(key: string) {
  const [value, setValue] = useState(() => sessionStorage.getItem(key) ?? "");
  useEffect(() => sessionStorage.setItem(key, value), [key, value]);
  return [value, setValue] as const;
}

Then do the ten minutes from Finding the back: put the mouse away, turn on the screen reader, throttle the network, paste, go back, make it fail.

Do it anyway

#

Nobody will thank you for the label that focuses its input. There's no metric for the error message that kept what someone typed. You do the work, and the best outcome is that nobody ever thinks about it.

Do it anyway. Partly because someone is on the other side of it. And partly for the same reason the cabinet maker does: you'll know. The standard you keep in the places nobody checks is the standard you actually have.

Resources

#
  • Web forms - learning forms from the basics (opens in a new tab)
  • Accessibility as craft - Interfaces is a design engineering magazine about building great interfaces that covers topics such as animation, typography, layout and color. (opens in a new tab)
  • Web Interface Guidelines - a non-exhaustive list of details that make a good (web) interface. (opens in a new tab)

Field notes

6 min read

A screen reader says: “button”

24px

Change your display name, then turn on email notifications. Cuts 0

Settings

RoughSanded
Pick a habit below, then sign up.Edges found 0/6

You left the page…

Field notes

One essay a week. No spam.

Habits