Corrections Policy
Last updated: November 2026
Our Commitment to Accuracy
Every piece of content on OmniColor is written with accuracy as a primary goal. But accuracy is a process, not a guarantee. When we discover an error — or a reader reports one — we correct it promptly, transparently, and without defensiveness.
This policy explains how we handle corrections, what kind of correction you can expect for each severity of error, and how you can report one.
How to Report an Error
If you spot an error in any OmniColor content, please let us know:
- Email: editorial@omnicolor.pages.dev
- Subject line: "Correction — [page URL]"
Please include:
- The URL of the page with the error
- The specific text that is wrong
- What the correct information should be
- A source or reference supporting the correction (if possible)
We do not require a source, but it helps us verify quickly. If you are unsure whether something is an error, err on the side of reporting — we would rather investigate a non-issue than miss a real error.
Correction Severity Levels
We categorize corrections by severity and respond within the following timeframes:
Critical (within 24 hours)
Errors that could cause user harm, loss, or legal issues:
- Incorrect WCAG contrast thresholds (e.g., stating AA is 3:1 instead of 4.5:1)
- Incorrect color conversion formulas that produce wrong output
- Tool descriptions that do not match actual tool behavior
- Security-related misstatements
- Legal or regulatory misinformation
Critical corrections are made within 24 hours of verification.
Significant (within 5 business days)
Errors that meaningfully mislead readers but are unlikely to cause harm:
- Incorrect examples (e.g., wrong RGB value for a HEX code)
- Outdated browser support claims
- Incorrect statistics or attributed data
- Wrong color names or mislabeled swatches
- Incorrect link targets
Significant corrections are made within 5 business days of verification.
Minor (within 10 business days)
Errors that are worth fixing but do not meaningfully impact understanding:
- Typos and grammatical errors
- Formatting issues
- Inconsistent terminology
- Broken links that still have working alternatives
Minor corrections are made within 10 business days, often batched.
How Corrections Appear on the Page
Depending on severity, corrections are handled in different ways:
Silent corrections
For typos, grammar, and formatting issues, we fix the text directly without a visible note. These changes do not meaningfully alter meaning.
Noted corrections
For significant errors, we:
- Fix the incorrect text
- Add a correction note at the bottom of the article (visible to readers)
- Update the "last updated" date
Example note: "Correction (November 2026): An earlier version of this article incorrectly stated that WCAG AA requires a 3:1 contrast ratio for body text. The correct threshold is 4.5:1."
Major corrections
For critical errors or substantial rewrites, we:
- Fix the incorrect text
- Add a prominent correction note at the top and bottom
- Explain what was wrong and what the correct information is
- Add a change log entry
- Notify any subscribers (if we have a newsletter)
Examples of Past Corrections
To be fully transparent, we maintain a public changelog of all significant corrections. See our Changelog for details.
What We Do Not Do
- We do not silently alter facts to make a page seem correct after a reader has already read it — significant changes get a visible correction note.
- We do not delete pages that contain errors — we correct them. Deleting pages creates broken links and hides the correction from users who may have bookmarked them.
- We do not blame the reader when they report an error, even if it turns out not to be one. We appreciate the report.
- We do not "update" dates on pages we have not actually changed for SEO purposes.
How to Report a Broken Tool
Broken tools (buttons that do not work, outputs that fail) are treated as critical corrections. If a tool is broken:
- Report it via support@omnicolor.pages.dev
- Include the tool URL, what you were doing, and what went wrong
- Include your browser and OS (Chrome 120 on macOS 14, etc.)
- Include a screenshot if possible
We aim to acknowledge tool bugs within 24 hours and fix confirmed bugs within 5 business days (or sooner if the bug affects many users).
Corrections Involving Third-Party Content
If you believe content on OmniColor infringes your copyright, this is not the right process. Please use our DMCA Policy.
If you believe content is factually wrong but is presented as a quote from a third party, we will review whether the quote is accurately represented. If the quote is accurate to the source, we will not change it — we will add a note that "this is a quote from the source, not our own claim."
No Retraction Policy
OmniColor does not "retract" content. Instead, we correct it and clearly note what was corrected. We do not delete content that was based on an honest mistake unless it poses ongoing harm.
Content is only removed when:
- It contains personal information that must be removed for privacy reasons
- It contains copyrighted content that we do not have rights to
- It poses an active danger to users (e.g., instructions for something harmful)
- It violates our own editorial standards and cannot be corrected
Communication of Corrections
For significant and critical corrections, we:
- Reply to the reader who reported it (thanking them and explaining the change)
- Update the article with a visible correction note
- Add an entry to our public changelog
- Where the error was likely to have misled many users, we may also note the correction on our homepage
Our Standards Team
Corrections are handled by our editorial team. Every correction is reviewed by at least one team member other than the original author, ensuring the correction is accurate.
Thank You
If you report a correction, thank you. Your feedback makes OmniColor more accurate and more useful for everyone. We genuinely appreciate readers who take the time to help us improve.
Contact
Corrections and content feedback: editorial@omnicolor.pages.dev
Tool bugs: support@omnicolor.pages.dev
General feedback: Feedback page