[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fJ83MCEgQ9_R4s3SjQ_d3OuCD0203J5hpqaIMZO16FZQ":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"sstucl","Sebastjan","https:\u002F\u002Fprofiles.wordpress.org\u002Fsstucl\u002F",3,0,100,30,94,"2026-08-29T16:25:23.603Z",[14,35,51],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":8,"downloaded":20,"rating":8,"num_ratings":8,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":31,"download_link":32,"security_score":9,"vuln_count":8,"unpatched_count":8,"last_vuln_date":33,"fetched_at":34},"ninja-ai-accessibility","NINJA AI Accessibility","1.0.0","\u003Cp>The European Accessibility Act (in force since June 2025) and WCAG 2.1 AA make\u003Cbr \u002F>\naccessibility a legal requirement, not a nice-to-have. NINJA AI Accessibility\u003Cbr \u002F>\nscans every published post and page for the barriers you can actually fix and\u003Cbr \u002F>\nscores each one 0–100, worst-first.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>This is not an accessibility “overlay.”\u003C\u002Fstrong> Overlay widgets don’t create\u003Cbr \u002F>\ncompliance — courts have repeatedly ruled against them, and in 2025 a large\u003Cbr \u002F>\nshare of accessibility lawsuits targeted sites that had one installed. We don’t\u003Cbr \u002F>\nhide problems behind a toolbar; we find the real ones in your content and tell\u003Cbr \u002F>\nyou how to fix them.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What it checks (per post\u002Fpage, scored 0–100):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Image alt text\u003C\u002Fstrong> (WCAG 1.1.1) — flags images with no \u003Ccode>alt\u003C\u002Fcode> attribute. Valid\u003Cbr \u002F>\ndecorative images (\u003Ccode>alt=\"\"\u003C\u002Fcode>) are correctly left alone, so you don’t get\u003Cbr \u002F>\nfalse positives.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Link purpose\u003C\u002Fstrong> (WCAG 2.4.4) — empty links and vague text like “click here”\u003Cbr \u002F>\nor “read more” that tell a screen-reader user nothing out of context.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Heading structure\u003C\u002Fstrong> (WCAG 1.3.1) — skipped heading levels and multiple H1s\u003Cbr \u002F>\nthat break the document outline.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Frame titles\u003C\u002Fstrong> (WCAG 4.1.2) — embedded iframes (video, maps) with no title.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Table headers\u003C\u002Fstrong> (WCAG 1.3.1) — data tables missing \u003Ccode>\u003Cth>\u003C\u002Fcode> header cells.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>EAA readiness panel:\u003C\u002Fstrong> checks for a published accessibility statement and a\u003Cbr \u002F>\ndeclared document language.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Honest about its limits.\u003C\u002Fstrong> Some criteria — colour contrast, keyboard focus\u003Cbr \u002F>\norder, theme landmarks — depend on rendered styles and can’t be judged from\u003Cbr \u002F>\ncontent alone, so we never claim to. Use this to fix what’s findable and pair\u003Cbr \u002F>\nit with a manual review for full WCAG 2.1 AA \u002F EAA conformance. The free plugin\u003Cbr \u002F>\nruns entirely on your site and makes \u003Cstrong>no external requests\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch3>NINJA AI Accessibility Pro (optional add-on)\u003C\u002Fh3>\n\u003Cp>NINJA AI Accessibility Pro (from https:\u002F\u002Fninja.si — not the WordPress.org\u003Cbr \u002F>\ndirectory) adds one-click, AI-assisted remediation (e.g. generating descriptive\u003Cbr \u002F>\nalt text from each image) and \u003Cstrong>Accessibility Watch\u003C\u002Fstrong> — it re-scans on a\u003Cbr \u002F>\nschedule and emails you when a new publish introduces a barrier or your score\u003Cbr \u002F>\ndrops. Pro is the only part that contacts ninja.si, and only after you register.\u003C\u002Fp>\n","Audit your content for WCAG \u002F EU Accessibility Act issues — alt text, headings, links, frames, tables — scored with a fix list. No overlay, no fluff.",122,"2026-05-25T12:21:00.000Z","7.0.2","6.8","7.4",[26,27,28,29,30],"accessibility","ada","alt-text","eaa","wcag","https:\u002F\u002Fninja.si\u002Fpro","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fninja-ai-accessibility.1.0.0.zip",null,"2026-07-22T17:31:50.256Z",{"slug":36,"name":37,"version":38,"author":5,"author_profile":6,"description":39,"short_description":40,"active_installs":8,"downloaded":41,"rating":8,"num_ratings":8,"last_updated":42,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":43,"homepage":49,"download_link":50,"security_score":9,"vuln_count":8,"unpatched_count":8,"last_vuln_date":33,"fetched_at":34},"ninja-ai-seo","NINJA AI SEO","1.4.1","\u003Cp>Search is shifting from ten blue links to AI answers. When ChatGPT, Claude,\u003Cbr \u002F>\nGrok, Perplexity or Gemini crawl your site, a handful of signals decide whether\u003Cbr \u002F>\nthey can \u003Cstrong>read, understand and cite\u003C\u002Fstrong> your content. NINJA AI SEO scores those\u003Cbr \u002F>\nsignals and shows you exactly what to fix.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>AI visibility (site-level):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>AI crawler access\u003C\u002Fstrong> — checks whether your robots.txt lets GPTBot, ClaudeBot,\u003Cbr \u002F>\nGoogle-Extended, PerplexityBot and Common Crawl in. Block them and you can\u003Cbr \u002F>\nnever be quoted.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Structured data\u003C\u002Fstrong> — emits schema.org JSON-LD (Article\u002FWebPage) on every post\u003Cbr \u002F>\nand page, turning your prose into facts a model can extract and trust.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>llms.txt\u003C\u002Fstrong> — detects the site-root file that tells LLMs what your best\u003Cbr \u002F>\ncontent is (Pro generates it for you).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>XML sitemap\u003C\u002Fstrong> — confirms crawlers can discover every page.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>On-page audit (per post\u002Fpage, scored 0–100):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Meta description\u003C\u002Fstrong> — the summary engines read first and often quote\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SEO title length\u003C\u002Fstrong> — how your page is titled and attributed\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Image alt text\u003C\u002Fstrong> — the only thing a text model “sees” in an image\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Content length\u003C\u002Fstrong>, \u003Cstrong>subheadings\u003C\u002Fstrong>, \u003Cstrong>internal links\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The Overview tab gives you a site SEO-health score, an AI-visibility panel, and\u003Cbr \u002F>\nyour top opportunities. For every page you can set the SEO title and meta\u003Cbr \u002F>\ndescription by hand; NINJA AI SEO outputs them (and the JSON-LD) on the front\u003Cbr \u002F>\nend immediately. \u003Cstrong>The free plugin is fully functional on its own and makes no\u003Cbr \u002F>\nexternal connections.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>NINJA AI SEO Pro (optional add-on)\u003C\u002Fh3>\n\u003Cp>NINJA AI SEO Pro is a separate add-on (available from https:\u002F\u002Fninja.si — not from\u003Cbr \u002F>\nthe WordPress.org directory) that adds a one-click auto-fix engine: it generates\u003Cbr \u002F>\nmeta descriptions and SEO titles from each page’s own content and backfills\u003Cbr \u002F>\nmissing image alt text, per page or across the whole site. Pro is the only part\u003Cbr \u002F>\nthat connects to ninja.si, and only after you choose to activate it.\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>The free plugin sends no data anywhere — all auditing happens locally in your\u003Cbr \u002F>\nWordPress install. (The optional Pro add-on contacts ninja.si only when you\u003Cbr \u002F>\nregister it; see the Pro readme.)\u003C\u002Fp>\n","Make your content visible to AI answer engines (ChatGPT, Claude, Perplexity, Gemini) and classic search. Audits SEO + AI signals, emits schema.",111,"2026-05-25T10:37:00.000Z",[44,45,46,47,48],"ai","meta-description","schema","seo","sitemap","https:\u002F\u002Fninja.si\u002Fplugins\u002Fninjaseo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fninja-ai-seo.1.4.1.zip",{"slug":52,"name":53,"version":17,"author":5,"author_profile":6,"description":54,"short_description":55,"active_installs":8,"downloaded":56,"rating":8,"num_ratings":8,"last_updated":57,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":58,"homepage":64,"download_link":65,"security_score":9,"vuln_count":8,"unpatched_count":8,"last_vuln_date":33,"fetched_at":34},"ninja-checkout-fields","NINJA Checkout Fields","\u003Cp>Every WooCommerce store has a checkout page, but the default field set rarely fits every business. NINJA Checkout Fields gives shop managers a clean admin screen (under WooCommerce \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Checkout Fields) where they can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enable or disable\u003C\u002Fstrong> any standard checkout field (Billing, Shipping, Additional\u002FOrder).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mark fields as required or optional\u003C\u002Fstrong> — override WooCommerce’s defaults to fit your workflow.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rename the label\u003C\u002Fstrong> shown to the customer, without editing template files or child themes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Set a placeholder\u003C\u002Fstrong> (hint text inside the input) per field.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Reorder fields\u003C\u002Fstrong> with simple priority numbers or ▲\u002F▼ buttons — lower priority = earlier on the form.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Live preview\u003C\u002Fstrong> that shows the derived checkout layout — exactly what your customers will see — updating as you edit.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Everything is saved in a single WordPress option. No database tables, no rewrite rules, and no external requests for managing your checkout (the only opt-in exception is the “NINJA Updates” email subscription described below). Activate, configure, done.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Protected fields:\u003C\u002Fstrong> \u003Ccode>billing_country\u003C\u002Fcode> and \u003Ccode>billing_email\u003C\u002Fcode> can never be disabled because WooCommerce requires them to complete order processing. The plugin enforces this server-side regardless of what the admin UI sends.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Reset:\u003C\u002Fstrong> One click restores the full WooCommerce default field set.\u003C\u002Fp>\n\u003Ch3>WooCommerce integration\u003C\u002Fh3>\n\u003Cp>NINJA Checkout Fields declares HPOS (High-Performance Order Storage \u002F Custom Order Tables) compatibility and uses the standard \u003Ccode>woocommerce_checkout_fields\u003C\u002Fcode> filter so it’s compatible with any WooCommerce version that exposes that filter (8.0+). It does not modify database tables, templates, or core files.\u003C\u002Fp>\n\u003Ch3>Stay updated (optional)\u003C\u002Fh3>\n\u003Cp>The admin screen has an optional “NINJA Updates” card: tick the consent box and enter your email to hear about plugin updates and new NINJA modules. It is entirely opt-in — nothing is sent unless you submit that form — and you can unsubscribe at any time with one click. This is the only feature that ever contacts an external service.\u003C\u002Fp>\n","Manage WooCommerce checkout fields without touching code — enable\u002Fdisable, relabel, reorder, and set placeholders from one screen.",116,"2026-05-26T07:25:00.000Z",[59,60,61,62,63],"checkout","checkout-fields","field-manager","woocommerce","woocommerce-checkout","https:\u002F\u002Fninja.si\u002Fplugins\u002Fninja-checkout-fields","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fninja-checkout-fields.1.0.0.zip"]