Accessibility after converting an AI website to WordPress

Why AI sites often miss accessibility basics

AI builders produce attractive pages, but accessibility is rarely their priority. In audits I regularly find buttons made from plain div elements, images without alternative text, low contrast text on gradients, headings chosen for size rather than structure, and menus that cannot be used with a keyboard. Visitors with screen readers or limited mobility simply cannot use parts of the site.

A migration to WordPress is the right moment to fix this. The content is already being reviewed, the theme is being set up, and the block editor produces mostly semantic HTML by default. With a modest extra effort, the new site can be far more accessible than the original.

Start with the heading structure

Every page should have exactly one H1 that describes its main topic, followed by H2 and H3 headings in a logical order. Screen reader users navigate by headings, the same way sighted readers scan a page. After conversion I open each template and check the outline. Headings that were only used for visual size are changed to paragraphs with a larger font, and missing levels are corrected.

This also helps search engines understand the page, so accessibility and SEO reinforce each other here.

Alternative text and meaningful images

Each informative image needs alternative text that describes its purpose, not its file name. Decorative images, such as background shapes, should have empty alternative text so screen readers skip them. During migration I go through the media library and fill in alternative text for the important images. It is repetitive work, but it is one of the most valuable accessibility improvements.

Colour contrast and readable text

Gradients and soft pastel colours are popular in AI-generated designs. They often fail contrast requirements, especially for small text. I check text and button colours with a contrast tool and adjust the design tokens in the theme settings when needed. A slightly darker shade of the brand colour usually keeps the look while making text readable for everyone.

I also make sure text can be enlarged to two hundred percent without content disappearing or overlapping.

Keyboard navigation and focus

Try using the site with only the Tab, Enter and Escape keys. Every link, button and form field should be reachable, and the focused element should be clearly visible. Menus and pop-ups must open and close with the keyboard. Converted pages sometimes keep custom interactive elements that ignore the keyboard; I replace those with standard blocks or accessible plugins.

A visible focus outline is not ugly. It is how many people find their way around the page.

Accessible forms

Forms are often rebuilt during a migration, which is an opportunity. Each field needs a visible label, not just placeholder text. Error messages should explain what is wrong and be announced to screen readers. Required fields must be indicated in text, not only by colour. Most good form plugins support this when configured properly.

Testing and maintaining accessibility

I combine automated checks with manual testing. Automated tools catch missing alternative text, contrast problems and structural errors. Manual testing with a keyboard and a screen reader catches what tools miss, such as confusing link texts or illogical reading order.

Accessibility is not a one-time task. I add a short checklist to the editorial guidelines so new pages keep the same standard: one H1, logical headings, alternative text, clear link text and sufficient contrast. Small imperfections will still appear now and then; that is normal and easy to correct once the team knows what to look for.

The business case

Accessible sites reach more people, perform better in search and reduce legal risk in many countries. More importantly, they are simply better websites. A migration from an AI builder to WordPress is the ideal moment to make that improvement without starting from zero.