[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fHq3fgaNnWm0JUpUKTNSWbEgllq0dJAog99Zjbk4NbrI":3,"$fD1u8CKTVSr6ku8Jc0hWYWm7bCTAQxZasvmmQvoWflLA":206,"$f6byF_mrGU2AmMOTdAOgN0H4pwb4brEu5w58jxiMng6E":211},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":35,"analysis":127,"fingerprints":185},"a11yfix-for-wcag","A11yFix for WCAG","1.0.0","kija3","https:\u002F\u002Fprofiles.wordpress.org\u002Fkija3\u002F","\u003Cp>A11yFix for WCAG is a WordPress admin tool for checking the accessibility of pages on your site. It is meant for site owners, developers, testers, and content editors who want to find common accessibility problems and inspect where those problems appear on real pages.\u003C\u002Fp>\n\u003Cp>The plugin opens inside the WordPress admin area under Tools. It can crawl pages from your site, remember the pages it found, run accessibility checks on those pages, and show the results in a way that is easier to review.\u003C\u002Fp>\n\u003Ch3>What This Plugin Does\u003C\u002Fh3>\n\u003Cp>In simple words, the plugin does four main jobs:\u003C\u002Fp>\n\u003Col>\n\u003Cli>It starts from your site home page and follows internal links.\u003C\u002Fli>\n\u003Cli>It stores the pages it found in your browser so you can work with them again without starting from zero every time.\u003C\u002Fli>\n\u003Cli>It runs accessibility rules against those pages.\u003C\u002Fli>\n\u003Cli>It helps you inspect problem areas in a live page view and, when possible, in the WordPress block editor view.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The plugin is focused on practical accessibility review. It does not automatically rewrite your site. Instead, it helps you discover issues, understand where they are, and review the affected content faster.\u003C\u002Fp>\n\u003Ch3>Important Thing To Know\u003C\u002Fh3>\n\u003Cp>The plugin stores crawl and test data locally in your browser. That means the saved list of pages and test results are mainly for the browser you used during testing. If you switch browser or clear browser storage, you may need to crawl and test again. This design keeps the data private and under your control, but it also means the plugin is not a centralized site-wide report tool. It is more of a personal review assistant that helps you work through accessibility issues in a structured way.\u003C\u002Fp>\n\u003Ch3>Main Workflow\u003C\u002Fh3>\n\u003Cp>The normal workflow is usually this:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Open the A11yFix for WCAG page in WordPress admin.\u003C\u002Fli>\n\u003Cli>Choose a depth limit.\u003C\u002Fli>\n\u003Cli>Click Start crawl to collect internal pages.\u003C\u002Fli>\n\u003Cli>Click Run test to move into testing.\u003C\u002Fli>\n\u003Cli>Review the results in Test results.\u003C\u002Fli>\n\u003Cli>Open a page in Rules view to see where the failed elements are.\u003C\u002Fli>\n\u003Cli>Switch to the WordPress editor view when available to compare the live page with editor blocks.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>What Each Tab Is For\u003C\u002Fh3>\n\u003Ch3>Crawled Pages Tab\u003C\u002Fh3>\n\u003Cp>This is the starting tab. It shows the pages the plugin found while crawling your site.\u003C\u002Fp>\n\u003Cp>This tab is needed because the plugin first needs a list of pages before it can run accessibility checks in a structured way.\u003C\u002Fp>\n\u003Cp>What you see here:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A depth setting.\u003C\u002Fli>\n\u003Cli>Buttons for crawl and test actions.\u003C\u002Fli>\n\u003Cli>A table of stored pages.\u003C\u002Fli>\n\u003Cli>Common layout detection information.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>What the common layout detection section means:\u003C\u002Fp>\n\u003Cp>The plugin tries to detect parts that are probably shared across many pages, such as the site header and footer. This is useful because repeated layout parts often create repeated accessibility problems across the whole site.\u003C\u002Fp>\n\u003Ch3>Test Tab\u003C\u002Fh3>\n\u003Cp>This tab is used to load pages into a preview iframe and run accessibility checks. Think of it as the active testing area.\u003C\u002Fp>\n\u003Cp>This tab is needed because the plugin needs a controlled page preview area where it can open one stored page at a time and evaluate it.\u003C\u002Fp>\n\u003Cp>What you see here:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A preview frame with the selected page.\u003C\u002Fli>\n\u003Cli>Buttons for running tests on one page or many pages.\u003C\u002Fli>\n\u003Cli>A button to stop a running test.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Test Results Tab\u003C\u002Fh3>\n\u003Cp>This tab shows the collected rule results for the stored pages.\u003C\u002Fp>\n\u003Cp>This tab is needed because it gives you a page-by-page summary of which accessibility rules passed or failed.\u003C\u002Fp>\n\u003Cp>What you see here:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A table with one row per stored page.\u003C\u002Fli>\n\u003Cli>A separate status cell for each rule.\u003C\u002Fli>\n\u003Cli>An action button called View and Fix.\u003C\u002Fli>\n\u003Cli>A scope toggle button.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Rules View Tab\u003C\u002Fh3>\n\u003Cp>This tab shows a page inside another preview area and can highlight the elements that failed a selected rule.\u003C\u002Fp>\n\u003Cp>This tab is needed because summary tables alone do not show exactly where the problem is on the page. Rules view helps you visually inspect the failing elements.\u003C\u002Fp>\n\u003Cp>What you see here:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Rule filter buttons.\u003C\u002Fli>\n\u003Cli>A Retest page button.\u003C\u002Fli>\n\u003Cli>A button to switch between the live page and the WordPress editor view.\u003C\u002Fli>\n\u003Cli>In some cases, buttons for viewing or sending an anonymous sample.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>What Each Button And Control Does\u003C\u002Fh3>\n\u003Ch3>Depth Limit\u003C\u002Fh3>\n\u003Cp>This number controls how far away from the home page the crawler is allowed to follow links.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Depth 0 usually means only the starting page.\u003C\u002Fli>\n\u003Cli>Depth 1 means pages linked directly from the starting page.\u003C\u002Fli>\n\u003Cli>Depth 2 goes one level deeper.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This control is needed so you can keep the crawl small and focused, or make it broader when needed.\u003C\u002Fp>\n\u003Ch3>Start Crawl\u003C\u002Fh3>\n\u003Cp>This button starts collecting internal pages from your site beginning at the home page.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Opens the crawl process.\u003C\u002Fli>\n\u003Cli>Follows allowed internal links.\u003C\u002Fli>\n\u003Cli>Ignores blocked WordPress paths that should not be tested like normal content pages.\u003C\u002Fli>\n\u003Cli>Saves the discovered pages locally in the browser.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed to build the page list before testing.\u003C\u002Fp>\n\u003Ch3>Run Test\u003C\u002Fh3>\n\u003Cp>This button appears in the Crawled pages tab.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Starts running accessibility checks on the stored crawled pages.\u003C\u002Fli>\n\u003Cli>Uses the preview\u002Ftesting flow instead of only showing the crawl list.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed to move from page discovery into accessibility checking.\u003C\u002Fp>\n\u003Ch3>Clear Crawled Pages\u003C\u002Fh3>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Removes the stored page list from the browser.\u003C\u002Fli>\n\u003Cli>Clears the crawl data so you can start fresh.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed when the crawl list is outdated, incorrect, or you want a clean new scan.\u003C\u002Fp>\n\u003Ch3>Run All\u003C\u002Fh3>\n\u003Cp>This button is in the Test tab.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Runs the accessibility test across the available stored pages.\u003C\u002Fli>\n\u003Cli>Continues page by page until it finishes or you stop it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed for full-site or multi-page review.\u003C\u002Fp>\n\u003Ch3>Run\u003C\u002Fh3>\n\u003Cp>This button is also in the Test tab.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Runs the test only for the page currently loaded in the preview iframe.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed when you only want to retest one page instead of everything.\u003C\u002Fp>\n\u003Ch3>Stop Test\u003C\u002Fh3>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Stops a running test session.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed when testing takes too long, the selected page is wrong, or you want to interrupt the current run.\u003C\u002Fp>\n\u003Ch3>Clear Test Results\u003C\u002Fh3>\n\u003Cp>This button is in the Test results tab.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Removes saved rule results from the browser.\u003C\u002Fli>\n\u003Cli>Keeps you from mixing old test results with new ones.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed when you want to retest from a clean state.\u003C\u002Fp>\n\u003Ch3>Scope Toggle Button\u003C\u002Fh3>\n\u003Cp>The label changes between Scope: page only and Scope: all.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Changes how rule failures are displayed in the results table.\u003C\u002Fli>\n\u003Cli>In page-only mode, the plugin focuses on problems that belong to the current page.\u003C\u002Fli>\n\u003Cli>In all mode, the plugin can show the broader failure state without limiting the view so strictly to the page-level scope.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed because sometimes you want a narrow page-specific view, and sometimes you want the wider rule result picture.\u003C\u002Fp>\n\u003Ch3>Rule Buttons In Rules View\u003C\u002Fh3>\n\u003Cp>These are the buttons such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Images alt\u003C\u002Fli>\n\u003Cli>Links\u003C\u002Fli>\n\u003Cli>Heading order\u003C\u002Fli>\n\u003Cli>Form labels\u003C\u002Fli>\n\u003Cli>ARIA and accessible names\u003C\u002Fli>\n\u003Cli>Keyboard focusable\u003C\u002Fli>\n\u003Cli>Low contrast\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>What they do:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Turn highlighting on or off for a specific rule.\u003C\u002Fli>\n\u003Cli>Show the elements on the page that failed that rule.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These buttons are needed so you can focus on one type of problem at a time instead of looking at all failures mixed together.\u003C\u002Fp>\n\u003Ch3>What Each Rule Button Is For\u003C\u002Fh3>\n\u003Ch3>Images Alt\u003C\u002Fh3>\n\u003Cp>Used to inspect images with missing, empty, or otherwise problematic alternative text.\u003C\u002Fp>\n\u003Ch3>Links\u003C\u002Fh3>\n\u003Cp>Used to inspect links that do not have a clear accessible name or meaningful text.\u003C\u002Fp>\n\u003Ch3>Heading Order\u003C\u002Fh3>\n\u003Cp>Used to inspect heading structure problems, such as skipped heading levels or confusing page outline order.\u003C\u002Fp>\n\u003Ch3>Form Labels\u003C\u002Fh3>\n\u003Cp>Used to inspect form controls that are missing labels or have labeling problems.\u003C\u002Fp>\n\u003Ch3>ARIA And Accessible Names\u003C\u002Fh3>\n\u003Cp>Used to inspect problems where ARIA attributes and the visible or computed accessible name do not work well together.\u003C\u002Fp>\n\u003Cp>This area groups checks related to how controls are named for assistive technology.\u003C\u002Fp>\n\u003Ch3>Keyboard Focusable\u003C\u002Fh3>\n\u003Cp>Used to inspect interactive-looking elements that are not properly keyboard accessible, or similar focus and keyboard behavior problems.\u003C\u002Fp>\n\u003Ch3>Low Contrast\u003C\u002Fh3>\n\u003Cp>Used to inspect text or UI parts that may not have enough color contrast.\u003C\u002Fp>\n\u003Ch3>Retest Page\u003C\u002Fh3>\n\u003Cp>This button is in Rules view.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Runs the checks again for the page currently open in Rules view.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed after you make a content or code change and want to verify that one page again.\u003C\u002Fp>\n\u003Ch3>View In WP Editor\u003C\u002Fh3>\n\u003Cp>This button appears in Rules view when an editor view is available for the current page.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Switches the Rules view iframe from the live page to the WordPress block editor view.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Why this is useful:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The live page shows the real output visitors see.\u003C\u002Fli>\n\u003Cli>The editor view helps you compare those failing areas with editable blocks.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When the plugin is already showing the editor, this button changes to View live so you can switch back.\u003C\u002Fp>\n\u003Ch3>View Live\u003C\u002Fh3>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Switches back from the editor view to the live frontend page.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed so you can compare frontend output and backend editor structure.\u003C\u002Fp>\n\u003Ch3>View Before Send\u003C\u002Fh3>\n\u003Cp>This button is normally hidden and only appears in special cases.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Opens a preview of the anonymous sample data the plugin is preparing.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed so a user can review what would be shared before sending anything.\u003C\u002Fp>\n\u003Ch3>Send Data\u003C\u002Fh3>\n\u003Cp>This button is also normally hidden and appears only in special situations, for example when the plugin detects a problem that the developers may want a sample for.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Sends an anonymous diagnostic sample to the configured sample endpoint.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed for debugging difficult mapping or inspection problems without sending the full site content in a normal manual report.\u003C\u002Fp>\n\u003Ch3>Status Line\u003C\u002Fh3>\n\u003Cp>At the top of the plugin there is a status message area that shows messages like Ready, running states, switching states, or errors.\u003C\u002Fp>\n\u003Cp>This is needed so the user can see what the plugin is doing right now.\u003C\u002Fp>\n\u003Ch3>What The Tables And Clickable Items Do\u003C\u002Fh3>\n\u003Ch3>Links In The Crawled Pages Table\u003C\u002Fh3>\n\u003Cp>The URL in each Crawled pages row is clickable.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Opens that stored page in the Test tab preview area.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This is needed for quick page selection.\u003C\u002Fp>\n\u003Ch3>Information In The Crawled Pages Table\u003C\u002Fh3>\n\u003Cp>Each row shows:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>URL\u003C\u002Fli>\n\u003Cli>Depth\u003C\u002Fli>\n\u003Cli>ID\u003C\u002Fli>\n\u003Cli>Crawled date and time\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This information helps you understand where the page was found, what content record it belongs to, and when it was last crawled.\u003C\u002Fp>\n\u003Ch3>Rule Status Cells In Test Results\u003C\u002Fh3>\n\u003Cp>Each rule column shows a result for that page.\u003C\u002Fp>\n\u003Cp>Typical meanings:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Pass means the rule did not find a problem for that page.\u003C\u002Fli>\n\u003Cli>Fail means the rule found one or more issues.\u003C\u002Fli>\n\u003Cli>Some cells can act like detail triggers so you can inspect the failed items for that rule.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These cells are needed so you can scan many pages quickly and open details only where needed.\u003C\u002Fp>\n\u003Ch3>View And Fix\u003C\u002Fh3>\n\u003Cp>This button is in the Test results table.\u003C\u002Fp>\n\u003Cp>What it does:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Opens the selected page in Rules view.\u003C\u002Fli>\n\u003Cli>Prepares the plugin for visual inspection and highlighting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This button is needed because it connects the summary table to the detailed inspection view.\u003C\u002Fp>\n\u003Ch3>What Kinds Of Accessibility Checks This Plugin Covers\u003C\u002Fh3>\n\u003Cp>Based on the current interface, the plugin checks areas such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Image alternative text\u003C\u002Fli>\n\u003Cli>Link naming and empty links\u003C\u002Fli>\n\u003Cli>Heading structure\u003C\u002Fli>\n\u003Cli>Form labels\u003C\u002Fli>\n\u003Cli>Accessible name source problems\u003C\u002Fli>\n\u003Cli>aria-labelledby integrity problems\u003C\u002Fli>\n\u003Cli>aria-hidden on interactive elements\u003C\u002Fli>\n\u003Cli>Keyboard focusability and keyboard interaction issues\u003C\u002Fli>\n\u003Cli>Low color contrast\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>What This Plugin Is Especially Good For\u003C\u002Fh3>\n\u003Cp>This plugin is useful when you want to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Crawl many internal pages quickly.\u003C\u002Fli>\n\u003Cli>Keep a browser-local testing history.\u003C\u002Fli>\n\u003Cli>Re-run checks after making fixes.\u003C\u002Fli>\n\u003Cli>See exactly where problem elements are located.\u003C\u002Fli>\n\u003Cli>Compare live content with WordPress editor blocks.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>What This Plugin Does Not Mainly Do\u003C\u002Fh3>\n\u003Cp>This plugin is not mainly a one-click auto-fixer. Its main strength is guided inspection, review, and retesting.\u003C\u002Fp>\n\u003Ch3>Short Summary\u003C\u002Fh3>\n\u003Cp>A11yFix is a WordPress accessibility review tool. It finds internal pages, runs accessibility rules, shows a results summary, and lets you inspect failing elements directly on the page. The tabs split the work into four stages: collecting pages, testing pages, reviewing results, and visually locating issues.\u003C\u002Fp>\n","A11yFix for WCAG is a WordPress admin tool for checking the accessibility of pages on your site. It is meant for site owners, developers, testers, and …",0,80,"2026-03-25T17:30:00.000Z","6.9.4","6.4","7.4",[18,19,20,21,22],"accessibility","admin-tools","audit","testing","wcag","https:\u002F\u002Fin3.dev\u002Fa11yfix\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fa11yfix-for-wcag.1.0.0.zip",100,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,94,"2026-05-20T08:24:25.382Z",[36,54,72,87,109],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":25,"num_ratings":31,"last_updated":46,"tested_up_to":14,"requires_at_least":47,"requires_php":48,"tags":49,"homepage":52,"download_link":53,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"sa11y","Sa11y, the accessibility quality assurance assistant | Accessibility Checker","1.2.7","Adam Chaboryk","https:\u002F\u002Fprofiles.wordpress.org\u002Fadamchaboryk\u002F","\u003Cp>Sa11y is an accessibility quality assurance tool that visually highlights common accessibility and usability issues. Geared towards content authors, Sa11y straightforwardly identifies errors or warnings at the source with a simple tooltip on how to fix them.\u003C\u002Fp>\n\u003Cp>Sa11y works in \u003Cstrong>Preview\u003C\u002Fstrong> mode.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Over 80 checks.\u003C\u002Fli>\n\u003Cli>Concise tooltips explain issues right at the source.\u003C\u002Fli>\n\u003Cli>Automatically checks content once the page has loaded.\u003C\u002Fli>\n\u003Cli>Highly customizable. Turn off or hide irrelevant checks.\u003C\u002Fli>\n\u003Cli>Content editors can temporarily dismiss warnings.\u003C\u002Fli>\n\u003Cli>100% free and open source.\u003C\u002Fli>\n\u003Cli>Available in English, French, Spanish, Polish, Ukrainian, German, Swedish, and many more languages through machine translations.\u003C\u002Fli>\n\u003Cli>Supports Multisite: create global settings and custom defaults for all websites on your network.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Visit the \u003Ca href=\"https:\u002F\u002Fsa11y.netlify.app\u002F\" rel=\"nofollow ugc\">project website\u003C\u002Fa> for a demo or to learn more!\u003C\u002Fp>\n","Geared towards content authors, Sa11y straightforwardly identifies accessibility issues at the source.",300,14864,"2025-12-18T21:05:00.000Z","5.6","7.2",[18,50,51,20,22],"accessibility-automated-testing","accessibility-checker","https:\u002F\u002Fsa11y.netlify.app\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsa11y.1.2.7.zip",{"slug":55,"name":56,"version":57,"author":58,"author_profile":59,"description":60,"short_description":61,"active_installs":44,"downloaded":62,"rating":33,"num_ratings":63,"last_updated":64,"tested_up_to":14,"requires_at_least":65,"requires_php":66,"tags":67,"homepage":66,"download_link":71,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"xcompliant","XCompliant – Accessibility Scan & Audit","1.0.11","XCompliant","https:\u002F\u002Fprofiles.wordpress.org\u002Fxcompliant\u002F","\u003Cp>XCompliant is an accessibility scanning and audit plugin designed to help WordPress site owners identify common accessibility issues and improve usability for a wider range of users.\u003C\u002Fp>\n\u003Cp>The plugin analyzes selected pages and content elements and highlights potential accessibility concerns based on established accessibility best practices, including WCAG-related guidelines.\u003C\u002Fp>\n\u003Cp>XCompliant is intended to support accessibility review and improvement efforts. The results provided are informational and do not constitute legal advice, certification, or a guarantee of compliance with any specific law or regulation.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Automated accessibility scans for selected pages\u003C\u002Fli>\n\u003Cli>Issue summaries grouped by category\u003C\u002Fli>\n\u003Cli>Accessibility insights related to structure, text alternatives, and navigation\u003C\u002Fli>\n\u003Cli>Ongoing scans for newly added or updated content\u003C\u002Fli>\n\u003Cli>Optional accessibility interface for end users\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>What XCompliant Does\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>XCompliant analyzes page content and interface elements to help identify potential accessibility-related issues, including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Missing or incomplete alternative text\u003C\u002Fli>\n\u003Cli>Interactive elements that may require improved labeling\u003C\u002Fli>\n\u003Cli>Navigation and keyboard interaction patterns\u003C\u002Fli>\n\u003Cli>Common UI and structural accessibility concerns\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin may apply session-based adjustments through an optional accessibility interface that allows users to customize their viewing experience.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Accessibility Standards\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>XCompliant references established accessibility guidelines, including WCAG 2.x-related principles, to help surface potential issues. Accessibility requirements vary by jurisdiction and context, and manual testing is strongly recommended in addition to automated tools.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How It Works\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Install and activate the XCompliant plugin.\u003C\u002Fli>\n\u003Cli>Register an account to enable scanning features.\u003C\u002Fli>\n\u003Cli>Select pages or allow automated scans to review accessibility-related findings.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Scans may take time to complete depending on site size and content.\u003C\u002Fp>\n","XCompliant is an accessibility scanning and audit plugin designed to help WordPress site owners identify common accessibility issues and improve usabi …",6835,31,"2026-04-03T14:33:00.000Z","5.2","",[18,68,69,70,22],"accessibility-audit","accessibility-scan","ada","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fxcompliant.1.0.11.zip",{"slug":73,"name":74,"version":75,"author":76,"author_profile":77,"description":78,"short_description":79,"active_installs":11,"downloaded":80,"rating":11,"num_ratings":11,"last_updated":81,"tested_up_to":14,"requires_at_least":82,"requires_php":16,"tags":83,"homepage":66,"download_link":86,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"wally-monitor","Wally Monitor","1.5.4","equallyze","https:\u002F\u002Fprofiles.wordpress.org\u002Fequallyze\u002F","\u003Cp>\u003Cstrong>Wally Monitor\u003C\u002Fstrong> is a comprehensive accessibility auditing plugin that helps you identify and fix accessibility issues on your WordPress website. Built on top of axe-core (the industry-standard accessibility testing engine), it provides detailed reports and actionable insights to make your site accessible to everyone.\u003C\u002Fp>\n\u003Ch4>📚 Third-Party Libraries\u003C\u002Fh4>\n\u003Cp>This plugin uses the following open-source libraries:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>axe-core v4.11.1\u003C\u002Fstrong> – Accessibility testing engine by Deque Systems\u003Cbr \u002F>\nSource: https:\u002F\u002Fgithub.com\u002Fdequelabs\u002Faxe-core\u003Cbr \u002F>\nLicense: MPL-2.0\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Chart.js v4.5.1\u003C\u002Fstrong> – JavaScript charting library\u003Cbr \u002F>\nSource: https:\u002F\u002Fgithub.com\u002Fchartjs\u002FChart.js\u003Cbr \u002F>\nLicense: MIT\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>FPDF 1.86\u003C\u002Fstrong> – PHP PDF generation library (modified with Wally_ prefix to avoid conflicts)\u003Cbr \u002F>\nSource: http:\u002F\u002Fwww.fpdf.org\u002F\u003Cbr \u002F>\nLicense: Free for personal and commercial use\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🎯 Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Automated Full Site Scanning\u003C\u002Fstrong> – Analyze all pages, posts, and custom post types in one click\u003C\u002Fli>\n\u003Cli>\u003Cstrong>208+ Accessibility Rules\u003C\u002Fstrong> – ~90 axe-core rules + 13 WordPress-specific + 48 NBR 17.225 + 57 IF-THEN exclusive checks\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Real-time WCAG Score\u003C\u002Fstrong> – Track your accessibility score from 0-100\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SEO Integration\u003C\u002Fstrong> – Shows accessibility impact directly in Yoast SEO and Rank Math meta boxes\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Block-Specific Detection\u003C\u002Fstrong> – Identifies issues in WordPress Gutenberg blocks (images, buttons, headings, etc.)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Historical Tracking\u003C\u002Fstrong> – Monitor progress over time with interactive charts\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Editor Integration\u003C\u002Fstrong> – Analyze content while editing posts and pages\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Professional Reports\u003C\u002Fstrong> – Clean, visual dashboards with detailed violation breakdowns\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WCAG Level Detection\u003C\u002Fstrong> – Categorizes issues by WCAG A, AA, AAA conformance levels\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🔍 What Does It Check?\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Images & Media\u003C\u002Fstrong>\u003Cbr \u002F>\n* Missing alt attributes\u003Cbr \u002F>\n* Empty alt text\u003Cbr \u002F>\n* Gallery accessibility\u003Cbr \u002F>\n* Video captions\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Forms\u003C\u002Fstrong>\u003Cbr \u002F>\n* Missing labels\u003Cbr \u002F>\n* Fieldset accessibility\u003Cbr \u002F>\n* Form validation\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Structure & Semantics\u003C\u002Fstrong>\u003Cbr \u002F>\n* Heading hierarchy\u003Cbr \u002F>\n* Landmark regions\u003Cbr \u002F>\n* Navigation structure\u003Cbr \u002F>\n* HTML validity\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Color & Contrast\u003C\u002Fstrong>\u003Cbr \u002F>\n* Color contrast ratios (WCAG AA\u002FAAA)\u003Cbr \u002F>\n* Text readability\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Interactive Elements\u003C\u002Fstrong>\u003Cbr \u002F>\n* Button labels\u003Cbr \u002F>\n* Link descriptions\u003Cbr \u002F>\n* Keyboard navigation\u003Cbr \u002F>\n* Focus indicators\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WordPress Specific\u003C\u002Fstrong>\u003Cbr \u002F>\n* Cover block contrast\u003Cbr \u002F>\n* Site logo alt text\u003Cbr \u002F>\n* Search widget labels\u003Cbr \u002F>\n* Embed titles\u003Cbr \u002F>\n* Custom HTML warnings\u003C\u002Fp>\n\u003Ch4>🚀 Why Accessibility Matters\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Legal Compliance\u003C\u002Fstrong> – Meet ADA, Section 508, and WCAG 2.2 requirements\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Better SEO\u003C\u002Fstrong> – Google prioritizes accessible websites in search rankings\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Wider Audience\u003C\u002Fstrong> – Reach 15%+ of users with disabilities\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Improved UX\u003C\u002Fstrong> – Accessible sites work better for everyone\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Brand Reputation\u003C\u002Fstrong> – Show you care about all users\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>💼 Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Marketing agencies managing multiple client sites\u003C\u002Fli>\n\u003Cli>Web developers building accessible themes\u002Fplugins\u003C\u002Fli>\n\u003Cli>Content creators ensuring inclusive content\u003C\u002Fli>\n\u003Cli>E-commerce stores reaching wider audiences\u003C\u002Fli>\n\u003Cli>Government and educational institutions\u003C\u002Fli>\n\u003Cli>Anyone committed to web accessibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🎨 Clean, Modern Interface\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Large, professional logo display\u003C\u002Fli>\n\u003Cli>Color-coded severity indicators\u003C\u002Fli>\n\u003Cli>Interactive violation cards with Quick Fix suggestions\u003C\u002Fli>\n\u003Cli>Mobile-responsive design\u003C\u002Fli>\n\u003Cli>WordPress admin design standards\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🔌 Integrations\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Yoast SEO\u003C\u002Fstrong> – Accessibility analysis in SEO meta box\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rank Math\u003C\u002Fstrong> – Integrated accessibility scores\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gutenberg\u003C\u002Fstrong> – Block-level issue detection\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Classic Editor\u003C\u002Fstrong> – Full compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>📊 Technical Details\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Built on axe-core 4.11.1 (Deque Systems)\u003C\u002Fli>\n\u003Cli>No external API calls – all processing happens locally\u003C\u002Fli>\n\u003Cli>No data collection or tracking\u003C\u002Fli>\n\u003Cli>Lightweight and optimized for performance\u003C\u002Fli>\n\u003Cli>Works with any WordPress theme\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🌐 Supported Languages\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>Portuguese (Brazil) – Interface em Português\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy & Data\u003C\u002Fh3>\n\u003Cp>Wally Monitor does NOT:\u003Cbr \u002F>\n* Collect any user data\u003Cbr \u002F>\n* Send information to external servers\u003Cbr \u002F>\n* Track user behavior\u003Cbr \u002F>\n* Require registration or API keys\u003Cbr \u002F>\n* Display advertisements\u003C\u002Fp>\n\u003Cp>All accessibility analysis happens locally in your WordPress installation using the axe-core JavaScript library.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For support, feature requests, or bug reports:\u003Cbr \u002F>\n* GitHub: (adicione seu repositório se tiver)\u003Cbr \u002F>\n* WordPress.org Support Forum: https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwally-monitor\u002F\u003C\u002Fp>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Built with \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdequelabs\u002Faxe-core\" rel=\"nofollow ugc\">axe-core\u003C\u002Fa> by Deque Systems\u003C\u002Fli>\n\u003Cli>Inspired by the need for better accessibility tools in WordPress\u003C\u002Fli>\n\u003Cli>Developed with ❤️ for an inclusive web\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Developers\u003C\u002Fh3>\n\u003Cp>Wally Monitor is open source! Developers can:\u003Cbr \u002F>\n* Extend rules with custom checks\u003Cbr \u002F>\n* Hook into analysis results\u003Cbr \u002F>\n* Customize scoring algorithms\u003Cbr \u002F>\n* Contribute to the codebase\u003C\u002Fp>\n\u003Cp>See GitHub repository for developer documentation.\u003C\u002Fp>\n","Complete accessibility auditing tool for WordPress. Scan your entire site for WCAG 2.2 compliance issues and improve SEO rankings.",189,"2026-03-18T03:42:00.000Z","5.0",[84,18,20,85,22],"a11y","seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwally-monitor.1.5.4.zip",{"slug":88,"name":89,"version":90,"author":91,"author_profile":92,"description":93,"short_description":94,"active_installs":95,"downloaded":96,"rating":97,"num_ratings":98,"last_updated":99,"tested_up_to":14,"requires_at_least":100,"requires_php":16,"tags":101,"homepage":104,"download_link":105,"security_score":106,"vuln_count":107,"unpatched_count":11,"last_vuln_date":108,"fetched_at":27},"pojo-accessibility","Ally – Web Accessibility & Usability","4.1.0","Elementor","https:\u002F\u002Fprofiles.wordpress.org\u002Felemntor\u002F","\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002F-2ig5D348vo?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Cp>Ally (formerly One Click Accessibility) is a free, powerful, and user-friendly plugin that helps WordPress creators build more accessible websites with ease.\u003Cbr \u002F>\nIt simplifies accessibility with three essential tools:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Ally Assistant\u003C\u002Fstrong> – Scan your pages, detect accessibility violations, and follow guided steps to fix them. Make manual adjustments or apply AI-powered suggestions, and track your progress.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Usability widget\u003C\u002Fstrong> – Let visitors personalize their browsing experience with a floating accessibility menu. Features include font resizing, color contrast, image hiding, animation pausing, language selection, screen reader support, and more.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Accessibility statement generator\u003C\u002Fstrong> – Create a fully customized accessibility statement and publish it automatically on your site, helping meet WCAG and legal requirements.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>No expertise required\u003C\u002Fstrong> -just activate, configure, and start making your site more inclusive today.Built by Elementor. Designed for every WordPress site. Ally is web accessibility—simplified.\u003C\u002Fp>\n\u003Ch3>Why does web accessibility matter?\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Who Needs It?\u003C\u002Fstrong> Every website owner—businesses, creators, and agencies.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Who is Responsible?\u003C\u002Fstrong> Website owners are legally and ethically responsible for accessibility. The web creator—who designs and builds the site—must implement and adjust accessibility features to ensure compliance with WCAG guidelines and provide an inclusive experience for all users.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Why Now?\u003C\u002Fstrong> Rising legal requirements (WCAG, EAA) and better user experience.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Why Should You Care?\u003C\u002Fstrong>  An accessible website isn’t just ethical; it’s good business. By prioritizing inclusivity, you improve user experience for everyone, boost your search engine rankings, and attract a wider audience.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>It’s the Law\u003C\u002Fh3>\n\u003Cp>As accessibility standards continue to evolve and become mandatory, it’s important to start making website adjustments to comply with fast-approaching global regulations. Among its other capabilities, this plugin lets you instantly generate your website’s Accessibility Statement, which is now mandatory in most locales.\u003C\u002Fp>\n\u003Cp>The Ally plugin is not a substitute for a thorough accessibility audit and is NOT intended to completely make your website legally compliant. However, with it, you’re one step closer to making your website inclusive to more visitors, including those with visual, auditory or cognitive challenges.\u003C\u002Fp>\n\u003Cp>Ensuring that your website complies with all applicable accessibility requirements is your responsibility. We recommend working with qualified accessibility professionals to help achieve full compliance.\u003C\u002Fp>\n\u003Ch3>Key Features & Benefits\u003C\u002Fh3>\n\u003Ch4>Ally Assistant\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Scan any URL on demand to detect accessibility gaps\u003C\u002Fli>\n\u003Cli>Launch directly from WordPress or Elementor\u003C\u002Fli>\n\u003Cli>Step-by-step guidance to fix issues\u003C\u002Fli>\n\u003Cli>AI-powered remediation suggestions\u003C\u002Fli>\n\u003Cli>Progress tracking via a visual dashboard\u003C\u002Fli>\n\u003Cli>No accessibility expertise required\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>How It Works\u003C\u002Fh4>\n\u003Cp>Ally Assistant scans individual URLs for accessibility violations, categorizes them by type and severity, and provides actionable insights. You can apply manual fixes manually or use AI suggestions while tracking your progress over time.\u003Cbr \u002F>\nAlly Assistant helps you:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Detect missing alternative text\u003C\u002Fli>\n\u003Cli>Label dynamic content & ARIA landmarks\u003C\u002Fli>\n\u003Cli>Validate forms & flag input errors\u003C\u002Fli>\n\u003Cli>Ensure keyboard & assistive tech compatibility\u003C\u002Fli>\n\u003Cli>Identify accessibility violations in tables\u003C\u002Fli>\n\u003Cli>Repair incorrect page structure & navigation\u003C\u002Fli>\n\u003Cli>Flag color contrast & visual style violations (coming soon)\u003C\u002Fli>\n\u003Cli>And detect 180+ other common accessibility violations based on WCAG 2.1 AA\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Accessibility Statement Generator\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Auto-generate a complete  accessibility statement\u003C\u002Fli>\n\u003Cli>Customize and publish to a dedicated page\u003C\u002Fli>\n\u003Cli>Link it using the widget\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usability Widget\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Offer visitors a customizable menu with features like:\u003C\u002Fli>\n\u003Cli>Contrast Modes (high, dark, light, negative)\u003C\u002Fli>\n\u003Cli>Font resizing & readable font toggle\u003C\u002Fli>\n\u003Cli>Pause animations & hide images\u003C\u002Fli>\n\u003Cli>Line height & text alignment options\u003C\u002Fli>\n\u003Cli>Keyboard navigation enhancements\u003C\u002Fli>\n\u003Cli>Underlined links & reading guide\u003C\u002Fli>\n\u003Cli>Skip to content \u002F sitemap viewer\u003C\u002Fli>\n\u003Cli>Language selector\u003C\u002Fli>\n\u003Cli>Skip to Main Content\u003C\u002Fli>\n\u003Cli>Restore defaults & widget toggle\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Premium widget features are also available within paid plans, including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Screen reader compatibility improvements\u003C\u002Fli>\n\u003Cli>White labeling (remove Elementor branding)\u003C\u002Fli>\n\u003Cli>Language selector directly in the widget\u003C\u002Fli>\n\u003Cli>Usage analytics to gain actionable insights from visitor interactions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Widget customization options for web creators\u003C\u002Fh4>\n\u003Cp>Tailor the widget’s look and behavior with options like:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Show\u002Fhide widget icon on mobile or desktop\u003C\u002Fli>\n\u003Cli>Select icon type and size\u003C\u002Fli>\n\u003Cli>Choose colors for icon, header, and text\u003C\u002Fli>\n\u003Cli>Define icon position (corner selection)\u003C\u002Fli>\n\u003Cli>Add\u002Fedit sitemap URL\u003C\u002Fli>\n\u003Cli>Enable\u002Fdisable features per device or user role\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Get Started Today\u003C\u002Fh3>\n\u003Ch3>Make your site more accessible with Ally!\u003C\u002Fh3>\n\u003Cp>Need help? Visit our \u003Ca href=\"https:\u002F\u002Fgo.elementor.com\u002Facc-wp-repo-learn-more\" rel=\"nofollow ugc\">help center\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fgo.elementor.com\u002Fwp-repo-wp-dash-sm-contact-us\u002F\" rel=\"nofollow ugc\">contact Supoprt\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>This plugin requires a connection to an active Elementor account in order to identify the user and provide the user with the purchased service. This connection is initiated manually by the user via the plugin’s settings panel. Learn more about our \u003Ca href=\"https:\u002F\u002Fgo.elementor.com\u002Facc-wp-repo-term-and-conditions\" rel=\"nofollow ugc\">terms and conditions\u003C\u002Fa>. This plugin uses a 3rd party service operated by Elementor.\u003C\u002Fp>\n\u003Cp>More accessibility features are on the way, so stay tuned!\u003C\u002Fp>\n\u003Ch3>Related Plugins\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsite-mailer\u002F\" rel=\"ugc\">Site Mailer\u003C\u002Fa>: Manage transactional emails with ease with Site Mailer. High deliverability, detailed logs and statistics, and no SMTP plugins needed.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fimage-optimization\u002F\" rel=\"ugc\">Image Optimizer\u003C\u002Fa>: Compress and optimize your images, giving you leaner, faster websites. Automatically optimize any new image you upload or run a bulk optimization process for existing uploads.\u003C\u002Fli>\n\u003C\u002Ful>\n","Ally: Make your site more inclusive by scanning for accessibility violations, fixing them easily, and adding a usability widget and accessibility stat …",500000,4422404,58,154,"2026-02-23T10:06:00.000Z","6.6",[84,18,102,22,103],"accessibility-statement","web-accessibility","https:\u002F\u002Felementor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpojo-accessibility.4.1.0.zip",93,4,"2026-03-10 16:11:03",{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":117,"downloaded":118,"rating":12,"num_ratings":119,"last_updated":120,"tested_up_to":14,"requires_at_least":121,"requires_php":66,"tags":122,"homepage":125,"download_link":126,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"userway-accessibility-widget","Accessibility by UserWay","2.6.6","UserWay","https:\u002F\u002Fprofiles.wordpress.org\u002Fuserwayorg\u002F","\u003Cp>Web accessibility can seem complex and overwhelming if you don’t know where to start.\u003C\u002Fp>\n\u003Cp>Let us make it easier, and, to coin a phrase, more accessible for everyone. UserWay’s Accessibility Widget creates a simpler and more accessible browsing experience for your users while increasing compliance with WCAG 2.1, ATAG 2.0, European EN 301 549, ADA, & Section 508 requirements.\u003C\u002Fp>\n\u003Cp>UserWay’s Accessibility Widget will strengthen any weak areas that could cause accessibility issues on your site. We are proud to say that a significant number of websites are more accessible today thanks to UserWay.\u003C\u002Fp>\n\u003Cp>UserWay’s Accessibility Widget makes smart modifications to elements on your site that are identified as being non-compliant, that may prevent keyboard-only navigation, or are in violation of ADA regulations.\u003C\u002Fp>\n\u003Cp>Install UserWay’s Accessibility Widget today.\u003Cbr \u002F>\nAfter installing UserWay’s Accessibility Widget, you will receive login instructions to the widget via email.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>ADA & WCAG 2.1 Compliance\u003C\u002Fstrong>\u003Cbr \u002F>\nUserWay’s best-in-class accessibility solutions move your site towards ADA and WCAG 2.1 compliance.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Shield Against Lawsuits\u003C\u002Fstrong>\u003Cbr \u002F>\nIncreasing your accessibility provides real, sustainable improvement for all users, and protects you from accessibility-related lawsuits.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Improve SEO, Boost Traffic\u003C\u002Fstrong>\u003Cbr \u002F>\nMake your commitment clear: a more inclusive site for everyone expands your demographic and boosts your SEO.\u003C\u002Fp>\n","UserWay’s Accessibility Widget creates a simpler and more accessible browsing experience for your users.",80000,924598,56,"2025-12-08T10:38:00.000Z","4.7",[18,70,123,124,22],"eaa-compliance","section-508","https:\u002F\u002Fuserway.org","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fuserway-accessibility-widget.2.6.6.zip",{"attackSurface":128,"codeSignals":169,"taintFlows":178,"riskAssessment":179,"analyzedAt":184},{"hooks":129,"ajaxHandlers":165,"restRoutes":166,"shortcodes":167,"cronEvents":168,"entryPointCount":11,"unprotectedCount":11},[130,136,140,144,148,152,158,160,161,162,163,164],{"type":131,"name":132,"callback":133,"file":134,"line":135},"action","init","a11yfix_load_textdomain","a11yfix.php",37,{"type":131,"name":137,"callback":138,"file":134,"line":139},"wp_enqueue_scripts","a11yfix_enqueue_assets",103,{"type":131,"name":141,"callback":142,"file":134,"line":143},"send_headers","a11yfix_send_post_id_header",118,{"type":131,"name":145,"callback":146,"file":134,"line":147},"admin_menu","a11yfix_register_tools_page",134,{"type":131,"name":149,"callback":150,"file":134,"line":151},"admin_enqueue_scripts","a11yfix_enqueue_admin_assets",243,{"type":153,"name":154,"callback":155,"priority":156,"file":134,"line":157},"filter","script_loader_tag","a11yfix_mark_module_scripts",10,275,{"type":131,"name":132,"callback":133,"file":159,"line":135},"trunk\u002Fa11yfix.php",{"type":131,"name":137,"callback":138,"file":159,"line":139},{"type":131,"name":141,"callback":142,"file":159,"line":143},{"type":131,"name":145,"callback":146,"file":159,"line":147},{"type":131,"name":149,"callback":150,"file":159,"line":151},{"type":153,"name":154,"callback":155,"priority":156,"file":159,"line":157},[],[],[],[],{"dangerousFunctions":170,"sqlUsage":171,"outputEscaping":173,"fileOperations":176,"externalRequests":11,"nonceChecks":11,"capabilityChecks":107,"bundledLibraries":177},[],{"prepared":11,"raw":11,"locations":172},[],{"escaped":174,"rawEcho":11,"locations":175},132,[],2,[],[],{"summary":180,"deductions":181},"The \"a11yfix-for-wcag\" v1.0.0 plugin demonstrates a strong security posture based on the provided static analysis and vulnerability history. The absence of known CVEs and unpatched vulnerabilities suggests a well-maintained and secure plugin.  The code analysis reveals a clean codebase with no dangerous functions, no raw SQL queries, and all output being properly escaped, which are excellent security practices. The presence of capability checks indicates that access to certain functionalities is likely controlled, further strengthening its security.\n\nHowever, a notable concern is the complete absence of nonce checks. While there are no detected AJAX handlers or shortcodes, which reduces the immediate risk of nonce bypasses, the lack of this fundamental WordPress security measure leaves potential future attack vectors open if new entry points are introduced without proper nonce implementation.  Furthermore, the analysis shows no taint flows, which is positive, but it's important to remember that static analysis might not catch all dynamic or complex vulnerabilities. The plugin's attack surface is currently zero, which is ideal, but this can change with future updates.\n\nIn conclusion, \"a11yfix-for-wcag\" v1.0.0 appears to be a secure plugin, particularly due to its clean code, proper output escaping, and lack of historical vulnerabilities. The primary area for improvement is the implementation of nonce checks for all relevant actions, even in the absence of current entry points, to proactively mitigate potential risks. The plugin's strengths lie in its adherence to secure coding practices for SQL and output, while its weakness is the missing nonce protection.",[182],{"reason":183,"points":156},"Missing nonce checks","2026-04-16T14:27:44.530Z",{"wat":186,"direct":197},{"assetPaths":187,"generatorPatterns":191,"scriptPaths":192,"versionParams":193},[188,189,190],"\u002Fwp-content\u002Fplugins\u002Fa11yfix-for-wcag\u002Fassets\u002Fdist\u002Fclient.js","\u002Fwp-content\u002Fplugins\u002Fa11yfix-for-wcag\u002Fassets\u002Fdist\u002Fa11yfix.js","\u002Fwp-content\u002Fplugins\u002Fa11yfix-for-wcag\u002Fassets\u002Fdist\u002Fa11yfix.css",[],[188,189],[194,195,196],"a11yfix-for-wcag\u002Fassets\u002Fdist\u002Fclient.js?ver=","a11yfix-for-wcag\u002Fassets\u002Fdist\u002Fa11yfix.js?ver=","a11yfix-for-wcag\u002Fassets\u002Fdist\u002Fa11yfix.css?ver=",{"cssClasses":198,"htmlComments":199,"htmlAttributes":200,"restEndpoints":201,"jsGlobals":202,"shortcodeOutput":205},[],[],[],[],[203,204],"a11yfixClientData","a11yfixData",[],{"error":207,"url":208,"statusCode":209,"statusMessage":210,"message":210},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fa11yfix-for-wcag\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":31,"versions":212},[213],{"version":6,"download_url":24,"svn_tag_url":214,"released_at":26,"has_diff":215,"diff_files_changed":216,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":217,"is_current":207},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fa11yfix-for-wcag\u002Ftags\u002F1.0.0\u002F",false,[],[]]