Give embedded tasks an understandable identity

What to change

Ask the supplier to provide a useful identity for each meaningful embed and verify that its content matches that identity.

A worked example

Illustrative example

A visitor can recognise Appointment request form as the embedded task and distinguish it from the separate Location map farther down the page.

How to check the result

Accept when each meaningful embed has an accurate, distinguishable name and a usable relationship with its surrounding page context.

A mistake to avoid

A useful frame title cannot repair inaccessible controls inside the embed; both the container and its actual interaction need review.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordAsk a tester using a screen reader to inspect the frames or embedded regions on the page. Record generic or missing names that give no clue about purpose.Navigate into and out of each embed. Check the surrounding heading and the embedded identity support the same task rather than contradicting one another.Inspect fallback and loading states. Ask the supplier to keep the purpose clear even before the embedded content becomes available.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.