Resources & Insights

This page demonstrates CONTENT_STRUCTURE accessibility violations — page language, document title, heading order, list structure, table headers, and language attributes. The layout looks like a typical blog/resources page.

Page-level violations already planted: html[lang="zz"] — not a valid BCP-47 tag (html-lang-valid · Critical). Empty <title></title> in <head> (document-title · Serious). Both CONTENT_STRUCTURE.

Featured Article — heading jumps from h1 to h4 here (heading-order violation)

The Business Case for Accessibility

Accessibility is not charity — it is good engineering, broader market reach, and reduced legal risk. This article explores the financial and reputational case for investing in inclusive design.

↑ The heading above this article used <h4> immediately after the <h1> page title — skipping two levels. Rule: heading-order (Serious · CONTENT_STRUCTURE). Correct sequence: h1 → h2 → h3 → h4.

Published 12 July 2025 · 8 min read

Read article →
Team collaborating on accessibility audit findings

Recent Articles

    ARIA Authoring for Enterprise

    Common mistakes in large-scale ARIA implementations and how to avoid them. This card is a <div> child of a <ul> — axe fires: list (Serious · CONTENT_STRUCTURE).

    Read →

    Keyboard Navigation Patterns

    How to implement focus management for dialogs, carousels, and data grids. Second <div> child of <ul> — contributes to the list violation node count.

    Read →

    Colour Contrast in Data Visualisation

    Accessible palettes for charts and graphs. Third <div> child — same list violation. Note the low-contrast amber text also demonstrates color-contrast.

    Read →

↑ The <ul> above contains <div> children, not <li> elements. Screen readers cannot identify the list structure or item count. Rule: list (Serious · CONTENT_STRUCTURE).

Accessibility Glossary

WCAG — Web Content Accessibility Guidelines. International standard for digital accessibility published by the W3C.
ARIA — Accessible Rich Internet Applications. A set of HTML attributes that expose semantic information to assistive technologies.
AT — Assistive Technology. Software or hardware that helps users with disabilities interact with digital content (e.g., screen readers, switch access).
AXE — Open-source automated accessibility testing engine used by JOP, Deque, and the wider industry.

↑ The <dl> above contains <div> direct children — not <dt>/<dd> pairs. Screen readers cannot associate terms with definitions. Rule: definition-list (Serious · CONTENT_STRUCTURE).

All terms defined above are drawn from W3C and ISO standards. This paragraph has lang="xx-glossary" — not a valid BCP-47 language code. Rule: valid-lang (Moderate · CONTENT_STRUCTURE).

Benchmark Results

Industry accessibility scores from our 2025 research. The table below plants four table-related CONTENT_STRUCTURE violations.

Sector Avg. WCAG Score Common Failures Trend
Finance 61 / 100 colour contrast, missing labels
Healthcare 54 / 100 missing alt text, keyboard traps
Retail 48 / 100 ARIA misuse, focus management
Government 72 / 100 document structure, language

Table violations: header row uses <td> not <th> (td-has-header · Serious). scope="column-group" is invalid (scope-attr-valid · Moderate). Body cells reference headers="benchmark-tier" which doesn't exist (td-headers-attr · Serious). "Trend" <th> has no body <td> column (th-has-data-cells · Serious). All CONTENT_STRUCTURE.

  • Orphaned list item — rule: listitem
    • Orphaned term — rule: dlitem