Skip to content
easeweb
Search topics

Content that disappears on narrow screens and at 400% zoom

A delivery panel set to display: none below 48em is gone on phones and at 400% zoom, and nothing else on the page gives the delivery cost.

WCAG 2.2
SC 1.4.10AA· new in 2.1
Required by
EN 301 549 (EU)
Broken .product-side { display: none; }
The accessibility problem illustrated: Low vision:How much is delivery?
01

The problem

People who zoom to 400%, and anyone on a phone, can't find the delivery cost or the returns period, because the panel that gives them isn't on the page

02

Try it

Zoom the page to 400%, then find out what delivery costs

At 150% the shop’s page has two columns, with Delivery and returns on the right. Drag the Zoom slider to 400% and scroll the page to the end. Where did the delivery cost go?

150%

Broken Can you fix this?

BrokenThe panel hidden below 48em

Enamel mug

$18

Steel with a glossy enamel coat. Holds 350 ml.

Delivery and returns

Dispatched in 1 to 2 working days.

Delivery $4.95, free on orders over $40.

Free returns within 30 days.

Window: 853 by 683 CSS pixels.

Delivery and returns is on the page

A recreated demo. The broken version is intentionally inaccessible.

03

The fix

Keep the panel on the page at every width

Before
BrokenThe panel hidden below 48em
<main class="product">  <div class="product-info">    <h1>Enamel mug</h1>    <p class="price">$18</p>    <button type="button" class="add">Add to bag</button>    <p>Steel with a glossy enamel coat. Holds 350 ml.</p>  </div>  <aside class="product-side" aria-labelledby="delivery-title">    <h2 id="delivery-title">Delivery and returns</h2>    <p>Dispatched in 1 to 2 working days.</p>    <p>Delivery $4.95, free on orders over $40.</p>    <p>Free returns within 30 days.</p>  </aside></main>
What is wrong3 points
  • Below 48em the panel is display: none.
  • At 200% zoom or more in a window 1280 pixels wide, and on a phone, the dispatch time, the delivery cost and the returns period aren't on the page, and nothing on it leads to them.
  • display: none removes the panel for screen readers too, so at those widths nobody gets it.
After

The panel follows the product

<main class="product">  <div class="product-info">    <h1>Enamel mug</h1>    <p class="price">$18</p>    <button type="button" class="add">Add to bag</button>    <p>Steel with a glossy enamel coat. Holds 350 ml.</p>  </div>  <aside class="product-side" aria-labelledby="delivery-title">    <h2 id="delivery-title">Delivery and returns</h2>    <p>Dispatched in 1 to 2 working days.</p>    <p>Delivery $4.95, free on orders over $40.</p>    <p>Free returns within 30 days.</p>  </aside></main>
How it is fixed1 step
  1. Remove display: none from the narrow layout. Below 48em the grid has one column, and the panel follows the product, after its description, in the order of the markup.

This fixes the Before and passes 1.4.10: the panel moves rather than disappearing, which the Understanding page does not count as a loss. On a phone the page gets a little longer, by the panel's heading and three lines.

04

Verify the fix

4 checks, no mouse.

Test with: Zoom, Screen reader

0 of 4 checked

Record the OS, browser and assistive-technology versions, the build, the date, and the actual result of each step. Repeat after the layout's breakpoints or the responsive utilities in the templates change.

Limits

This is a starting pattern, not a guarantee for every application. Comparing two widths finds what has gone, not whether what is left makes sense: check that the reading order still works once the columns stack. A page that scrolls sideways at 320 pixels is a different failure, covered in pages that scroll sideways on a narrow screen, and a dialog that is on the page but runs past the edges of a short window in modals cut off at the top and bottom when zoomed in. Paths and class names in the snippets are placeholders.

This is a recreated teaching example, not a finding about a named client. The code is a starting pattern: test it in your own product. No completed assistive-technology test is claimed here.

EaseWeb service

Fixed it? Keep it from coming back.

I turn guides like this one into rules your coding agents follow and checks your CI runs. Then I retest by hand with a keyboard and screen readers, periodically.

See the service