How to make an accessible pricing table in WordPress without a plugin
Make a pricing table in WordPress without a plugin, from Columns, Group, List and Buttons core blocks that take your theme's colours, and keep it accessible.
You can make a pricing table in WordPress without a plugin: a Heading, then a Columns block with one Group per tier, and inside each Group a Heading for the plan name, Paragraphs for the price and summary, a List of features and a Buttons block. Leave the colour and font settings on those blocks empty, or pick swatches from your theme's palette, and the table takes your theme's colours and type, and follows them when the theme changes.
A pricing plugin earns its place when you need a monthly and yearly toggle, or prices pulled live from a shop. For a fixed set of plans, core blocks give you markup you own, with no extra script and no stylesheet that outlives the plugin. The harder part is the one most pricing sections skip: making the table make sense to a screen reader and a keyboard.
Build it with core blocks, step by step#
- Add a Heading block (H2) that names the choice, such as "Plans and prices".
- Add a Columns block below it, with one column per tier. Columns stack on a phone without any extra setting.
- Put a Group block in each column. Give it padding from the spacing presets and, if you want a card surface, a background swatch from the theme palette rather than a custom colour. How palette presets work explains why the swatch matters.
- Fill the Group: a Heading (H3) for the plan name, a Paragraph for the price, a Paragraph saying who the plan is for, a List of features and a Buttons block with one Button.
- Finish one tier, then duplicate its column (Options, then Duplicate) for the others, and change the words.
- Check the Styles tab of every block before you publish. Any colour or font that shows a custom value instead of a theme preset will ignore your palette and your next rebrand.
That gives you a working table. The sections below are what makes it an accessible one.
Common accessibility failures in pricing layouts#
Audits of commercial pricing components consistently expose four critical structural defects:
- Broken heading hierarchies: Tier names such as "Starter", "Team", or "Enterprise" are frequently styled using generic
<span>or<p>tags with inline font sizes rather than proper<h3>elements. Screen reader users navigating by headings cannot build a mental outline of available tiers or jump directly between plans. - Ambiguous call-to-action buttons: Multiple buttons on the same page labelled simply "Get started", "Buy now", or "Select plan" provide zero context when an assistive technology user tabs through interactive controls in isolation.
- Inaccessible feature checkmarks: Feature checklists that use standalone SVG icons or emoji tick marks without descriptive text leave non-sighted visitors unable to tell whether a capability is included, excluded, or optional.
- Low-contrast badges and muted text: "Popular" badges, billing frequency notes, and secondary feature descriptions placed on tinted background bands frequently fall below the WCAG AA minimum contrast ratio of 4.5:1 for standard text.
Choosing between card grids and data tables#
Before opening the block editor, decide whether your pricing model represents a comparison of cards or a structured data table:
- Tier card grids: Best when each plan has a distinct persona, a short summary of four to six core benefits, and a dedicated purchase button. A standard
wp:columnslayout with nested cards provides the most readable structure on both mobile screens and desktop viewports. - Detailed comparison matrix: Required when comparing dozens of granular technical specifications, capacity limits, and line-item features across three or more tiers. This layout demands a genuine HTML
<table>element with row and column headers (<th scope="col">and<th scope="row">), allowing assistive technologies to announce the corresponding tier and feature name for every cell.
Here is how an interactive comparison section can balance visual distinction with structured layout:
Structuring semantic card markup with core blocks#
An accessible three-tier pricing grid relies on a disciplined container hierarchy. At the root, an <h2> introduces the pricing options. Inside a wp:columns container, each column houses one complete tier card wrapped in a wp:group.
Inside each card, use an <h3> for the plan tier name, followed by a dedicated price paragraph, an introductory paragraph, a semantic unordered list (<ul>) for included features, and an explicitly labelled button.
Here is the clean core block markup for an accessible tier card:
<!-- wp:group {"className":"pricing-card","style":{"spacing":{"padding":{"top":"var:preset|spacing|40","bottom":"var:preset|spacing|40","left":"var:preset|spacing|40","right":"var:preset|spacing|40"}}},"layout":{"type":"flex","orientation":"vertical"}} -->
<div class="wp-block-group pricing-card">
<!-- wp:heading {"level":3,"fontSize":"large"} -->
<h3 class="wp-block-heading has-large-font-size">Professional</h3>
<!-- /wp:heading -->
<!-- wp:paragraph {"style":{"typography":{"fontSize":"2.5rem","lineHeight":"1"}}} -->
<p style="font-size:2.5rem;line-height:1"><strong>$49</strong> <span style="font-size:1rem;color:var(--wp--preset--color--contrast-muted)">/ month</span></p>
<!-- /wp:paragraph -->
<!-- wp:paragraph {"fontSize":"small"} -->
<p class="has-small-font-size">For growing organisations requiring advanced workflow controls and priority support.</p>
<!-- /wp:paragraph -->
<!-- wp:list {"className":"pricing-features"} -->
<ul class="wp-block-list pricing-features">
<!-- wp:list-item -->
<li><span class="screen-reader-text">Included: </span>Unlimited active projects</li>
<!-- /wp:list-item -->
<!-- wp:list-item -->
<li><span class="screen-reader-text">Included: </span>Advanced permission controls</li>
<!-- /wp:list-item -->
<!-- wp:list-item -->
<li><span class="screen-reader-text">Included: </span>Automated daily backups</li>
<!-- /wp:list-item -->
</ul>
<!-- /wp:list -->
<!-- wp:buttons {"layout":{"type":"flex","justifyContent":"center"}} -->
<div class="wp-block-buttons">
<!-- wp:button {"width":100} -->
<div class="wp-block-button has-custom-width wp-block-button__width-100">
<a class="wp-block-button__link wp-element-button" href="/checkout/?plan=pro" aria-label="Sign up for the Professional plan at $49 per month">Get Professional</a>
</div>
<!-- /wp:button -->
</div>
<!-- /wp:buttons -->
</div>
<!-- /wp:group -->
Adding screen-reader context to CTA buttons#
When a visually impaired user navigates a webpage using a screen reader rotor or keyboard shortcuts, the software compiles all links into an alphabetical list. If every tier button simply says "Get started", the list presents three identical entries with no indication of cost or entitlement.
You can resolve this ambiguity in two ways:
- Explicit
aria-labelattributes: Adding an descriptivearia-labelto each link overrides the visible text for assistive software: ``html <a class="wp-block-button__link" href="/checkout/?plan=team" aria-label="Subscribe to the Team plan at £79 per month">Get started</a>`` - Visually hidden text elements: Inserting a span with the standard WordPress
.screen-reader-textutility class inside the button text preserves the visual layout while appending necessary context: ``html <a class="wp-block-button__link" href="/checkout/?plan=team">Get started <span class="screen-reader-text">on the Team plan (£79/month)</span></a>``
Both techniques allow sighted users to enjoy concise, punchy call-to-action labels while giving assistive technology users the exact details they need to make an informed decision.
Communicating feature inclusion accessibly#
Pricing lists often feature icons: green ticks for included items and grey crosses for excluded capabilities. A screen reader reading a list that only contains icon markup will either skip the icon entirely or announce an unhelpful image filename.
To ensure feature checklists are readable:
- Prefix list items with accessible text: Use
<span class="screen-reader-text">Included: </span>or<span class="screen-reader-text">Not included: </span>before the feature description. - Provide high visual contrast: Do not rely solely on colour (green vs red) to convey status. Sighted users with colour vision deficiencies need distinct shape indicators or clear strikethrough styling to distinguish included and excluded rows.
- Ensure minimum tap targets: On touch screens, each interactive link or disclosure trigger must meet the minimum 44px by 44px target size mandated by WCAG Success Criterion 2.5.5.
Verifying contrast and keyboard focus#
Before deploying a pricing section to production, run these three checks on your staging environment:
- Test keyboard tab order: Unplug your mouse and press
Tabrepeatedly to cycle through the pricing cards. Ensure the browser focus ring is clearly visible around each tier button, that focus flows logically from left to right, and that no interactive element is skipped. - Inspect contrast ratios: Use Chrome DevTools or Lighthouse to audit contrast between text, badges, and card surfaces. Highlighted tier cards with coloured backgrounds must maintain at least a 4.5:1 contrast ratio against body text and 3:1 against UI borders.
- Validate across default themes: Confirm that your typography classes and spacing presets scale smoothly between mobile and desktop viewports without horizontal table overflow.
Pattern Paste's pricing patterns are this recipe already built: core-block markup with no colour or font of its own, checked for contrast in Twenty Twenty-Five and Twenty Twenty-Four, ready to paste. For a feature-by-feature grid, the comparison patterns use a real table.
From the library






