Changeset 3766977

Timestamp:

10/26/2026 05:17:45 PM (4 hours ago)

Author:

itsmanzur

Message:

readme: add FAQs, fix inaccurate claims (rescan, fonts, same-site scanning)

File:

• accessiq/trunk/readme.txt (modified) (6 diffs)

accessiq/trunk/readme.txt

@@ -36 +36 @@
 
 **♿ WCAG 2.1 & 2.2 Accessibility Scanner**
-Run unlimited scans on any page or post URL. Get a 0–100 accessibility score, severity-ranked issues with element snippets, full scan history, and one-click rescans. Choose Level A, AA, or AAA as the target; the checks are automated and cover a subset of WCAG.
+Run unlimited scans on any page or post URL on your site. Get a 0–100 accessibility score, severity-ranked issues with element snippets, and full scan history. Choose Level A, AA, or AAA as the target; the checks are automated and cover a subset of WCAG.
 
 **🔥 Self-Hosted Click Heatmap Engine**
@@ -73 +73 @@
 **UX Designers** — Validate design decisions with real click data. Measure the impact of layout changes with before/after score tracking.
 
-**SEO Professionals** — Google uses accessibility signals as ranking factors. Accessible, well-structured content with proper headings and alt text ranks better. AccessIQ catches both.
+**SEO Professionals** — Clear heading structure, descriptive alt text and well-labelled links help both visitors and search engines understand your content. AccessIQ checks for these common problems.
 
 ---
@@ -87 +87 @@
 * **Scan History:** Full history with date, score, issue count, and WCAG level per URL
 * **Score History Chart:** Line chart showing your score over time
-* **One-click Rescan:** Re-run any scan instantly from the reports page
 * **Print Reports:** Print scan reports directly from the browser
 * **Unlimited Scans:** No limits, no paywalls, no scan credits
@@ -264 +263 @@
 = Which WCAG standard does the scanner support? =
 
-AccessIQ checks against WCAG 2.1 & 2.2 at Levels A, AA, and AAA. You can choose the target level when running each scan. WCAG 2.1 is the standard referenced by ADA, EAA (EU), and AODA (Canada) requirements. Automated checks cover a subset of the success criteria, so manual testing is still needed to claim conformance.
+AccessIQ checks against WCAG 2.1 & 2.2 at Levels A, AA, and AAA. You can choose the target level when running each scan. WCAG 2.1 Level AA is widely referenced in accessibility rules and guidance (for example EN 301 549, used for the European Accessibility Act), but requirements differ by country, so check the rules that apply to you. Automated checks cover a subset of the success criteria, so manual testing is still needed to claim conformance.
 
 = How is AccessIQ different from overlay accessibility widgets? =
@@ -305 +304 @@
 
 Use the Print Report button to print or save as PDF from your browser. AccessIQ Pro adds full PDF report generation with white-label branding.
+
+= How do I check my WordPress site for WCAG issues for free? =
+
+Install and activate AccessIQ, open **AccessIQ → WCAG Scanner**, choose the target level (A, AA or AAA) and run a scan on any page or post URL on your site. You get a 0–100 accessibility score and a list of issues ranked by severity, each with the element snippet and what to fix. Scans are unlimited and need no account. Automated checks cover a subset of WCAG, so keyboard and screen reader testing are still needed.
+
+= Is there a free, self-hosted alternative to Hotjar or Microsoft Clarity for WordPress? =
+
+AccessIQ includes click heatmaps and basic behavior analytics (sessions, bounce rate, average time on page and device split) that are stored in your own WordPress database, with no external service and no cookies used for tracking. It records click positions and session statistics, not screen recordings, so it is not a full replacement for session-replay tools.
+
+= Do I need an account or an API key to use AccessIQ? =
+
+No. The free plugin needs no account, no API key, no scan credits and no subscription. Scans, heatmaps and analytics all run on your own site.
+
+= Does AccessIQ work with WooCommerce and other plugins? =
+
+The scanner analyzes the final rendered HTML of any public page on your own site, whichever theme, page builder or plugin produced it, so shop and product pages can be scanned like any other public page. The heatmap and analytics tracker runs on front-end pages that visitors browse.
 
 = How do I get support? =
@@ -531 +546 @@
 **What we do NOT collect:** IP addresses, usernames, email addresses, cookies, or any personally identifiable information (PII).
 
-No data is sent to third-party servers. The WordPress admin loads fonts from Google Fonts (see External Services). You can delete all AccessIQ data by deactivating and deleting the plugin.
+No data is sent to third-party servers, and no external fonts or scripts are loaded. You can delete all AccessIQ data by deactivating and deleting the plugin.
 
 For heatmap and analytics tracking, we recommend adding a disclosure to your site's privacy policy informing visitors that anonymous click and session data is collected for site improvement.