How to build a contact section in a WordPress block theme without a form plugin
Build a contact section in a WordPress block theme from core blocks: tappable phone and email, address, opening hours and service area, and when a form plugin is worth it.
Most visitors to a contact section want one of four things: a number to tap, an address to send, the hours you are open, or whether you cover their area. Core blocks do all four without a form plugin: Buttons for the phone and email, a Paragraph for the address, a Table for the hours, and Details or a List for the service area. What WordPress will not tell you is when one of them has quietly failed on a phone, so this post covers the build and the checks.
A form plugin is the right tool for some sites, and the last section says which. For a plumber, a clinic or a café, a form is often the slowest way to be reached: the visitor types a message, waits, and rings someone else in the meantime.
What a contact section actually has to carry#
Before you open the editor, list the facts. A contact section is a ledger of those facts, set at reading size, with the two that can be acted on made tappable.
- Phone, as a link a thumb can hit, with the number printed in full.
- Email, as a link, with the address printed in full.
- Address, as text a visitor can copy, plus a link that opens their own map app.
- Opening hours, with closed days stated rather than left out.
- Service area, for anyone who travels to the customer: towns or postcodes, in words.
- A place photograph, optional, when the building is part of finding you.
Anything else (a social row, a newsletter sign-up, a sitemap) belongs in the footer, where visitors look for it on every page. The contact section is for getting hold of a person.
Phone and email: Buttons, not inline links#
The quickest way to add a phone number is to type it into a Paragraph and link it. That gives you a link the height of one line of text, often around 24px on a phone, and a visitor with a thumb hits the line above it. WCAG 2.2 sets 24px as the minimum target at level AA (Success Criterion 2.5.8) and 44px as the enhanced target at AAA (2.5.5); for the one link a customer came to the page to press, aim for 44.
A Button block gives you padding on every side, which is what makes the target tall. Put a Buttons block in the section with one Button for the phone and one for the email, and set each link with the right scheme:
<!-- wp:buttons -->
<div class="wp-block-buttons">
<!-- wp:button -->
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="tel:+441632960018">01632 960018</a></div>
<!-- /wp:button -->
<!-- wp:button {"className":"is-style-outline"} -->
<div class="wp-block-button is-style-outline"><a class="wp-block-button__link wp-element-button" href="mailto:[email protected]">[email protected]</a></div>
<!-- /wp:button -->
</div>
<!-- /wp:buttons -->
Three details matter here.
- The label is the number itself, not "Call us". On a desktop, a
tel:link opens a calling app or nothing at all, so the visitor needs to read the number and dial it from their phone. The same goes formailto:on a computer with no mail client set up: the click does nothing, silently, and the printed address is the only thing that still works. - The
hrefuses the international form,tel:+44followed by the number without its leading zero, so the link works for a visitor on a roaming phone. - Leave the colour settings alone, or pick from the palette. A custom colour on a button ignores your theme from then on; how palette presets work explains why the swatch matters.
The cost: a button is louder than a link. Two filled buttons side by side compete, which is why the email above uses the outline style. If your theme's buttons are still short, the fix is padding in theme.json under styles.elements.button, once, rather than a custom value on every button.
Address and map: a link, not an embed#
Type the address into a Paragraph, with a line break (Shift and Enter) between lines, so it can be selected and copied in one go. Under it, add a Button or a plain link labelled "Open in Maps" that points at a maps search for the postcode. On a phone that opens the visitor's own map app, already zoomed to you, with directions one tap away.
An embedded map needs a Custom HTML block with an iframe, which loads a third party's scripts and cookies on every view. In the UK and the EU that usually means a consent banner for one map. If the building is hard to find, a Cover block with a photograph of the front door does more than a map pin: it is what the visitor will see when they arrive.
For the directions themselves, a Details block works well. Put "Parking and access" in the summary and the paragraph inside; visitors who need it open it, and everyone else reads past it. Details is a native <details> element, so it opens with a keyboard and is announced as a disclosure without any script.
Opening hours: a two-column table that fits at 390px#
A Table block with two columns, day and hours, is the clearest way to set opening times, and a screen reader announces it as a table. Keep it to two columns. A table with the days running across the top looks tidy on a desktop and is seven columns wide on a phone.
Here is the part WordPress gets wrong silently. The Table block wraps its table in a figure that scrolls sideways when the content is too wide, so a wide hours table does not break the layout; it hides Saturday and Sunday off the right edge, behind a scrollbar many phones do not show. Nothing in the editor warns you. Check it at 390px wide (browser developer tools, or your own phone) and look for the weekend.
Two more rules for the rows:
- Write closed days in. "Sunday: closed" answers the question; a missing Sunday makes the visitor wonder whether you forgot.
- Write a range with the word "to", such as "8am to 6pm", and leave out seconds and the 24-hour clock unless your customers use it.
If a table feels too heavy, a Group per day with a row layout (day on the left, hours on the right, justified apart) and a Separator between them reads as a ruled list. It costs you the table semantics, so a screen reader hears each row as two short paragraphs rather than a labelled cell.
Service area: words before a map#
If you travel to customers, the question is "do you cover me?", and the answer is a list of towns or postcodes. A List block or a Columns block of short lists, at body size, answers it for every visitor and for search engines. A map image of a shaded area answers it only for people who already know where the boundary roads are.
Put the edge cases in a sentence beneath: "Further out by arrangement" is an answer; silence sends the visitor to a competitor who wrote one.
When you do need a form plugin#
A form plugin earns its place when the enquiry has structure the business needs before it can reply:
- Quotes that need fields, such as room dimensions, a vehicle registration or a photo of the fault.
- File uploads, which
mailto:cannot carry reliably. - Bookings against real availability, where a calendar plugin or a booking service is the honest tool.
- Enquiries routed elsewhere, into a CRM, a help desk or a shared inbox by topic.
- Visitors who will not use email, such as a public sector audience on locked-down work machines.
The cost of the plugin is a script, a stylesheet that may not follow your theme, spam filtering to maintain, and stored personal data you are now responsible for. If you add one, keep the phone and email buttons beside it. A form is one more way in, not a replacement for the ones that work without it.
What to do on Monday#
Open your contact page on your phone. Tap the number and the email; if either is hard to hit, swap it for a Button. Check the hours table for a hidden weekend at 390px wide, add any missing closed days, and replace an embedded map with an "Open in Maps" link. Then copy the same phone and email into the footer, so every page has them.
If you are building the section from scratch, adding a block pattern covers where pasted markup goes in the editor.
Pattern Paste's contact patterns are these sections already built in core blocks, with tappable phone and email, ruled hours and service-area lists, and no colour or font of their own; each is checked for legibility in Twenty Twenty-Five and Twenty Twenty-Four.
From the library






