
An image's aria-describedby can expose a table's words as a continuous description without preserving table navigation inside that description. W3C's complex-image guidance identifies this limitation. Keep the detailed table independently available when readers need to inspect individual rows or columns.
The problem is the description channel, not a rule that adding aria-describedby destroys a visible HTML table. A visible table can still be reached separately in the document. Do not hide or remove that independent route merely because all its words appear in an announced description.
Compare two markup arrangements
The following minimal examples use an invented two-option print comparison. Replace the illustrative image path with an authorized diagram to reproduce the check locally. No browser or assistive-technology test was run for this guide.
Arrangement A attaches the visible table as the image description:
<img src="print-options.png" alt="Print option comparison"
aria-describedby="data-a">
<table id="data-a">
<caption>Illustrative print choices</caption>
<tr><th scope="col">Option</th><th scope="col">Width</th></tr>
<tr><th scope="row">Small</th><td>10 cm</td></tr>
<tr><th scope="row">Large</th><td>20 cm</td></tr>
</table>
The expected description-channel limitation is continuous text. The table remains visible and should also be evaluated through the reader's ordinary table-navigation route. If the implementation instead hides it and relies solely on the association, that separate structured route can be lost.
Arrangement B uses concise image identification and an ordinary link to a visible table:
<img src="print-options.png"
alt="Two print sizes compared; detailed dimensions follow">
<a href="#data-b">Read the print-dimension table</a>
<table id="data-b">
<caption>Illustrative print choices</caption>
<tr><th scope="col">Option</th><th scope="col">Width</th></tr>
<tr><th scope="row">Small</th><td>10 cm</td></tr>
<tr><th scope="row">Large</th><td>20 cm</td></tr>
</table>
The figures are hypothetical labels for this navigation exercise, not print-production recommendations. The long-description overview helps choose when a detailed equivalent is needed; this comparison isolates how an association differs from independently navigable structure.
Record two different interactions
For each arrangement, record the browser and assistive technology before testing. First encounter the image and note its announced name and any description. Then navigate to the table as table content and request the Large row with its Width column header. Do not describe a successful result until those actions have actually been performed.
For B, activate the adjacent link and confirm that the intended table can be found in the resulting page position and reading sequence. A fragment link is a route to content, not a universal guarantee that every browser moves keyboard focus identically. If the route is unclear, use visible headings or a dedicated description page and retest that arrangement.
Preserve meaning without duplicating every value
Use the context-based alternative-text guide for the short identification. Keep the essential visual conclusion in surrounding prose when it helps readers, but avoid repeating the entire table in the short alternative. If the design includes selectable gallery items, inspect their forced-color selection cues separately; that presentation issue does not resolve description navigation.
Accept the page when the image is identifiable and the detailed values retain the structure required for the task. If values cannot be associated with their headers in the actual delivered page, keep the source data and revise the presentation. Source inspection alone cannot certify the reading experience.
Related tasks
- How Do I Explain a Diagram When One-Line Alt Text Is Not Enough?
- Should I Use My Generation Prompt as Alt Text for an AI Image?
- Why Does My Selected Photo Lose Its Border in Windows High Contrast?
Sources and scope
- Complex Images, W3C WAI: A description supplied through aria-describedby is treated as continuous text rather than exposing its internal headings or table structure.
Reviewed against W3C's complex-image guidance on October 31, 2026. This addresses description-channel structure, not a tested result for every browser and assistive-technology combination.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.