Label the measurement basis and units
State that the fictional table measures garments laid flat, identify the measurement points and use consistent units. Let the buyer find a size without losing row meaning on a phone, then close the guide and return to selection. Actual product-family measurements and any approved tolerance must replace the example values.
Worked example — illustrative data.
| Size | Garment chest width laid flat | Garment length |
|---|---|---|
| S | 48 cm | 65 cm |
| M | 52 cm | 68 cm |
| L | 56 cm | 71 cm |
Label these as illustrative garment measurements, not a live sizing promise. Place a diagram or plain instruction beside the table explaining the measurement points and whether the fabric is laid flat. If the owner has an approved tolerance or fit description, show it where it changes the choice. For mobile acceptance, ask a tester to find the M measurements without losing row and column meaning. For keyboard acceptance, open and close the guide and return to the size selector with visible focus.
Identical size labels can describe different cuts
Two products can use the same S/M/L labels with different cuts. Link the guide to the relevant product family and make exceptions explicit rather than applying one generic table across the catalog.
Publish a size guide only after the product owner approves measurements and the rendered guide supports the choice. Do not infer personal fit or invent a return guarantee from these dimensions.
Continue with Guides for stores, software teams and local businesses, eCommerce website design and development and Website usability checklist for a buying journey.
For keyboard operation and readable table/reflow behavior, see the W3C WCAG quick reference.