Describe the relevant detail

W3C’s image guidance distinguishes informative, decorative and functional images. Apply that distinction to a portfolio: a project photograph may need a description of the feature it demonstrates, while a purely decorative background may not convey additional information. Keep important project facts in nearby text as well. A reader should not need perfect vision or a high-resolution download to understand what you delivered.

Avoid empty visual language

Descriptions such as beautiful design or amazing project do not explain the work. Identify the arrangement, material, action or outcome relevant to the case study. Do not repeat a long caption word for word if the surrounding interface already provides it accessibly. For charts and complex diagrams, supply an equivalent explanation or data table. Review the published page with images unavailable to see whether the story remains coherent.

Imagine this

Hypothetical example

A hypothetical architecture portfolio describes a courtyard image as showing shaded circulation linking three entrances, rather than simply “luxury building.” The accompanying text explains the circulation brief. A decorative texture receives no competing description because it contributes atmosphere rather than project evidence.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

W3C WAI: Images Tutorial ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.