FAILURE MAP

Understand the failure.
Verify the repair.

Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.

Explore the cases ↓How results are verified ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

WHAT THE ARCHIVE CONTAINS

100840 executable cases. 20168 are open.

Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.

The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗

A RECORD OF WHAT WENT WRONG

Browse the archive / 100840

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-8401

Tree keyboard expansion: Collapse-all leaves unrelated expanded branches open · case 01

Collapse-all leaves unrelated expanded branches open.

Tree accessibility● Open access↗
FA-8402

Tree keyboard expansion: Collapse-all leaves unrelated expanded branches open · case 02

Collapse-all leaves unrelated expanded branches open.

Tree accessibility◈ Members↗
FA-8403

Tree keyboard expansion: Collapse-all leaves unrelated expanded branches open · case 03

Collapse-all leaves unrelated expanded branches open.

Tree accessibility◈ Members↗
FA-8404

Tree keyboard expansion: Collapse-all leaves unrelated expanded branches open · case 04

Collapse-all leaves unrelated expanded branches open.

Tree accessibility◈ Members↗
FA-8405

Tree keyboard expansion: Collapse-all leaves unrelated expanded branches open · case 05

Collapse-all leaves unrelated expanded branches open.

Tree accessibility◈ Members↗
FA-8406

Live-region announcement scheduling: Repeated identical status changes are queued again · case 01

Repeated identical status changes are queued again.

Assistive announcements● Open access↗
FA-8407

Live-region announcement scheduling: Repeated identical status changes are queued again · case 02

Repeated identical status changes are queued again.

Assistive announcements◈ Members↗
FA-8408

Live-region announcement scheduling: Repeated identical status changes are queued again · case 03

Repeated identical status changes are queued again.

Assistive announcements◈ Members↗
FA-8409

Live-region announcement scheduling: Repeated identical status changes are queued again · case 04

Repeated identical status changes are queued again.

Assistive announcements◈ Members↗
FA-8410

Live-region announcement scheduling: Repeated identical status changes are queued again · case 05

Repeated identical status changes are queued again.

Assistive announcements◈ Members↗
FA-8411

Live-region announcement scheduling: Disabled live regions still speak updates · case 01

Disabled live regions still speak updates.

Assistive announcements● Open access↗
FA-8412

Live-region announcement scheduling: Disabled live regions still speak updates · case 02

Disabled live regions still speak updates.

Assistive announcements◈ Members↗
FA-8413

Live-region announcement scheduling: Disabled live regions still speak updates · case 03

Disabled live regions still speak updates.

Assistive announcements◈ Members↗
FA-8414

Live-region announcement scheduling: Disabled live regions still speak updates · case 04

Disabled live regions still speak updates.

Assistive announcements◈ Members↗
FA-8415

Live-region announcement scheduling: Disabled live regions still speak updates · case 05

Disabled live regions still speak updates.

Assistive announcements◈ Members↗
FA-8416

Live-region announcement scheduling: Busy live regions announce incomplete updates · case 01

Busy live regions announce incomplete updates.

Assistive announcements● Open access↗
FA-8417

Live-region announcement scheduling: Busy live regions announce incomplete updates · case 02

Busy live regions announce incomplete updates.

Assistive announcements◈ Members↗
FA-8418

Live-region announcement scheduling: Busy live regions announce incomplete updates · case 03

Busy live regions announce incomplete updates.

Assistive announcements◈ Members↗
FA-8419

Live-region announcement scheduling: Busy live regions announce incomplete updates · case 04

Busy live regions announce incomplete updates.

Assistive announcements◈ Members↗
FA-8420

Live-region announcement scheduling: Busy live regions announce incomplete updates · case 05

Busy live regions announce incomplete updates.

Assistive announcements◈ Members↗
FA-8421

Live-region announcement scheduling: Urgent announcements wait behind polite messages · case 01

Urgent announcements wait behind polite messages.

Assistive announcements● Open access↗
FA-8422

Live-region announcement scheduling: Urgent announcements wait behind polite messages · case 02

Urgent announcements wait behind polite messages.

Assistive announcements◈ Members↗
FA-8423

Live-region announcement scheduling: Urgent announcements wait behind polite messages · case 03

Urgent announcements wait behind polite messages.

Assistive announcements◈ Members↗
FA-8424

