Corrections Policy
How to report inaccurate explanations, unexpected diagnostic behavior, accessibility issues, and translation mistakes on I/O Checkup.
What to report
Tell us when a test behaves unexpectedly, a label overstates what a measurement means, a translation changes the meaning, or a control is difficult to use. A browser limitation should be explained clearly rather than presented as a device fault.
Help us reproduce it
Include the page URL, browser and operating-system versions, device category, steps taken, and what you expected versus what happened. For a translation issue, include the language and the original wording. A cropped screenshot can help, but remove personal details first.
A denied permission, unsupported API, unusual device mapping, or print-driver setting can produce a different result without a software defect. We compare those conditions before assigning a cause.
How we handle a correction
We assess the report against the relevant browser API and the tool behavior, reproduce it where possible, and correct confirmed errors. A fix may involve a calculation, permission flow, label, explanation, translation, or accessibility control.
Substantive corrections should describe what changed and the scope of affected results. If an old exported result is no longer reliable, the appropriate next step is to rerun that check. Minor spelling and formatting fixes do not require a separate notice.
We cannot promise a response deadline or certify a physical device remotely. Urgent hardware or safety concerns belong with the device manufacturer or a qualified technician.