How to fix dlitem on WordPress.org
Wrap every `<dt>` (term) and `<dd>` (description) element inside a parent `<dl>` element so description list items have their required container.
Steps for WordPress.org
- Identify the source of the markup: is it your theme, a page builder (Elementor, Divi, Beaver Builder), or a plugin?
- For theme files: go to Appearance → Theme File Editor, or edit via FTP, and search for `<dt` / `<dd` in your child theme's PHP files.
- For Elementor: use the 'HTML' widget or the 'Text Editor' widget's HTML mode to locate and fix the markup; alternatively, use Elementor's custom code blocks.
- For Divi: open the affected module in the Divi Builder, switch to 'Text' mode in the content area, and add `<dl>` wrappers around bare `<dt>`/`<dd>` tags.
- For Gutenberg blocks: if using a custom HTML block, edit the block directly; if using a third-party block plugin that outputs bad HTML, contact the plugin author or replace the block with a Custom HTML block using correct markup.
- After fixing, flush permalinks (Settings → Permalinks → Save) and any caching, then retest.
What is dlitem?
HTML has a special "description list" structure made up of three tags working together: `<dl>` (the list container), `<dt>` (a term or label), and `<dd>` (the description or value for that term). The rule being violated means your page has one or more `<dt>` or `<dd>` elements that are sitting outside of a `<dl>` wrapper — like list items floating in the air with no list around them. This is a structural HTML error that breaks the semantic meaning of the content and violates WCAG 2.x Success Criterion 1.3.1 (Info and Relationships).
Screen readers used by blind and low-vision shoppers rely on correct HTML structure to announce content meaningfully — for example, reading out "Shipping time: 3–5 business days" as a paired term and value. When `<dt>`/`<dd>` elements lack a `<dl>` parent, screen readers cannot convey that relationship, making product specs, FAQs, and shipping information confusing or completely inaccessible for these customers. This directly violates WCAG 2.1 Success Criterion 1.3.1, which is a legal compliance requirement in many jurisdictions (ADA in the US, EN 301 549 in Europe). Beyond legal risk, accessibility failures can cost you customers, damage your reputation, and expose you to demand letters or lawsuits. Fixing this is also a trust signal: Google's crawlers increasingly reward semantically correct, accessible pages.
See the complete Dlitem guide for every platform and the full background.
Not sure if your WordPress.org store has this?
Run a free SEOLZ scan — we’ll find dlitem and every other issue across your whole site.
Scan my site free