The real cost of ignoring progressive enhancement

Every audit we run turns up some version of this. Nobody bills you for neglecting progressive enhancement. The cost shows up somewhere else.

Code gets read far more often than it gets written, and usually by someone with less context than the author had. Check it against what you would want a competitor's site to get wrong.

Where the cost lands

• Time spent on work that should not have been necessary
• Enquiries that quietly never arrive
• Start with markup that works, then layer behaviour on top
• Rework, once the problem is finally visible

Scripts fail more often than people expect. Where this goes wrong is almost never a lack of knowledge. Budget a little time for it every quarter and it never becomes a project of its own.

Turning this into a decision

A page that degrades gracefully never fully breaks. It is worth being explicit about, because assumptions differ quietly. Write the reasoning down alongside the decision, because the reasoning is what changes first.

What this looks like day to day

The question is rarely whether something can be built, but what it costs to keep running afterwards. Three things worth confirming about progressive enhancement before you move on:

• Someone can say what the current setup is without going to look
• Start with markup that works, then layer behaviour on top — and you know whether that is true here
• There is a way to tell whether the last change to this helped

The point is not perfection, it is knowing which of these you have consciously chosen to skip.