AccessMate vs Contact Form 7

AccessMate scans your WordPress site for accessibility issues against WCAG 2.0, 2.1, 2.2, and Section 508 — pick a single standard or combine several — scores each page, and provides guided fixes, all from your WordPress dashboard. Zero running cost for you. AccessMate is 100% free. AI features (auto alt-text, code fixes, plain-English explanations) use your own API key from Anthropic, OpenAI, Google Gemini, or a local Ollama instance. Your key is stored encrypted in your database and never proxied through our servers. Core features Accessibility scanner — powered by axe-core, scans every page against your choice of WCAG standard, or several combined at once Score & grade — A–F accessibility score, weighted across Critical/Serious/Warning/Notice severity tiers, with POUR (Perceivable, Operable, Understandable, Robust) breakdown Issue detail panel — shows the offending HTML, WCAG criterion, and affected element count Issues by page — stacked bar chart showing critical/serious/warning/notice counts per page Accessibility statement generator — creates a public accessibility statement page for your site Visitor accessibility toolbar — floating widget with 10 user-controlled accessibility features AI auto-fix (requires API key) — generates corrected HTML for fixable issues AI alt text (requires API key) — writes descriptive alt text for images AI explanations (requires API key) — plain-English summaries for non-technical site owners WCAG standards & rulesets AccessMate scans with axe-core, the same open-source accessibility testing engine used by major browser DevTools. Pick any one of the following from the ruleset selector in the scanner or in Settings, or combine a standard with Best Practice: WCAG 2.0 — A, AA, or AAA WCAG 2.1 — A, AA, or AAA WCAG 2.2 — AA Section 508 Best Practice — common accessibility recommendations beyond the WCAG spec Visitor accessibility toolbar features Font size · High contrast · Dyslexia font · Grayscale · Reading guide · Pause animations · Line height · Large cursor · Highlight links · Screen mask AI providers supported Anthropic Claude (claude-haiku-4-5, claude-sonnet-4) OpenAI (gpt-4o-mini, gpt-4o) Google Gemini (gemini-1.5-flash, gemini-1.5-pro) Ollama (local, no key needed — llama3.2, mistral, phi3) Privacy AccessMate makes no external requests unless you configure an AI provider and trigger an AI action. When an AI action is triggered, your WordPress server makes a direct request to your chosen provider using your key. No data passes through AccessMate servers. The API key is encrypted at rest using AES-256-CBC with your WordPress auth salt. Third Party Libraries axe-core by Deque Systems — Mozilla Public License 2.0 (MPL-2.0) Freemius WordPress SDK — GNU General Public License v3 (GPLv3) — Pro build only OpenDyslexic font via Fontsource — Bitstream Vera Fonts License — loaded on demand from jsDelivr CDN only when the dyslexia font feature is enabled by the visitor External Services This plugin can connect to the following external services. No external requests are made unless you explicitly configure and trigger the relevant feature. AI providers (optional) When you add an API key and click an AI action (auto-fix suggestion, alt-text generation, or accessibility report summary), your WordPress server sends a direct HTTPS request to your chosen AI provider. The request contains the page HTML snippet and accessibility issue context being analysed. No data passes through AccessMate servers. These requests are only sent when you have entered an API key in Settings and manually trigger an AI action. Anthropic — https://api.anthropic.com/ Used for: AI fix suggestions, alt-text generation, accessibility report summaries. Data sent: page HTML snippet, accessibility issue context, and your Anthropic API key (in the request header). Terms of Service | Privacy Policy OpenAI — https://api.openai.com/ Used for: AI fix suggestions, alt-text generation, accessibility report summaries. Data sent: page HTML snippet, accessibility issue context, and your OpenAI API key (in the request header). Terms of Service | Privacy Policy Google Gemini — https://generativelanguage.googleapis.com/ Used for: AI fix suggestions, alt-text generation, accessibility report summaries. Data sent: page HTML snippet, accessibility issue context, and your Gemini API key (as a URL parameter). Terms of Service | Privacy Policy Ollama — http://localhost:11434/ (local only) Ollama runs entirely on the user’s own machine or local network. No data is sent to any external server. jsDelivr CDN (visitor-facing, on demand) When a site visitor enables the Dyslexia Font feature in the accessibility toolbar, their browser loads the OpenDyslexic font stylesheet from jsDelivr. This is a standard browser-initiated HTTP request that includes the visitor’s IP address and User-Agent string. The font is cached locally after the first load; no further requests are made on subsequent pages. This request is triggered only by the visitor explicitly toggling the dyslexia font feature — it is never loaded automatically. jsDelivr — https://cdn.jsdelivr.net/ Privacy Policy

How to use this plug-in: If you install and activate this plug-in before installing Contact Form 7, the default form created by Contact Form 7 will be accessible. If you’ve already installed Contact Form 7, you’ll want to delete the default form and create new forms using the templates available in this plug-in. Use Contact Form 7 with an accessible default form This plug-in replaces the default template that Contact Form 7 automatically generates with an accessible equivalent of that form and adds a suite of additional basic form types that you can choose from to model your new forms. The plug-in doesn’t change anything about forms that have already been built with Contact Form 7. The structure of Contact Form 7 is such that it isn’t possible for the plug-in to rewrite existing forms for improved accessibility, but it is possible to make sure that the base you have for starting a form is accessible. Contact Form 7 is actually a very accessible plug-in. It has an accessible back-end, and if you create the right template, the front-end form will have great accessibility. Since version 4.5, Contact Form 7 has included the label element; but the usage of them is limited, and isn’t the best possible method. This plug-in supplies a new default form that includes everything you need to make your default form accessible. For more information about making Contact Form 7 accessible, read how to set up an accessible form using contact form 7, by Rian Rietveld.