Live-region announcement scheduling: Urgent announcements wait behind polite messages · case 04

Urgent announcements wait behind polite messages.

Assistive announcements◈ Members↗
FA-8425

Live-region announcement scheduling: Urgent announcements wait behind polite messages · case 05

Urgent announcements wait behind polite messages.

Assistive announcements◈ Members↗
FA-8426

Live-region announcement scheduling: Atomic announcements read only the appended fragment · case 01

Atomic announcements read only the appended fragment.

Assistive announcements● Open access↗
FA-8427

Live-region announcement scheduling: Atomic announcements read only the appended fragment · case 02

Atomic announcements read only the appended fragment.

Assistive announcements◈ Members↗
FA-8428

Live-region announcement scheduling: Atomic announcements read only the appended fragment · case 03

Atomic announcements read only the appended fragment.

Assistive announcements◈ Members↗
FA-8429

Live-region announcement scheduling: Atomic announcements read only the appended fragment · case 04

Atomic announcements read only the appended fragment.

Assistive announcements◈ Members↗
FA-8430

Live-region announcement scheduling: Atomic announcements read only the appended fragment · case 05

Atomic announcements read only the appended fragment.

Assistive announcements◈ Members↗
FA-8431

Accessible name precedence: Referenced labels are reordered alphabetically · case 01

Referenced labels are reordered alphabetically.

Assistive semantics● Open access↗
FA-8432

Accessible name precedence: Referenced labels are reordered alphabetically · case 02

Referenced labels are reordered alphabetically.

Assistive semantics◈ Members↗
FA-8433

Accessible name precedence: Referenced labels are reordered alphabetically · case 03

Referenced labels are reordered alphabetically.

Assistive semantics◈ Members↗
FA-8434

Accessible name precedence: Referenced labels are reordered alphabetically · case 04

Referenced labels are reordered alphabetically.

Assistive semantics◈ Members↗
FA-8435

Accessible name precedence: Referenced labels are reordered alphabetically · case 05

Referenced labels are reordered alphabetically.

Assistive semantics◈ Members↗
FA-8436

Accessible name precedence: An explicit empty aria-label falls back to unrelated text · case 01

An explicit empty aria-label falls back to unrelated text.

Assistive semantics● Open access↗
FA-8437

Accessible name precedence: An explicit empty aria-label falls back to unrelated text · case 02

An explicit empty aria-label falls back to unrelated text.

Assistive semantics◈ Members↗
FA-8438

Accessible name precedence: An explicit empty aria-label falls back to unrelated text · case 03

An explicit empty aria-label falls back to unrelated text.

Assistive semantics◈ Members↗
FA-8439

Accessible name precedence: An explicit empty aria-label falls back to unrelated text · case 04

An explicit empty aria-label falls back to unrelated text.

Assistive semantics◈ Members↗
FA-8440

Accessible name precedence: An explicit empty aria-label falls back to unrelated text · case 05

An explicit empty aria-label falls back to unrelated text.

Assistive semantics◈ Members↗
FA-8441

Accessible name precedence: An explicit empty native label falls back to content · case 01

An explicit empty native label falls back to content.

Assistive semantics● Open access↗
FA-8442

Accessible name precedence: An explicit empty native label falls back to content · case 02

An explicit empty native label falls back to content.

Assistive semantics◈ Members↗
FA-8443

Accessible name precedence: An explicit empty native label falls back to content · case 03

An explicit empty native label falls back to content.

Assistive semantics◈ Members↗
FA-8444

Accessible name precedence: An explicit empty native label falls back to content · case 04

An explicit empty native label falls back to content.

Assistive semantics◈ Members↗
FA-8445

Accessible name precedence: An explicit empty native label falls back to content · case 05

An explicit empty native label falls back to content.

Assistive semantics◈ Members↗
FA-8446

Accessible name precedence: Hidden content is used as a fallback accessible name · case 01

Hidden content is used as a fallback accessible name.

Assistive semantics● Open access↗
FA-8447

Accessible name precedence: Hidden content is used as a fallback accessible name · case 02

Hidden content is used as a fallback accessible name.

Assistive semantics◈ Members↗
FA-8448

Accessible name precedence: Hidden content is used as a fallback accessible name · case 03

Hidden content is used as a fallback accessible name.

Assistive semantics◈ Members↗
FA-8449

