{"id":309585,"date":"2026-05-25T20:10:42","date_gmt":"2026-05-25T20:10:42","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/accessmate\/"},"modified":"2026-09-15T10:00:54","modified_gmt":"2026-09-15T10:00:54","slug":"accessmate","status":"publish","type":"plugin","link":"https:\/\/dsb.wordpress.org\/plugins\/accessmate\/","author":14112142,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.1.0","stable_tag":"trunk","tested":"7.1.1","requires":"5.8","requires_php":"7.4","requires_plugins":null,"header_name":"AccessMate","header_author":"AWSM Innovations","header_description":"AI-powered WCAG 2.1 AA accessibility scanner with auto-fix suggestions and a visitor-facing accessibility toolbar. Free \u2014 bring your own AI key.","assets_banners_color":"8083ce","last_updated":"2026-09-15 10:00:54","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/accessmate.ai\/","header_author_uri":"http:\/\/awsm.in\/","rating":0,"author_block_rating":0,"active_installs":10,"downloads":408,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"awsmin","date":"2026-08-13 07:35:52","revision":3644512}},"upgrade_notice":{"1.1.0":"<p>Adds selectable WCAG\/Section 508 rulesets. No upgrade steps required.<\/p>","1.0.0":"<p>Initial release. No upgrade steps required.<\/p>"},"ratings":[],"assets_icons":{"icon.svg":{"filename":"icon.svg","revision":3548400,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3696943,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3696943,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3695916,"resolution":"1","location":"assets","locale":"","width":1626,"height":1118},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3695916,"resolution":"2","location":"assets","locale":"","width":1626,"height":1118},"screenshot-3.gif":{"filename":"screenshot-3.gif","revision":3695916,"resolution":"3","location":"assets","locale":"","width":800,"height":490},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3695916,"resolution":"4","location":"assets","locale":"","width":1573,"height":1044},"screenshot-5.gif":{"filename":"screenshot-5.gif","revision":3695916,"resolution":"5","location":"assets","locale":"","width":800,"height":767},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3695916,"resolution":"6","location":"assets","locale":"","width":1406,"height":1186},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3695916,"resolution":"7","location":"assets","locale":"","width":389,"height":469},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3695916,"resolution":"8","location":"assets","locale":"","width":1400,"height":1021},"screenshot-9.png":{"filename":"screenshot-9.png","revision":3695916,"resolution":"9","location":"assets","locale":"","width":1400,"height":1021}},"screenshots":{"1":"Dashboard \u2014 issue counts by severity, passed checks, Issues by Page chart, and the Pages &amp; Posts table with per-page grades","2":"Accessibility Audit Report \u2014 every scanned page with its grade, score, issue count and last scan time","3":"Front-end accessibility scan launched from the admin bar","4":"Scan results panel \u2014 score, grade, severity filter tabs and per-issue WCAG references","5":"AI fix suggestion for a detected issue","6":"Settings \u2014 AI provider, model, encrypted key input, connection test, and default ruleset","7":"Visitor accessibility toolbar as seen by site visitors","8":"Widget configurator \u2014 colour, position, button size and feature toggles with live preview","9":"Accessibility statement generator \u2014 five-step wizard"}},"plugin_section":[],"plugin_tags":[1953,209467,240895,17212,1956],"plugin_category":[34],"plugin_contributors":[78837],"plugin_business_model":[],"class_list":["post-309585","plugin","type-plugin","status-publish","hentry","plugin_tags-accessibility","plugin_tags-accessibility-checker","plugin_tags-accessibility-widget","plugin_tags-ada-compliance","plugin_tags-wcag","plugin_category-accessibility","plugin_contributors-awsmin","plugin_committers-awsmin"],"banners":{"banner":"https:\/\/ps.w.org\/accessmate\/assets\/banner-772x250.png?rev=3696943","banner_2x":"https:\/\/ps.w.org\/accessmate\/assets\/banner-1544x500.png?rev=3696943","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/accessmate\/assets\/icon.svg?rev=3548400","icon":"https:\/\/ps.w.org\/accessmate\/assets\/icon.svg?rev=3548400","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-1.png?rev=3695916","caption":"Dashboard \u2014 issue counts by severity, passed checks, Issues by Page chart, and the Pages &amp; Posts table with per-page grades"},{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-2.png?rev=3695916","caption":"Accessibility Audit Report \u2014 every scanned page with its grade, score, issue count and last scan time"},{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-3.gif?rev=3695916","caption":"Front-end accessibility scan launched from the admin bar"},{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-4.png?rev=3695916","caption":"Scan results panel \u2014 score, grade, severity filter tabs and per-issue WCAG references"},{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-5.gif?rev=3695916","caption":"AI fix suggestion for a detected issue"},{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-6.png?rev=3695916","caption":"Settings \u2014 AI provider, model, encrypted key input, connection test, and default ruleset"},{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-7.png?rev=3695916","caption":"Visitor accessibility toolbar as seen by site visitors"},{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-8.png?rev=3695916","caption":"Widget configurator \u2014 colour, position, button size and feature toggles with live preview"},{"src":"https:\/\/ps.w.org\/accessmate\/assets\/screenshot-9.png?rev=3695916","caption":"Accessibility statement generator \u2014 five-step wizard"}],"raw_content":"<!--section=description-->\n<p><strong>Accessibility work usually costs you a loop.<\/strong> Copy a URL. Paste it into an off-site scanner. Wait. Hit the free-tier limit. Read a report that tells you what is broken but not what to type. Switch to your editor. Guess at the fix. Go back, paste the URL again, and start over \u2014 for every page, every time the site changes.<\/p>\n\n<p><strong>AccessMate closes that loop inside WordPress.<\/strong> Scan from your dashboard, see every issue ranked by severity, copy an AI-suggested code fix straight into your editor, and re-scan in a click. No tab-switching, no re-pasting URLs, no per-scan credits.<\/p>\n\n<h4>Why developers pick AccessMate<\/h4>\n\n<ul>\n<li><strong>The whole site, in one place<\/strong> \u2014 scan your pages from the Pages &amp; Posts list and see them together: score, letter grade, issue count and last scan date per page, with the worst offenders ranked so you know where to start<\/li>\n<li><strong>Fixes you can paste, not homework<\/strong> \u2014 most scanners hand you a rule name and a spec link. AccessMate shows the offending markup, the exact success criterion, and \u2014 with AI enabled \u2014 a corrected code snippet you copy into your editor<\/li>\n<li><strong>Scan the page you are looking at<\/strong> \u2014 hit <strong>Scan Page<\/strong> in the admin bar on any front-end page and results slide in over the live site. No going back to the dashboard to check your work<\/li>\n<li><strong>Catch regressions before your client does<\/strong> \u2014 accessibility is not a one-off project. Re-scan after a redesign, a new plugin or a content push and see immediately whether anything you shipped broke what was working<\/li>\n<li><strong>A toolbar, not an overlay<\/strong> \u2014 visitor comfort controls without the price tag or the promises<\/li>\n<\/ul>\n\n<h4>A toolbar, not an overlay<\/h4>\n\n<p>AccessMate's visitor toolbar does one honest thing: it lets visitors adjust how your site is displayed \u2014 larger text, higher contrast, a dyslexia-friendly font, reduced motion. It is 15KB, loads deferred, and renders in a Shadow DOM so it cannot touch your theme's styles.<\/p>\n\n<p>What it deliberately does <strong>not<\/strong> do is rewrite your markup, inject ARIA it cannot understand, or claim to make your site compliant. No front-end script can do that. Real accessibility comes from fixing the underlying code \u2014 which is exactly what the scanner half of AccessMate is built to help you do, quickly.<\/p>\n\n<h4>Core features<\/h4>\n\n<ul>\n<li><strong>Accessibility scanner<\/strong> \u2014 powered by axe-core, scans your pages against your choice of WCAG standard, or several combined at once<\/li>\n<li><strong>Score &amp; letter grade<\/strong> \u2014 every scanned page gets a 0\u2013100 score and an A\/B\/C\/D\/F grade, calculated from passed checks against failures weighted by Critical\/Serious\/Warning\/Notice severity<\/li>\n<li><strong>Site-wide scanning<\/strong> \u2014 AccessMate discovers the public URLs on your site and scans them individually, with per-page results, search, and post-type filtering<\/li>\n<li><strong>Scan from the front end<\/strong> \u2014 a \"Scan Page\" button in the admin bar scans whatever page you are viewing and shows results in a slide-in panel, with filter tabs for Critical, Serious and Passed checks and a ruleset switcher for re-scanning<\/li>\n<li><strong>Issues by page<\/strong> \u2014 stacked bar chart showing critical\/serious\/warning\/notice counts per page<\/li>\n<li><strong>Issue detail panel<\/strong> \u2014 shows the offending HTML, the WCAG success criterion with a link to the spec, the CSS selector, and the affected element count<\/li>\n<li><strong>Passed checks<\/strong> \u2014 AccessMate records what passed, not just what failed, so you can show progress<\/li>\n<li><strong>Accessibility statement generator<\/strong> \u2014 a five-step wizard that produces a published accessibility statement page for your site<\/li>\n<li><strong>Visitor accessibility toolbar<\/strong> \u2014 floating widget with 10 user-controlled accessibility features, configurable colour, position and button size<\/li>\n<li><strong>AI fix suggestions<\/strong> <em>(requires API key)<\/em> \u2014 explains what to change and generates a corrected code snippet<\/li>\n<li><strong>AI explanations<\/strong> <em>(requires API key)<\/em> \u2014 plain-English summaries of an issue for non-technical site owners<\/li>\n<\/ul>\n\n<h4>WCAG standards &amp; rulesets<\/h4>\n\n<p>AccessMate scans with <a href=\"https:\/\/github.com\/dequelabs\/axe-core\">axe-core<\/a>, 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:<\/p>\n\n<ul>\n<li>WCAG 2.0 \u2014 A, AA, or AAA<\/li>\n<li>WCAG 2.1 \u2014 A, AA, or AAA<\/li>\n<li>WCAG 2.2 \u2014 AA<\/li>\n<li>Section 508<\/li>\n<li>Best Practice \u2014 common accessibility recommendations beyond the WCAG spec<\/li>\n<li>Combined presets \u2014 Best Practice + WCAG 2.0 AA, + WCAG 2.1 AA, or + WCAG 2.2 AA<\/li>\n<\/ul>\n\n<h4>Visitor accessibility toolbar features<\/h4>\n\n<ul>\n<li>Font size <\/li>\n<li>High contrast <\/li>\n<li>Dyslexia font <\/li>\n<li>Grayscale <\/li>\n<li>Reading guide <\/li>\n<li>Pause animations <\/li>\n<li>Line height <\/li>\n<li>Large cursor <\/li>\n<li>Highlight links <\/li>\n<li>Screen mask<\/li>\n<\/ul>\n\n<p>Each feature can be switched on or off in the Widget configurator, along with the accent colour, screen position and button size. The toolbar renders inside a Shadow DOM, so its styles cannot affect your theme, and visitor preferences are remembered in their browser's localStorage.<\/p>\n\n<h4>AI providers supported<\/h4>\n\n<ul>\n<li><strong>Anthropic Claude<\/strong> (claude-haiku-4-5, claude-sonnet-4)<\/li>\n<li><strong>OpenAI<\/strong> (gpt-4o-mini, gpt-4o)<\/li>\n<li><strong>Google Gemini<\/strong> (gemini-1.5-flash, gemini-1.5-pro)<\/li>\n<li><strong>Ollama<\/strong> (local, no key needed \u2014 llama3.2, mistral, phi3)<\/li>\n<\/ul>\n\n<h4>Privacy<\/h4>\n\n<p>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.<\/p>\n\n<p>The OpenDyslexic font used by the toolbar's dyslexia feature is bundled inside the plugin and served from your own site. No font CDN is contacted.<\/p>\n\n<h3>Third Party Libraries<\/h3>\n\n<ul>\n<li><a href=\"https:\/\/github.com\/dequelabs\/axe-core\">axe-core<\/a> by Deque Systems \u2014 Mozilla Public License 2.0 (MPL-2.0)<\/li>\n<li><a href=\"https:\/\/fontsource.org\/fonts\/opendyslexic\">OpenDyslexic font via Fontsource<\/a> \u2014 Bitstream Vera Fonts License \u2014 bundled with the plugin and served locally; no CDN request is made<\/li>\n<\/ul>\n\n<h3>External Services<\/h3>\n\n<p>This plugin can connect to the following external services. No external requests are made unless you explicitly configure and trigger the relevant feature.<\/p>\n\n<h4>AI providers (optional)<\/h4>\n\n<p>When you add an API key and click an AI action (fix suggestion or plain-English explanation), 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.<\/p>\n\n<p><strong>Anthropic<\/strong> \u2014 <code>https:\/\/api.anthropic.com\/<\/code>\nUsed for: AI fix suggestions and plain-English issue explanations.\nData sent: page HTML snippet, accessibility issue context, and your Anthropic API key (in the request header).\n<a href=\"https:\/\/www.anthropic.com\/legal\/consumer-terms\">Terms of Service<\/a> | <a href=\"https:\/\/www.anthropic.com\/legal\/privacy\">Privacy Policy<\/a><\/p>\n\n<p><strong>OpenAI<\/strong> \u2014 <code>https:\/\/api.openai.com\/<\/code>\nUsed for: AI fix suggestions and plain-English issue explanations.\nData sent: page HTML snippet, accessibility issue context, and your OpenAI API key (in the request header).\n<a href=\"https:\/\/openai.com\/policies\/terms-of-use\">Terms of Service<\/a> | <a href=\"https:\/\/openai.com\/policies\/privacy-policy\">Privacy Policy<\/a><\/p>\n\n<p><strong>Google Gemini<\/strong> \u2014 <code>https:\/\/generativelanguage.googleapis.com\/<\/code>\nUsed for: AI fix suggestions and plain-English issue explanations.\nData sent: page HTML snippet, accessibility issue context, and your Gemini API key (as a URL parameter).\n<a href=\"https:\/\/ai.google.dev\/gemini-api\/terms\">Terms of Service<\/a> | <a href=\"https:\/\/policies.google.com\/privacy\">Privacy Policy<\/a><\/p>\n\n<p><strong>Ollama<\/strong> \u2014 <code>http:\/\/localhost:11434\/<\/code> (local only)\nOllama runs entirely on the user's own machine or local network. No data is sent to any external server.<\/p>\n\n<h3>Source Code<\/h3>\n\n<p>The admin interface and scan overlay are built from TypeScript and React sources with Vite. The unminified sources are included in this plugin under <code>\/src<\/code> and <code>\/widget<\/code>, alongside <code>package.json<\/code>, <code>tsconfig.json<\/code> and the Vite configuration files. To rebuild the bundles in <code>\/assets<\/code>, run <code>npm install<\/code> followed by <code>npm run build<\/code>.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>accessmate<\/code> folder to <code>\/wp-content\/plugins\/<\/code><\/li>\n<li>Activate the plugin through the <strong>Plugins<\/strong> menu in WordPress<\/li>\n<li>Navigate to <strong>AccessMate<\/strong> in your admin menu<\/li>\n<li>Click <strong>Scan<\/strong> to perform your first accessibility check, or use <strong>Scan Page<\/strong> in the admin bar while viewing any page on your site<\/li>\n<li><em>(Optional)<\/em> Go to <strong>Settings<\/strong> to add an AI provider key for AI-powered fix suggestions and explanations<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"is%20accessmate%20free%3F\"><h3>Is AccessMate free?<\/h3><\/dt>\n<dd><p>Yes. Scanning, reporting, the accessibility statement generator and the visitor toolbar are free with no usage limits. The AI features are optional and use your own API key, billed directly by the AI provider \u2014 AccessMate does not resell AI usage or take a cut.<\/p><\/dd>\n<dt id=\"do%20i%20need%20an%20ai%20key%20to%20use%20accessmate%3F\"><h3>Do I need an AI key to use AccessMate?<\/h3><\/dt>\n<dd><p>No. The scanner, scoring, reports, statement generator and visitor toolbar all work with the AI provider set to <strong>None<\/strong>. The API key only unlocks the two AI buttons in the issue detail panel.<\/p><\/dd>\n<dt id=\"does%20accessmate%20guarantee%20wcag%20compliance%3F\"><h3>Does AccessMate guarantee WCAG compliance?<\/h3><\/dt>\n<dd><p>No. Automated scanning identifies a significant subset of issues for the WCAG or Section 508 standard you select, but cannot replace manual testing with real assistive technologies. The plugin's report includes a disclaimer to that effect.<\/p><\/dd>\n<dt id=\"is%20the%20ai%20api%20key%20stored%20securely%3F\"><h3>Is the AI API key stored securely?<\/h3><\/dt>\n<dd><p>Your key is encrypted with AES-256-CBC using your WordPress authentication salt before being stored in <code>wp_options<\/code>. The raw key is never returned in any API response \u2014 only a boolean <code>ai_key_set<\/code> flag.<\/p><\/dd>\n<dt id=\"which%20pages%20does%20accessmate%20scan%3F\"><h3>Which pages does AccessMate scan?<\/h3><\/dt>\n<dd><p>AccessMate discovers the public URLs on your site and lists them in <strong>Pages &amp; Posts<\/strong>, where you can scan them individually. You can also scan whichever page you are currently viewing with the <strong>Scan Page<\/strong> button in the admin bar, or pass a specific URL via the REST API (<code>POST \/wp-json\/accessmate\/v1\/scan<\/code> with a <code>url<\/code> body parameter).<\/p><\/dd>\n<dt id=\"does%20accessmate%20scan%20automatically%3F\"><h3>Does AccessMate scan automatically?<\/h3><\/dt>\n<dd><p>Scans are run on demand. AccessMate does register a weekly WP-Cron event that re-checks your home page in the background and updates the \"last checked\" date shown on the Report screen; the per-page results in your dashboard are only updated when you run a scan yourself.<\/p><\/dd>\n<dt id=\"does%20the%20toolbar%20affect%20my%20site%27s%20performance%3F\"><h3>Does the toolbar affect my site's performance?<\/h3><\/dt>\n<dd><p>The widget bundle is 15.2KB (5.7KB gzipped) and loads with the <code>defer<\/code> attribute. It uses Shadow DOM so its styles cannot affect your existing CSS, and it is only injected when at least one toolbar feature is enabled.<\/p><\/dd>\n<dt id=\"will%20accessmate%20conflict%20with%20elementor%20or%20woocommerce%3F\"><h3>Will AccessMate conflict with Elementor or WooCommerce?<\/h3><\/dt>\n<dd><p>AccessMate does not modify your theme's output except via the opt-in accessibility toolbar. Its admin interface is confined to its own admin pages, and the scan overlay is only loaded for logged-in users who can manage options.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Added selectable rulesets, including WCAG 2.0, WCAG 2.1, WCAG 2.2, Section 508, and Best Practice, along with combined presets such as \"Best Practice + WCAG AA\" for scans.<\/li>\n<li>Replaced the previous fixed WCAG 2.1 AA-only scanning configuration with flexible ruleset selection.<\/li>\n<li>Added a \"Serious\" severity tier (alongside Critical\/Warning\/Notice) and moved to a weighted accessibility score.<\/li>\n<li>Added an accessibility statement generator.<\/li>\n<li>Implemented various user interface improvements.<\/li>\n<li>Minor code improvements and changes.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release<\/li>\n<li>WCAG 2.1 AA scanner with per-page scoring and letter grades<\/li>\n<li>React admin dashboard with severity breakdown and Issues by Page chart<\/li>\n<li>Per-page scanner with per-URL results and slide-in issue panel<\/li>\n<li>Front-end scan overlay launched from the admin bar<\/li>\n<li>AI provider integration (Anthropic, OpenAI, Gemini, Ollama) \u2014 bring your own key<\/li>\n<li>Visitor accessibility toolbar with 10 features (Shadow DOM, localStorage)<\/li>\n<li>Widget configurator with colour, position, and feature toggles<\/li>\n<li>Full i18n support \u2014 all user-facing strings are translatable<\/li>\n<\/ul>","raw_excerpt":"Scan your site for Accessibility issues inside WordPress. Paste the AI-suggested fix and re-scan in one click. No off-site tools.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/309585","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=309585"}],"author":[{"embeddable":true,"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/awsmin"}],"wp:attachment":[{"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=309585"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=309585"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=309585"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=309585"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=309585"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/dsb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=309585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}