glimanaDocs
/
Open Glimana →

Issue guide · Accessibility

Accessibility problems found by Lighthouse

SeverityInfo
CategoryAccessibility
ScopeWhole site
EffortMedium
Verified byRe-crawl after you mark the task done
Rule keyaccessibility_lighthouse

Short answer

Glimana runs Lighthouse (mobile) on your home page and most-clicked pages once a week and reports five accessibility checks that have a clear, page-level fix: colour contrast, image alt text, form field labels, a main landmark and link names. These problems make the page hard or impossible to use for people who rely on screen readers, keyboard navigation or zoom. Accessibility is not a direct ranking factor, but alt text and link names overlap with what search engines read, and many jurisdictions now require it by law. Fix the failing checks listed in the evidence.

Why it matters

Someone using a screen reader cannot tell what an unlabeled image shows or what an unlabeled input expects; someone with low vision cannot read 3:1 grey-on-grey text. These five checks are the ones where the fix is unambiguous; the full axe-core rule set produces many more findings, which Glimana deliberately does not report as issues because they tend to be noisy.

How Glimana detects it

Each week Glimana runs Lighthouse with the mobile strategy on the home page and the pages with the most clicks (up to 300 runs in the last 14 days, latest run per page). From the accessibility audits it keeps only color-contrast, image-alt, label, landmark-one-main and link-name. The evidence lists the failing checks per page with example elements.

How to fix it

  1. Find the affected pages in Glimana. Open Issues › Accessibility problems found by Lighthouse. The evidence lists, per page, which of the five checks failed and an example element for each, so you can jump straight to the offending markup.

  2. Apply the fix on your platform.

    Check What it means Fix
    color-contrast Text is lighter than 4.5:1 against its background (3:1 for large text) Darken the text or lighten the background; check with a contrast tool
    image-alt <img> has no alt attribute Describe the image; use alt="" for purely decorative images
    label A form field has no associated label Add <label for="id"> or aria-label
    landmark-one-main The page has no <main> landmark Wrap the primary content in <main>
    link-name A link has no accessible text (icon-only, empty) Add visible text or aria-label

    Contrast and landmarks come from the theme (customise colours; most block themes include <main>). Alt text is set per image in the Media Library. Icon links in menus and social widgets need an aria-label; the Accessibility Checker plugin flags them in the editor.

    Dawn passes these checks by default; failures usually come from custom colour settings (contrast), product images without alt (set alt text in the product's media), and app-injected icon buttons. Add aria-label to icon-only links in the theme.

    Run axe DevTools or Lighthouse locally while fixing; add eslint-plugin-jsx-a11y or an axe check in CI so the five rules cannot regress.

  3. Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with curl -s https://your-domain/page | grep -i '<title\|canonical\|robots' that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached.

  4. Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when the next weekly Lighthouse run no longer reports the listed checks on the affected pages. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.

How the fix is verified

The task closes when the next weekly Lighthouse run no longer reports the listed checks on the affected pages.

Sources