Accessible name precedence: Hidden content is used as a fallback accessible name · case 04

Hidden content is used as a fallback accessible name.

Assistive semantics◈ Members↗
FA-8450

Accessible name precedence: Hidden content is used as a fallback accessible name · case 05

Hidden content is used as a fallback accessible name.

Assistive semantics◈ Members↗
FA-8451

Accessible name precedence: Empty referenced labels are dropped and precedence changes · case 01

Empty referenced labels are dropped and precedence changes.

Assistive semantics● Open access↗
FA-8452

Accessible name precedence: Empty referenced labels are dropped and precedence changes · case 02

Empty referenced labels are dropped and precedence changes.

Assistive semantics◈ Members↗
FA-8453

Accessible name precedence: Empty referenced labels are dropped and precedence changes · case 03

Empty referenced labels are dropped and precedence changes.

Assistive semantics◈ Members↗
FA-8454

Accessible name precedence: Empty referenced labels are dropped and precedence changes · case 04

Empty referenced labels are dropped and precedence changes.

Assistive semantics◈ Members↗
FA-8455

Accessible name precedence: Empty referenced labels are dropped and precedence changes · case 05

Empty referenced labels are dropped and precedence changes.

Assistive semantics◈ Members↗
FA-8456

Accessible relationship resolution: A control can reference itself as its controlled target · case 01

A control can reference itself as its controlled target.

Assistive semantics● Open access↗
FA-8457

Accessible relationship resolution: A control can reference itself as its controlled target · case 02

A control can reference itself as its controlled target.

Assistive semantics◈ Members↗
FA-8458

Accessible relationship resolution: A control can reference itself as its controlled target · case 03

A control can reference itself as its controlled target.

Assistive semantics◈ Members↗
FA-8459

Accessible relationship resolution: A control can reference itself as its controlled target · case 04

A control can reference itself as its controlled target.

Assistive semantics◈ Members↗
FA-8460

Accessible relationship resolution: A control can reference itself as its controlled target · case 05

A control can reference itself as its controlled target.

Assistive semantics◈ Members↗
FA-8461

Accessible relationship resolution: Duplicate target IDs are announced repeatedly · case 01

Duplicate target IDs are announced repeatedly.

Assistive semantics● Open access↗
FA-8462

Accessible relationship resolution: Duplicate target IDs are announced repeatedly · case 02

Duplicate target IDs are announced repeatedly.

Assistive semantics◈ Members↗
FA-8463

Accessible relationship resolution: Duplicate target IDs are announced repeatedly · case 03

Duplicate target IDs are announced repeatedly.

Assistive semantics◈ Members↗
FA-8464

Accessible relationship resolution: Duplicate target IDs are announced repeatedly · case 04

Duplicate target IDs are announced repeatedly.

Assistive semantics◈ Members↗
FA-8465

Accessible relationship resolution: Duplicate target IDs are announced repeatedly · case 05

Duplicate target IDs are announced repeatedly.

Assistive semantics◈ Members↗
FA-8466

Accessible relationship resolution: One missing relationship erases all resolved targets · case 01

One missing relationship erases all resolved targets.

Assistive semantics● Open access↗
FA-8467

Accessible relationship resolution: One missing relationship erases all resolved targets · case 02

One missing relationship erases all resolved targets.

Assistive semantics◈ Members↗
FA-8468

Accessible relationship resolution: One missing relationship erases all resolved targets · case 03

One missing relationship erases all resolved targets.

Assistive semantics◈ Members↗
FA-8469

Accessible relationship resolution: One missing relationship erases all resolved targets · case 04

One missing relationship erases all resolved targets.

Assistive semantics◈ Members↗
FA-8470

Accessible relationship resolution: One missing relationship erases all resolved targets · case 05

One missing relationship erases all resolved targets.

Assistive semantics◈ Members↗
FA-8471

Accessible relationship resolution: Relationships resolve to incompatible widget roles · case 01

Relationships resolve to incompatible widget roles.

Assistive semantics● Open access↗
FA-8472

Accessible relationship resolution: Relationships resolve to incompatible widget roles · case 02

Relationships resolve to incompatible widget roles.

Assistive semantics◈ Members↗
FA-8473

Accessible relationship resolution: Relationships resolve to incompatible widget roles · case 03

