Skip to main content

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 final step in the pre-launch phase, iteration closes the feedback loop. It ensures that accessibility is not a one-time task but 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 pre-launch 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 pre-launch because its intent is systemic correction. It addresses shortcomings at the source, not the symptoms, like stopgaps.

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.

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.