A compatibility answer is a scoped finding, not an isolated yes/no label. We record the printer edition, task, media and mode with the evidence. The structured database is intentionally small at launch and grows only when the record adds practical value.
Fields in a model record
- Exact model and market edition.
- Technology and operating or stored dimensions.
- Media type, physical size, documented weight or thickness and input path.
- Borderless and duplex combinations as separate fields.
- Scanner type, scan area, ADF and feeder duplex.
- Connections, consumable codes and declared replacement yields.
- OS versions and applications where a documented route exists.
- Official source URL, checked date and scope for each finding.
Evidence states
| State | Meaning |
|---|---|
| Documented | An official source supports this specific finding under its stated conditions. |
| Observed | A future real test reports this exact combination; conditions must be provided. |
| Not verified | The evidence collected does not answer the question. Do not assume support. |
Unknown is not unsupported
A missing specification is preserved as unknown. We report a limitation as an explicit negative only when an official source or an appropriately scoped real observation supports it. The presence of a feature on a neighboring model is not evidence. Print duplex and scan duplex, for example, are always separate.
Corrections
Use Contact to provide the full model, regional source, section and proposed correction. We do not accept a successful anecdote as proof for an entire category of paper. No launch record claims a hands-on test.