Separate a figure from its background
Look at the astronomy club poster. If the moon blends into the stars, the reader may have trouble locating it. Try removing a few stars near its edge or putting a calmer patch behind it. Compare the versions at the size the poster will be seen. The change that helps depends on the shapes and colours already there.
In the faces-or-vase image, the same outline can look like the edge of a vase or the edge of two faces. What you see as the figure can change even though the image stays the same. On a page, check that a card, section or control reads as a distinct group when the task needs it to.
Four ways to mark a group
Space. Compare the gap between two cards with the spacing inside each card. If the cards run together, increase the gap a little at a time. On a narrow screen, try stacking them with the heading and details of each card kept together.
Fill. Try a background colour that distinguishes a region from the surface around it. Very similar fills can be hard to tell apart. View the two colours at the size and brightness people use, then check the contrast of any text placed on the fill.
Border. A clear edge can help identify an input, button or small panel. Decide what the line needs to communicate. A decorative card edge and the only visible outline of a text input have different jobs.
Shadow. A subtle shadow can suggest depth, for example when a menu opens above the page. Try it with and without a shadow. Keep the text, control labels and keyboard focus clear in either version.
Check the edge that carries meaning
For an author-styled web control, check the non-text visual cues needed to identify the control or its state. WCAG 2.2 AA sets at least 3:1 against adjacent colours for those cues, with exceptions for inactive controls and unmodified browser-drawn controls. For example, a sole input outline or a custom focus ring needed to show focus must be distinguishable against adjacent colours. A purely decorative card border has no minimum under this criterion. Check text using the separate text contrast rule. WCAG Non-text Contrast
Try a simple booking form. Put a white input on a white page and use its border as the only visible clue to the field’s edge. Compare a #C7C7C7 border with #949494 against white. The two ratios are about 1.69:1 and 3.03:1. Only the second reaches 3:1 in this example. Give the input a clear label such as Name for the booking, and test the separate keyboard focus style when you enter the field.
Compare on the finished layout
Use the greyscale or blur sketch to compare broad grouping, then open the unfiltered page on a phone. Can you tell where one section ends and the next begins? Can you find each input and its label? If the page is interactive, move through it with a keyboard too. Check that you can see the focused control and that a sticky bar never fully covers it. WCAG Focus Visible and WCAG Focus Not Obscured (Minimum)
For nested cards, test one relationship at a time. If an outer section and an inner card need different cues, use a gap to group the section and a fill to mark the card. Ask a reader which information belongs together. If the cues compete with the text, simplify one layer and try the task again.
Check your understanding
Two informational cards look like one block on a narrow screen. Each already has a clear heading. Which change would you compare first?
Pick the one you would defend. Your answer stays private.
Your place and first choices stay on this browser. Classroom credit is recorded separately.
Stuck on something?Ask Meher, your AI tutor