Skip to main content
📚 Cite this page

AMA
Weru Lawrence. (Iterate) to Address Shortcomings. The ENABLE Model website. Published 2025. Accessed 2026-05-16. https://enablemodel.com/docs/builder-side/iteration

APA
Weru, L. (2025). (Iterate) to Address Shortcomings. The ENABLE Model. https://enablemodel.com/docs/builder-side/iteration

MLA
Weru, Lawrence. "(Iterate) to Address Shortcomings." The ENABLE Model, 2025, https://enablemodel.com/docs/builder-side/iteration.

Chicago
Weru, Lawrence. "(Iterate) to Address Shortcomings." The ENABLE Model. 2025. https://enablemodel.com/docs/builder-side/iteration.

BibTeX

@misc{enable2025iteration,
              author = {Weru, Lawrence},
              title = {(Iterate) to Address Shortcomings},
              year = {2025},
              url = {https://enablemodel.com/docs/builder-side/iteration},
              note = {The ENABLE Model}
            }

Iterate to Address Shortcomings

Iteration is the process of making continuous improvements based on testing, feedback, and evaluation. In the context of accessibility, iteration means revisiting and refining digital systems, policies, or environments to resolve accessibility shortcomings discovered during development, QA, or after real-world use.

Role in the ENABLE Model​

As the last product-change step in the builder-side phase, iteration closes the feedback loop. Instead of a one-time task, it ensures that accessibility is a recurring obligation. Without iteration, accessibility flaws identified earlier may persist unaddressed, limiting equity for end-users.

While iteration can occur post-launch as new versions of a product, service or other artifact are released, anything implemented by builders (developers, designers, institutions) even after initial launch is considered part of builder-side as long as it's part of the product's official development lifecycle, not a user-side workaround.

Iteration is what distinguishes a builder who continues to care from one who abandons the user after launch. It functions inside builder-side because its intent is systemic correction.

iteration vs stopgaps

Unlike support channels, iteration changes the product or service itself. Unlike stopgaps, iteration addresses shortcomings at the source, not the symptoms.

Why Iteration Matters​

No product or policy is perfect at launch. Real accessibility gaps are often revealed only through diverse user interaction and long-term observation. Iteration ensures that accessibility is not postponed or deprioritized when flaws are found -- it institutionalizes the act of fixing them. This act separates performative inclusion from meaningful access.

Grounding​

ADA settlements such as Peapod and H&R Block required revised bug-fix procedures, testing, reporting, and ongoing oversight, making iteration a legal obligation in remediation contexts.12 The DOJ's 2024 web rule creates continuing compliance duties for state and local government web content and mobile apps.3 The European Accessibility Act's transitional measures run through 28 June 2030 for certain pre-existing services and products.4

WCAG's own publication history models iterative improvement at the standards level: 2.0 (2008), 2.1 (2018), and 2.2 (2023).5

WebAIM's 2026 analysis found that accessibility errors per page increased 10.1% from 2025, with pages growing more complex and accumulating more detected failures.6 That regression illustrates what happens when accessibility work does not continue after launch.6

Aisha Malik reported that Google kept shipping new Android and Chrome accessibility updates after launch, treating accessibility as ongoing product work rather than a one-time release event.7

In the news

Richer alt text in Word and PowerPoint, powered by generative AI (November 18, 2025)
-- shireensalma, Microsoft 365 Blog

  • Microsoft announces that they have iterated to improve alt text in Word and Powerpoint. They also request that end-users submit feedback to creators.

Chrome 126 Adds Direct UI Automation Support for Accessibility (2024)
-- Google Cloud Blog

  • Google iterated on Chrome's accessibility architecture to directly support Windows UI Automation framework, improving compatibility with Narrator, Magnifier, and Voice Access. This systemic fix -- rather than expecting users to find workarounds -- reduced memory usage and processing overhead for assistive technology users.

Xbox Adaptive Controller Update: Expanded USB Support (August 2024)
-- Xbox Wire

  • Microsoft announced that each USB port on the Xbox Adaptive Controller now supports up to 12 buttons, a second stick, and hat switch -- responding to community feedback about connection limitations. This iteration demonstrates how ongoing collaboration with the Gaming & Disability Community leads to meaningful improvements, not just launch-day accessibility.

Examples​

  • Updating AI models that misrecognize non-standard speech after real-world failures.
  • Improving color contrast based on user testing from people with low vision.
  • Adding keyboard support to features previously built only for mouse users.
  • Refining caption accuracy or timing after feedback from deaf users.

Care sounds like​

"How can our speech recognition AI do a better job with people who stutter? If it can't, can we provide an accessible alternative?"
"We got feedback from a blind user who couldn't complete the checkout process -- we're deploying a fix in the next sprint."
"We missed this WCAG criterion during development; it's going into the next release."

Neglect sounds like​

"Well, it passed our automated tests -- we don't have time to revisit it now."
"We already launched; we can't prioritize that kind of fix at this point."
"If users had issues, they should've reported them earlier."

Real-world Scenario​

Larry tries to verify a credit card transaction via phone, but the speech recognition AI hangs up after failing to understand his stutter. He is locked out of his account. Had the development team iterated on past reports from people who stutter -- or even built an accessible alternative flow -- the lockout could have been avoided. Iteration isn't just about polish; it's about restoring access.

Footnotes​

  1. U.S. Department of Justice: Peapod Settlement Agreement ↩

  2. U.S. Department of Justice: H&R Block Consent Decree ↩

  3. ADA.gov: Fact Sheet - New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments ↩

  4. EUR-Lex: Directive (EU) 2019/882, Article 32 ↩

  5. W3C: WCAG 2 Overview ↩

  6. WebAIM: The WebAIM Million - The 2026 report on the accessibility of the top 1,000,000 home pages ↩ ↩2

  7. Aisha Malik, TechCrunch, Google rolls out new AI and accessibility features to Android and Chrome ↩


Manifestations

The following manifestations are associated with this ENABLE Model location:


Edited by Lawrence Weru S.M. (Harvard)

Disclaimer

The ENABLE Model draws on the principles of anthropology and the practice of journalism to create a public ethnography of accessibility, documenting how people intervene or compensate for accessibility breakdowns in the real world. Inclusion here does not imply endorsement. It chronicles observed use -- how a tool, organization, or strategy is actually used -- rather than how it is marketed. References, when provided, are for verification and transparency.


📚 Cite this page

AMA
Weru Lawrence. (Iterate) to Address Shortcomings. The ENABLE Model website. Published 2025. Accessed 2026-05-16. https://enablemodel.com/docs/builder-side/iteration

APA
Weru, L. (2025). (Iterate) to Address Shortcomings. The ENABLE Model. https://enablemodel.com/docs/builder-side/iteration

MLA
Weru, Lawrence. "(Iterate) to Address Shortcomings." The ENABLE Model, 2025, https://enablemodel.com/docs/builder-side/iteration.

Chicago
Weru, Lawrence. "(Iterate) to Address Shortcomings." The ENABLE Model. 2025. https://enablemodel.com/docs/builder-side/iteration.

BibTeX

@misc{enable2025iteration,
              author = {Weru, Lawrence},
              title = {(Iterate) to Address Shortcomings},
              year = {2025},
              url = {https://enablemodel.com/docs/builder-side/iteration},
              note = {The ENABLE Model}
            }