Guide
Lovable Site Accessibility in WordPress: A Fix List
A Lovable site converted to WordPress keeps most of its accessibility problems and loses a few of its own. The common issues are missing alt text, headings used for size instead of structure, low-contrast brand colors, buttons that are really links, and interactive components that became static markup. You fix them in three places: the image alt fields, the block markup in the Site Editor, and theme.json for color tokens. This guide gives the checks in order and the exact place to edit each one.
What changes when the site becomes a theme
In Lovable your pages are React components. Accessibility there depends on what the generated JSX contains: alt attributes, heading levels, aria-* attributes, focus handling in dialogs and menus. shadcn/ui components ship with reasonable keyboard behaviour, so a Lovable app often behaves better than its static markup suggests.
A WordPress block theme is HTML with block markup. The structure survives, the JavaScript behaviour does not. That is good for some things and bad for others.
What usually gets better: the page is server-rendered HTML, so screen readers and assistive tools see content without waiting for scripts. Navigation becomes a real WordPress navigation block with a standard mobile toggle. Forms become Contact Form 7 markup with labels.
What usually gets worse: anything that depended on React state. Tabs, modals, dropdowns and accordions convert as their default state only, so the hidden panels are either visible or absent, not toggleable. Animations land on their final state. Our supported features page lists the full split.
Run the checks in this order
Do the structural checks first. Fixing headings and alt text changes what every other test reports, so there is no point tuning contrast before the outline is right.
Work on one page at a time, starting with the homepage and the page that gets your contact form.
- Check the heading outline. Open the page in the Site Editor (
Appearance → Editor), open the list view, and read the headings top to bottom. One H1 per page, then H2 for sections, H3 inside them. No skipped levels. - Check every image for alt text. Select each image block and fill the
Alternative textfield. Leave it empty only for images that are purely decorative. - Check link and button text. Every link should make sense read on its own. Replace "Read more" and "Click here" with the destination.
- Check color contrast. Body text needs enough contrast against its background. Test your brand colors before you test anything else, because they repeat on every page.
- Check keyboard order. Press
Tabfrom the top of the page. The focus ring should move through header, navigation, content and footer in visual order, and never disappear. - Check the form. Every field needs a visible label, and errors need to be readable as text, not only as a red border.
Fix alt text, headings and labels
Alt text is the most common gap in a converted site, because Lovable projects often use images without an alt attribute. The converter copies images into the theme, but it cannot invent a description. Add them in the editor: select the image block, open the block settings sidebar, fill Alternative text. One short sentence that says what the image shows. If the image repeats text that is already next to it, leave alt empty so screen readers skip it.
Headings are the second gap. In Tailwind markup it is easy to write a div with text-4xl where a heading belongs, or an h3 chosen because it looked the right size. In WordPress, change the level in the block toolbar, then restyle it in theme.json or with the block's typography settings. Size and level are separate decisions.
Link labels matter more than they look. A card that is entirely clickable in React often converts to a heading, a paragraph and a button. Give the button a label that names the destination: "Read the pricing guide", not "More".
Site logo images need alt text too. If your logo links to the homepage, the alt text should say the site name, not the word "logo".
Contrast and focus come from theme.json
The converter writes your Tailwind palette into theme.json as named color tokens. That is the single place to change a color everywhere. Edit it in the theme files, or use Appearance → Editor → Styles for the same tokens through the interface.
Two pairs are worth testing by hand: body text on the page background, and button text on the button background. Muted gray on white is the usual failure, because a Tailwind text-gray-400 that looked fine in a design mockup is often too light for body copy.
Focus styles disappear more often than they fail. If a Lovable project removed the default outline for looks, the converted theme can inherit the same rule. Make sure focused links and buttons get a visible ring that contrasts with both the element and the page. Keyboard users and screen magnifier users need it to know where they are.
Do not rely on color alone to carry meaning. Required fields, error states and active navigation items need text or an icon as well as a color change.
Interactive components that need a decision
These are the pieces where the conversion is honest but incomplete. Each one needs you to choose a replacement, not just a style fix.
Accordions convert to the WordPress details block, which is a real native disclosure and keyboard accessible. Tabs, modals and dropdowns do not have a native equivalent, so they arrive as their default state. Decide per component: flatten it into normal sections, or add a plugin or block that provides an accessible version.
Carousels convert as approximations. A carousel is hard to make accessible anyway, so moving to a plain grid of items is often the better outcome rather than a loss.
Anything built on custom React state and event handlers is not converted at all. If the component was central to the site, it needs a developer, a plugin, or a rethink. Converter vs manual rebuild vs headless covers how to decide.
Carry over any lang setting. The converter writes the page language and hreflang, which tells screen readers which pronunciation to use. Check it is right if your site is not in English.
- Accordions — become the details block, keyboard accessible out of the box.
- Tabs — default panel only; flatten into sections with headings, or add a block that handles them.
- Modals — the dialog content is static; move it to its own page or an inline section.
- Dropdown menus — the header navigation block handles its own submenus; custom dropdowns do not survive.
- Animated reveals — land on their final state, which removes a motion problem rather than creating one.
Where IQDesk fits
Our converter builds the theme and shows it next to your original site in WordPress Playground, in the browser. That side-by-side view is the fastest way to spot structural differences before you install anything: a heading that lost its level, an image that moved, a button that became plain text.
The AI fix agent can read your source project and edit the theme. Accessibility instructions work well because they are concrete. Try "Change the card titles on the services page from paragraphs to h3 headings" or "Make the muted text color darker so it passes contrast on white". Instructions are capped at 2,000 characters and each fix runs up to 20 tool steps, so send one focused request at a time.
The agent cannot judge whether your alt text is accurate, and it will not invent descriptions of your photos. That part is yours.
Conversion, review and the theme download are free, and every account includes two free AI-fix attempts. See pricing for what credits cost beyond that.
A short launch check
Before you point the domain at WordPress, walk through the site once with the mouse put away. Tab through every page. Then zoom the browser to 200% and read the homepage.
Two WordPress settings are worth confirming at the same time, because both affect how the site is read and found.
- Page titles are unique and describe the page, not the site.
- Alt text is filled on every meaningful image, empty on decorative ones.
- Headings run H1, H2, H3 with no skipped level.
- Focus is visible on every link, button and form field.
- Form fields have visible labels, not placeholder text standing in for them.
- Settings → Reading — uncheck "Discourage search engines from indexing this site" before launch.
- Settings → Permalinks — confirm the structure so slugs read cleanly.
- Language — the site language matches the content, and hreflang is right if you have translations.
FAQ
Does converting a Lovable site to WordPress make it more accessible?
Partly. The page becomes server-rendered HTML, navigation becomes a standard WordPress navigation block, and forms get real labels through Contact Form 7. But missing alt text, wrong heading levels and low-contrast colors carry over unchanged, and interactive components that relied on React state arrive as static markup. You still need to run the checks by hand.
Where do I add alt text in a WordPress block theme?
Open Appearance then Editor, select the image block, and fill the Alternative text field in the block settings sidebar. For images inside a pattern, edit the pattern file in the theme's patterns folder or edit the page that uses it. Leave alt empty for purely decorative images so screen readers skip them.
Why did my accordion keep working but my tabs did not?
Accordions convert to the WordPress details block, which is a native HTML disclosure element with built-in keyboard support. Tabs, modals and dropdowns have no native equivalent in WordPress, so the converter keeps the default state only. You either flatten them into normal sections or add a block or plugin that provides an accessible version.
How do I fix color contrast across the whole converted site?
Edit the color tokens in theme.json, or change the same tokens under Appearance, Editor, Styles. The converter writes your Tailwind palette there, so one change applies everywhere it is used. Test body text on the page background and button text on the button background first, since those repeat on every page.
Can the IQDesk AI fix agent correct accessibility problems?
It can make structural edits, such as changing a paragraph to a heading or darkening a color token that fails contrast. Give it one specific instruction at a time; instructions are limited to 2,000 characters and each fix runs up to 20 tool steps. It cannot write accurate alt text for your photos, because it cannot judge what the image is meant to communicate.