Description

ScoreFix helps real visitors — not just your score. It finds common accessibility and UX issues that drag down Google Lighthouse (especially Accessibility), then applies real fixes to your HTML output: meaningful ALT text, labels for controls, and names for links and buttons. No fake overlays, no “accessibility theater.”

Why ScoreFix?

Business-first language — Issues are explained in terms of conversions, readability, and trust — not jargon.
Automatic Scan — Surfaces images without ALT, unnamed links/buttons, unlabeled fields, and basic contrast risks.
ScoreFix Score (0–100) — One number you can track after each scan.
Apply Fixes (optional) — When you turn fixes on, ScoreFix improves the markup your site outputs. The MVP applies non-destructive runtime fixes (no bulk database rewrites), so you can ship safely.

Who it is for

Non-technical WordPress owners
WooCommerce stores
Small agencies managing client sites

What makes it different

Not a generic “accessibility widget” — We don’t paint over problems; we address missing names and labels in the actual output.
Not only a checklist — Scan + prioritized issues + one-click enable for automatic fixes.
Lighthouse-aligned — Focused on changes that commonly affect Accessibility audits and real users.

Limitations (important)

ScoreFix does not guarantee legal WCAG compliance or a perfect Lighthouse score.
Semantic ALT for SEO may still need your editorial judgment.
Highly dynamic JavaScript-only interfaces may need manual work outside the plugin.
Extra scan rules (headings, landmarks, tables, media, forms, generic links) are heuristic and may miss issues or flag false positives; tune behavior with filters documented in code where applicable.

Screenshots

ScoreFix dashboard with score, issues, and actions.

Installation

Upload the plugin folder to /wp-content/plugins/scorefix/ or install the zip from the Plugins screen.
Activate ScoreFix through the Plugins menu.
Go to Settings ScoreFix, run a scan, then choose whether to enable automatic fixes.

FAQ

Will this change my database content?: The MVP applies fixes at runtime when “Apply Fixes” is on. It does not bulk-edit posts in the database.
Does it work with WooCommerce?: Yes — WooCommerce’s product post type is included in scans when that post type exists.
Is this a visual overlay?: No. ScoreFix does not rely on overlays to fake compliance.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“ScoreFix – Boost Lighthouse & Improve UX” is open source software. The following people have contributed to this plugin.

Carles

Translate “ScoreFix – Boost Lighthouse & Improve UX” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.0.10

New: 10 auto‑fix runtime handlers — video, audio, and iframe text alternatives,
grouped control labels, and missing name inferrals for accessibility gaps.
New: AI skill definitions for accessibility, performance, SEO, and WP development.
Fix: metadata fields, .distignore exclusions, and readme formatting for WordPress.org review.
Fix: Dashboard page alignment and ImagesRule ALT validation tweaks.

1.0.9

Skipped — rolled into 1.0.10.

1.0.8

Misc: maintenance release.

1.0.7

Misc: maintenance release.
Updated tested WordPress and PHP versions.

1.0.6

Score: media library is one bucket (sum of attachment-issue penalties capped at 100), not one bucket per image file — prevents hundreds of “clean” attachments from inflating the overall average when posts still have many issues. Model id per_page_average_v2.

1.0.5

Score: new default model per_page_average_v1 — each scanned post, each scanned image attachment, and each distinct rendered URL gets an internal 0–100 from its issues (penalties capped per bucket); the dashboard “Overall score” is the average of those values (still shown as 0–100). Old snapshots without scanned_post_ids keep the previous single-sum behaviour. Filters: scorefix_score_context, scorefix_calculated_score.

1.0.4

Scanner (Phase 5A): local performance heuristics on scanned HTML — images missing width/height (attrs or inline style), loading="lazy" suggestion with conservative main/first-block heuristic, and high count of <script src>. New issue types perf_*; glossary + dashboard context “Performance (HTML heuristic)”. Filters: scorefix_collect_performance_heuristics, scorefix_perf_script_src_threshold.

1.0.3

Rendered HTML scan: always part of a full scan. Background queue (WP-Cron + opening ScoreFix settings) uses built-in limits (RenderCaptureConfig: timeout, max URLs, batch size) and URL list from defaults + published posts/pages/products; merges rendered_url when done. No dashboard UI for capture tuning. Filter scorefix_skip_render_url_scan for edge cases.

1.0.2

Scanner: optional same-host loopback fetch of rendered public HTML (signed one-time token), merged into scan with source rendered_url. Settings UI for URLs, timeout, max URLs. Filter scorefix_render_capture_sslverify for local dev TLS.

1.0.1

Scanner: additional DOM heuristics (headings, landmarks, generic link text, form groups/autocomplete/required hints, video/audio/iframe, data tables). Heuristic only — not a WCAG guarantee.

1.0.0

Initial release: scanner, ScoreFix Score, admin dashboard, runtime fix engine.