Editorial Standards

Last updated: November 2026

Overview

These editorial standards define the quality bar that every tool, article and page on OmniColor must meet before publication. They are based on Google's E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness) and reflect our commitment to genuine usefulness over filler content.

If a piece of content on OmniColor does not meet these standards, it does not belong on OmniColor.

Foundational Requirements

Every page must be:

  • Original: Not copied, scraped, paraphrased from other sites, or generated by AI from templates
  • Accurate: Every factual claim is verifiable and verifiably correct
  • Useful: Provides genuine value to the reader beyond what a single-sentence answer would provide
  • Complete: Covers the topic thoroughly without padding
  • Honest: Discloses limitations, does not make false claims, does not fabricate statistics or testimonials

Tool Page Standards

Every tool page must include:

Working Tool

  • The tool must fully function as advertised. No placeholder tools, no "coming soon" pages, no disabled features without clear indication.
  • Every advertised capability must actually be implemented and tested.
  • The tool must work on mobile (down to 320px width) and desktop.

Technical Explanation

  • A clear explanation of what the tool does and how it works.
  • For any mathematical operation (color conversion, contrast ratio, Delta E), the actual formula must be shown.
  • For any standard followed (WCAG, CSS Color Module), the specification must be cited.

How-to-Use Instructions

  • Step-by-step instructions for using the tool.
  • Each step described in plain language, not technical jargon.
  • Screenshots or examples where helpful.

Real Examples

  • At least 3 real examples showing input → output for that tool.
  • Examples use common, recognizable colors or values.
  • Examples are correct — if we say #FF0000 converts to rgb(255, 0, 0), it must actually do so.

Use Cases

  • At least 4 concrete scenarios where a user would use this tool.
  • Specific to real professions or workflows, not generic ("for designers").

Limitations

  • Honest disclosure of what the tool cannot do or does approximately.
  • Notes about color space gamut differences for RGB↔CMYK.
  • Notes about approximate simulations (color blindness, mesh gradients).

FAQs

  • At least 4 genuine FAQs based on real questions users ask.
  • Each answer is 2-4 sentences, substantive and specific.
  • No questions invented just to have FAQs.

Related Links

  • At least 3 links to genuinely related tools or guides.
  • Links open related tool pages, not a random "recommended" section.

Article Standards

Every blog article or guide must include:

Original Perspective

  • The article must add something beyond what a Wikipedia summary provides.
  • Either: practical experience, specific examples, technical depth, or unique framing.
  • Not acceptable: generic restatements of common knowledge.

Depth

  • At least 800 words for guides, 1200 for in-depth articles.
  • Depth is achieved through useful content — not padding with filler.
  • H2 and H3 headings create a logical structure.

Accuracy and Citations

  • Every factual claim is accurate.
  • Every non-obvious claim is cited or linked to a reliable source.
  • Color theory claims reference established sources (Itten, Munsell, W3C).
  • Statistics are real — never invented.

Examples and Illustrations

  • Each concept illustrated with a concrete example.
  • Where appropriate, visual examples (color swatches, diagrams).
  • Code examples tested and functional.

Author Information

  • Byline or attribution where the article has a specific author.
  • Author bio for the editorial team available on the Editorial Team page.
  • No fabricated authors or credentials.

Review Date

  • Publication date and last-updated date shown.
  • Updated only when actually reviewed/changed — not for SEO purposes.

Language Standards

  • Clear: No jargon without explanation.
  • Direct: Each sentence serves a purpose.
  • Precise: No vague claims ("best", "amazing") without evidence.
  • Neutral: No unnecessary marketing hype.
  • Respectful: No condescension, no mockery of competitors or users.

Fact-Checking Process

Every factual claim goes through:

  1. Drafting: Writer makes claim with source in mind.
  2. Source verification: Reviewer checks the source actually supports the claim.
  3. Cross-reference: For contested claims, multiple sources required.
  4. Specification check: For technical claims, verified against W3C or other authoritative source.

Update and Review Cadence

  • Technical content (WCAG, CSS, browser support): Reviewed every 12 months.
  • Framework palettes (Tailwind, Bootstrap, Material): Reviewed when frameworks release major updates.
  • General content: Reviewed when errors are reported.
  • Tool descriptions: Reviewed when tools are updated.

Prohibited Content Practices

We never:

  • Generate AI content and present it as human-written without disclosure. Where AI is used as a tool, humans are responsible for accuracy and originality.
  • Publish hundreds of near-identical pages to manipulate search rankings.
  • Keyword stuff or repeat keywords unnaturally.
  • Create fake testimonials or reviews.
  • Publish inflated statistics.
  • Fabricate authors or credentials.
  • Hide advertising as editorial content.
  • Manipulate dates to appear "recently updated" without actual changes.

Accessibility Standards

Every page must meet WCAG 2.2 AA:

  • Body text contrast ≥ 4.5:1
  • Large text contrast ≥ 3:1
  • Keyboard navigable
  • Screen-reader compatible (tested with NVDA/VoiceOver)
  • Descriptive alt text on images
  • Semantic heading hierarchy

Technical Standards

Every page must:

  • Load in under 2 seconds on a 4G connection (measured on real deployment)
  • Score 90+ on Lighthouse Performance
  • Score 100 on Lighthouse Accessibility (where achievable)
  • Have zero console errors
  • Pass W3C HTML validation

Editorial Independence

OmniColor's editorial content is independent of advertising and business relationships:

  • Advertisers cannot purchase editorial coverage.
  • Advertisers cannot request changes to tool descriptions or articles.
  • Advertising is clearly separated from tool content.
  • No paid "featured tool" placements exist.
  • No affiliate marketing disguised as editorial.

Corrections

When we make mistakes, we correct them promptly and transparently. See our Corrections Policy for how we handle corrections.

Complaints and Feedback

If you believe any OmniColor content fails these standards, please email editorial@omnicolor.pages.dev with:

  • The page URL
  • The specific issue
  • What standard it fails

We take every editorial complaint seriously and will respond within 5 business days.

Review and Iteration

These standards themselves are reviewed annually and updated based on:

  • Feedback from readers
  • Evolution of search engine quality guidelines
  • Changes in applicable regulations
  • Team learning

Contact

Questions about editorial standards: editorial@omnicolor.pages.dev

Report an error or violation: editorial@omnicolor.pages.dev