Fixlight

Theme check

Is Blogtag accessible?

No automated check can say that a theme is accessible. Here is what one found: on October 27, 2026, our check of Blogtag 0.4 on its WordPress.org preview found 22 accessibility problems in the theme's own parts (its header, menus, footer and layout), 18 of them serious or critical.

We make Fixlight, a free WordPress plugin that fixes some of these problems, so we're not neutral. The measurements below are what our check found; anyone can repeat it with the same method.

What the check found

What the check found on Blogtag's preview
ProblemImpactTimesWCAGFree Fixlight plugin fixes it
Buttons with no textCritical14.1.2Yes
Links with no textSerious162.4.4Yes
Text with too little contrastSerious11.4.3No, needs a person
Heading levels skipModerate21.3.1No, needs a person
Page regions that cannot be told apartModerate1Best practiceNo, needs a person
Content outside the page regionsModerate1Best practiceNo, needs a person

How we checked: One page, the theme's home page on WordPress.org's preview (wp-themes.com), which shows the same sample posts for every theme. It was loaded in a real browser and checked with axe-core's WCAG 2.2 A and AA rules and its best practices. Problems inside the sample posts are not counted against the theme, except colour problems its styling causes. Automated checks find many problems, but not all of them. Your site, with your own content, settings and plugins, will give different results. Blogtag may have changed since October 27, 2026.

How to fix them

What the free Fixlight plugin does here

Of these, the free plugin fixes buttons with no text, links with no text on its own, in the HTML the site sends, with no widget. The rest (text with too little contrast, heading levels skip, page regions that cannot be told apart, content outside the page regions) need a change in the theme's settings or code.

About Blogtag

All theme checks