Compare decision attributes on the same basis
Compare mounting, power and physical constraints on the same basis for every lamp. Keep the source field beside the value, and leave unknown runtime unverified instead of treating it as a missing capability. The table should help a buyer rule out an unsuitable item without manufacturing a universal best product.
Worked example — illustrative data.
| Attribute | Arc | Clamp | Portable | Source |
|---|---|---|---|---|
| Mounting | Base, 16 cm | Clamp up to 45 mm | Base, 12 cm | Approved dimension sheet required |
| Power | Mains | Mains | Rechargeable | Manufacturer record required |
| Main constraint | Needs desk space | Needs compatible edge | Runtime not verified | Product owner review |
| Best-fit task to evaluate | Fixed desk | Small desk with edge | Moving between rooms | Illustrative use hypothesis |
Choose comparison rows from the buyer’s main constraints rather than the longest available specification list. State whether a measurement concerns the product footprint, usable space or attachment limit. Use the same basis for every product. Link each column to the exact product and variant when implementing the table. Keep unverified runtime, durability and safety claims blank or marked unknown until supported. Check the table on a phone with meaningful headers.
Decision: Use this specimen to identify what data is needed for a fair choice. Publish real comparisons only after the owner confirms the source values and the rendered table remains usable.
A missing specification is not proof of missing capability: A missing specification does not mean the product lacks the capability. Mark the value unverified and identify the source needed; do not award the alternative an automatic win.
Should the table declare one product the winner?
Name a best fit only for a stated task and supported constraints. A portable lamp may suit moving between rooms while a clamp model saves desk space. Neither conclusion establishes a universal winner or unverified product performance.
Continue with Guides for stores, software teams and local businesses, eCommerce website design and development and What belongs on an eCommerce product page?.
For table relationships and reflow, see the W3C WCAG quick reference.