Relationships resolve to incompatible widget roles.

Assistive semantics◈ Members↗
FA-8474

Accessible relationship resolution: Relationships resolve to incompatible widget roles · case 04

Relationships resolve to incompatible widget roles.

Assistive semantics◈ Members↗
FA-8475

Accessible relationship resolution: Relationships resolve to incompatible widget roles · case 05

Relationships resolve to incompatible widget roles.

Assistive semantics◈ Members↗
FA-8476

Accessible relationship resolution: Hidden relationship targets remain exposed · case 01

Hidden relationship targets remain exposed.

Assistive semantics● Open access↗
FA-8477

Accessible relationship resolution: Hidden relationship targets remain exposed · case 02

Hidden relationship targets remain exposed.

Assistive semantics◈ Members↗
FA-8478

Accessible relationship resolution: Hidden relationship targets remain exposed · case 03

Hidden relationship targets remain exposed.

Assistive semantics◈ Members↗
FA-8479

Accessible relationship resolution: Hidden relationship targets remain exposed · case 04

Hidden relationship targets remain exposed.

Assistive semantics◈ Members↗
FA-8480

Accessible relationship resolution: Hidden relationship targets remain exposed · case 05

Hidden relationship targets remain exposed.

Assistive semantics◈ Members↗
FA-8481

Successful form control collection: Disabled field values are submitted · case 01

Disabled field values are submitted.

Form submission● Open access↗
FA-8482

Successful form control collection: Disabled field values are submitted · case 02

Disabled field values are submitted.

Form submission◈ Members↗
FA-8483

Successful form control collection: Disabled field values are submitted · case 03

Disabled field values are submitted.

Form submission◈ Members↗
FA-8484

Successful form control collection: Disabled field values are submitted · case 04

Disabled field values are submitted.

Form submission◈ Members↗
FA-8485

Successful form control collection: Disabled field values are submitted · case 05

Disabled field values are submitted.

Form submission◈ Members↗
FA-8486

Successful form control collection: Unnamed controls create empty-name form entries · case 01

Unnamed controls create empty-name form entries.

Form submission● Open access↗
FA-8487

Successful form control collection: Unnamed controls create empty-name form entries · case 02

Unnamed controls create empty-name form entries.

Form submission◈ Members↗
FA-8488

Successful form control collection: Unnamed controls create empty-name form entries · case 03

Unnamed controls create empty-name form entries.

Form submission◈ Members↗
FA-8489

Successful form control collection: Unnamed controls create empty-name form entries · case 04

Unnamed controls create empty-name form entries.

Form submission◈ Members↗
FA-8490

Successful form control collection: Unnamed controls create empty-name form entries · case 05

Unnamed controls create empty-name form entries.

Form submission◈ Members↗
FA-8491

Successful form control collection: Unchecked choices submit values as though selected · case 01

Unchecked choices submit values as though selected.

Form submission● Open access↗
FA-8492

Successful form control collection: Unchecked choices submit values as though selected · case 02

Unchecked choices submit values as though selected.

Form submission◈ Members↗
FA-8493

Successful form control collection: Unchecked choices submit values as though selected · case 03

Unchecked choices submit values as though selected.

Form submission◈ Members↗
FA-8494

Successful form control collection: Unchecked choices submit values as though selected · case 04

Unchecked choices submit values as though selected.

Form submission◈ Members↗
FA-8495

Successful form control collection: Unchecked choices submit values as though selected · case 05

Unchecked choices submit values as though selected.

Form submission◈ Members↗
FA-8496

Successful form control collection: All submit buttons contribute their values · case 01

All submit buttons contribute their values.

Form submission● Open access↗
FA-8497

Successful form control collection: All submit buttons contribute their values · case 02

All submit buttons contribute their values.

Form submission◈ Members↗
FA-8498

Successful form control collection: All submit buttons contribute their values · case 03

All submit buttons contribute their values.

Form submission◈ Members↗
FA-8499

Successful form control collection: All submit buttons contribute their values · case 04

All submit buttons contribute their values.

Form submission◈ Members↗
FA-8500

Successful form control collection: All submit buttons contribute their values · case 05

All submit buttons contribute their values.

Form submission◈ Members↗

INSPECTABLE BY DESIGN

Every result has a runnable source.

Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.

Read the methodology ↗