A visitor-facing accessibility interface can offer useful preferences such as larger text, reduced motion or contrast adjustments. That is different from repairing the underlying product.
If a checkout button has no accessible name, a form field has no label, a modal traps focus incorrectly, or a custom component cannot be operated by keyboard, the underlying implementation still matters.
The ADAFix approach
We treat a visitor interface as optional assistance, not as proof of compliance.
The core product is source-level remediation: find the broken behavior, map it to the code when possible, create a reversible fix, and run the relevant test again.
That distinction matters because accessibility is ultimately about whether people can use the website — not whether a toolbar is present.