{% load brickwork_icons %} {% comment %} PRICING / comparison table: what each plan actually includes, row by row. WHEN TO USE THIS. Underneath the tier cards, not instead of them. The cards sell; this answers the reader who has narrowed it to two plans and wants to know precisely what the cheaper one gives up. Do not lead a pricing page with it: a grid of twenty ticks is a reference document, not a pitch. WHY IT OWNS ITS MARKUP. No component does this, and it should not: a real comparison is tabular data, and tabular data belongs in a
| on each plan and | on each capability, so
a cell in the middle of the grid is announced as "Team, Multi-currency,
Included" rather than just "Included".
- Every cell says whether it is included in WORDS. The tick and dash are
decorative icons sitting next to visually hidden text, because a tick
alone is meaning carried by shape and colour, which fails WCAG 1.4.1.
WHY THE SCROLL CONTAINER. Four columns of real words do not fit a 360px
phone, and a table that overflows makes the whole PAGE scroll sideways, which
is the thing WCAG 1.4.10 is about. So the table scrolls inside its own box
instead. That box is focusable (tabindex="0") and named (role="region" plus
aria-labelledby), because a scrollable area a mouse user can drag must also
be reachable and operable by keyboard, and a focusable region needs an
accessible name to be worth landing on.
The heading id is referenced by aria-labelledby, so if you copy this section
twice into one page, change the id on both ends of that pair.
No view context needed. The plans and rows are written inline on purpose:
this is the part of a pricing page that gets edited by whoever writes the
copy, not by whoever writes the view.
{% endcomment %}
Compare the plansEverything below is per account, not per invoice. The trial gives you Scale for thirty days whichever plan you end up on.
Prices exclude VAT. Changing plan takes effect on the next invoice, and we credit the unused part of the current one. |
|---|