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
Technical debt
Technical debt is the accumulated future cost created by choosing incomplete, inferior, or deferred technical solutions.
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
-
Software Architecture Decision-MakingTechnical debt is the future cost or limitation created by expedient technical choices or by allowing design constraints to accumulate.
-
Vibe EngineeringThe accumulated cost and risk created when expedient software decisions or deferred maintenance make future development and operation more difficult.
-
Lead Developer Career GuideThe future cost of maintaining or changing software resulting from expedient choices or unresolved technical issues.
-
Architecture Modernization: Socio-technical alignment of software, strategy, and structureTechnical debt is the future cost and constraint created by choosing expedient implementation or maintenance decisions over more durable solutions.
-
Think Like a Software Engineering ManagerTechnical debt is the accumulated future cost of expedient technical decisions that make software harder to change or maintain.
-
Grokking Software ArchitectureTechnical debt is the future cost of short-term software design or implementation compromises made in favor of speed over quality and maintainability.
-
Delivering Machine Learning Projects: From design to deploymentTechnical debt is the future cost created by expedient technical decisions that increase maintenance, correction, or evolution effort.
-
Graph Neural Networks in ActionTechnical debt is the future cost of design or implementation decisions that require later rework, workarounds, or replacement.
-
"Looks Good to Me"The future maintenance and remediation cost created by accepting an expedient or suboptimal software decision.
-
Think Like a CTOTechnical debt is the accumulated cost of choosing short-term technical solutions that make future software maintenance or change more difficult.
-
Build High Value Software SystemsTechnical debt is the future cost created by implementation choices that make a system harder, riskier, or more expensive to change or operate.
-
Collaborative Software Design: How to facilitate domain modeling decisionsThe future cost of deliberately choosing a less-than-ideal software design or implementation in order to deliver value sooner.
-
The Art of CodeTechnical debt is the future cost of maintenance and change created by expedient technical choices or unresolved implementation deficiencies.
-
PostgreSQL Mistakes and How to Avoid ThemTechnical debt is the accumulated cost of delaying or choosing expedient implementations that make future changes or maintenance more difficult.
-
Designing AI SystemsTechnical debt is the future cost of maintaining or changing a system because expedient implementation choices created structural limitations or rework.
Compare how 16 books explain technical debt →
Related concepts
- refactoringaddressed by · Refactoring is the disciplined restructuring of existing software to improve its internal qualities while preserving its externally observable behavior.
- Boy Scout Ruleaddressed by · The Boy Scout Rule is a software maintenance practice of leaving code cleaner than it was found by making small improvements while changing it.
- pair programmingaddressed by · Pair programming is a software-development practice in which two programmers collaborate on the same programming task or code, often sharing coding and review responsibilities.
- code duplicationproduced by · Code duplication is the presence of the same or substantially similar implementation logic in multiple locations within a software system.
- comprehension debtcontrasts with · Comprehension debt is the accumulated gap between the complexity of software and its maintainers’ understanding of its architecture, assumptions, and behavior.
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.















