liveBook · Manning

Technical debt

As explained in Architecting Accessibility

Technical debt is the accumulated future cost created by choosing incomplete, inferior, or deferred technical solutions.

Accessibility-related technical debt builds when teams defer accessibility work to save time. Inaccessible patterns can become embedded in code, templates, frameworks, and team workflows, making remediation slower and more expensive. Include accessibility requirements early, so product decisions reduce barriers instead of adding them. section 1.2

How Architecting Accessibility covers it

How deep it goes
Traces costs from inaccessible patterns in code, templates, and frameworks to embedded workflows and more expensive remediation.
Examples
Points to inaccessible patterns in code, templates, frameworks, habits, procurement practices, and development workflows.
What you can do after
Evaluate how delaying accessibility work increases remediation effort and cost, then raise accessibility during requirements and design.
How it connects
Connects technical debt with accessibility requirements, product planning, remediation, and usability.

Also explained in

Compare how 16 books explain technical debt →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.