plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "accessibility-checker",
  "version": "0.1.0",
  "description": "Check a website for WCAG 2.2 accessibility issues in a real browser with axe-core: violations by severity, WCAG criterion, affected elements and plain-language fixes, with EAA, BFSG and ADA context.",
  "author": {
    "name": "Brightstep Tech Inc.",
    "email": "contact@thecvapp.com",
    "url": "https://a11y.eralpbayraktar.com/"
  },
  "license": "MIT",
  "keywords": [
    "accessibility",
    "wcag",
    "wcag 2.2",
    "a11y",
    "accessibility checker",
    "european accessibility act",
    "eaa",
    "bfsg",
    "barrierefreiheit",
    "ada compliance",
    "color contrast",
    "alt text"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Accessibility Checker WCAG",
        "shortDescription": "WCAG, BFSG & EAA Website-Check",
        "longDescription": "Accessibility Checker WCAG checks a public web page for accessibility problems. Give it a URL and it loads the page, and optionally up to 4 more pages linked from it, in a real headless browser, runs the open-source axe-core rules for WCAG 2.2 Level A and AA, and lists what to fix first: each issue's severity, the WCAG success criterion, how many elements fail, example selectors and HTML, and a plain-language fix. It catches problems that need a rendered page, such as low colour contrast, missing alt text, unlabeled form fields, nameless buttons and links, and small touch targets. After you fix things, ask for a rescan and it shows what was fixed, what is new and what changed. Issues inside third-party embeds such as YouTube videos are tagged and listed after your own. It also looks for a link to an accessibility statement (Erkl\u00e4rung zur Barrierefreiheit). Every report adds a short checklist of what automation cannot test, and context on Germany's BFSG, the European Accessibility Act (EAA) and the ADA, in German or English to match ChatGPT's language. Automated checks find only part of all accessibility issues, so a report is not a legal conformity assessment or certificate. Pages behind a login, intranets and private addresses cannot be scanned.",
        "developerName": "Brightstep Tech Inc.",
        "category": "Developer Tools",
        "capabilities": [
          "Check a website",
          "Rescan and compare"
        ],
        "websiteURL": "https://a11y.eralpbayraktar.com/",
        "privacyPolicyURL": "https://a11y.eralpbayraktar.com/privacy",
        "termsOfServiceURL": "https://a11y.eralpbayraktar.com/terms",
        "defaultPrompt": [
          "Pr\u00fcfe kundenseite.de auf Barrierefreiheit nach BFSG",
          "Check my website example.com for WCAG 2.2 accessibility issues",
          "Is my online shop ready for the European Accessibility Act?"
        ],
        "brandColor": "#1D4ED8",
        "composerIcon": "./assets/icon.png",
        "logo": "./assets/logo.png",
        "supportURL": "https://a11y.eralpbayraktar.com/support"
      },
      "onboardingSkill": "./skills/get-started/SKILL.md",
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Page with known WCAG violations",
              "prompt": "Check https://projects.accesscomputing.uw.edu/au/before.html for WCAG 2.2 accessibility issues",
              "tools_triggered": "check_accessibility",
              "expected_behavior": "Shows a report for the University of Washington 'Accessible University' inaccessible demo page: critical issues first, including form fields without labels (label, about 10 elements, WCAG 1.3.1/4.1.2) and images without alt text (image-alt, WCAG 1.1.1), then colour contrast (1.4.3), missing page language (3.1.1) and small targets (2.5.8), each with sample selectors, HTML and a plain-language fix, a manual-check list and the 'not a legal conformity assessment' note."
            },
            {
              "description": "Several pages of a site, EAA framing",
              "prompt": "Is https://www.gov.uk ready for the European Accessibility Act? Check the homepage and a couple of other pages.",
              "tools_triggered": "check_accessibility",
              "expected_behavior": "Calls the tool with maxPages 3, checks gov.uk plus two linked pages, reports the few automated findings by severity, explains that the EAA is presumed met through EN 301 549 (WCAG 2.1 AA) and that automated checks cover only part of it, and does not call the site compliant."
            },
            {
              "description": "Clean page: honest about the limits",
              "prompt": "Run an accessibility check on example.com",
              "tools_triggered": "check_accessibility",
              "expected_behavior": "Reports no automated WCAG A/AA violations on https://example.com/ and says this does not mean the site conforms, listing the manual checks (keyboard, alt-text quality, forms, zoom)."
            },
            {
              "description": "ADA phrasing, plain-language priorities",
              "prompt": "Check https://projects.accesscomputing.uw.edu/au/after.html for ADA website accessibility problems and tell me what to fix first",
              "tools_triggered": "check_accessibility",
              "expected_behavior": "Reports far fewer issues than the 'before' page (at most a few, e.g. small targets or link styling), lists them in order of severity with fixes, mentions that ADA complaints usually cite WCAG 2.1 AA, and states that the scan is not legal advice or a guarantee against claims."
            },
            {
              "description": "German BFSG request",
              "prompt": "Pr\u00fcfe https://www.w3.org/WAI/ auf Barrierefreiheit nach BFSG",
              "tools_triggered": "check_accessibility",
              "expected_behavior": "Checks the W3C WAI home page, answers in German with the findings by severity (or none); the widget is in German, findings inside the embedded YouTube video are tagged 'Drittanbieter-Einbettung' and listed after the page's own, the accessibility statement link is reported, and the BFSG context (scope, micro-enterprise exemption, dates) is mentioned along with the note that an automated scan is not a conformity assessment."
            }
          ],
          "negative": [
            {
              "description": "General WCAG knowledge question, no site to scan",
              "prompt": "What changed between WCAG 2.1 and WCAG 2.2?"
            },
            {
              "description": "PDF accessibility is out of scope",
              "prompt": "Make my PDF brochure accessible and tag the headings"
            },
            {
              "description": "Legal certificate request",
              "prompt": "Write me an official certificate that my shop is EAA compliant so I can show it to customers"
            }
          ]
        },
        "demo_recording_url": "https://a11y.eralpbayraktar.com/demo.mp4",
        "commerce": false,
        "commerce_description": "This plugin does not sell products or process payments."
      },
      "publication": {
        "release_notes": "Initial release: check a public web page (and up to 4 linked pages) for WCAG 2.2 A/AA issues with axe-core in a real browser; issues by severity with WCAG criteria, sample elements and plain-language fixes; rescan comparison; EAA, BFSG and ADA context."
      },
      "apps": "./.app.json"
    }
  },
  "homepage": "https://a11y.eralpbayraktar.com/"
}