· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Brightstep Tech Inc. v0.1.0
WCAG, BFSG & EAA Website-Check
Developer declarations; not independently tested. Listing last checked Nov 4, 2026. Package observed Nov 3, 2026.
This plugin does not sell products or process payments.
Prüfe kundenseite.de auf Barrierefreiheit nach BFSG
From the marketplace listing
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ärung 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.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →Find competitors to follow as you develop your plugin.
Check a live public website for WCAG 2.1/2.2 AA accessibility issues with axe-core, and get plain-English fix steps for each failing rule.
Shared terms: wcag, website, check, accessibility
Checks a website's public setup from the outside (HTTPS and security headers, certificate dates, SPF and DMARC, privacy, terms and contac...
Shared terms: website, check, fail, fix
Audit a public website before launch and get prioritized findings with the evidence behind them.
Shared terms: website, check, alt, browser
Scan a web page for WCAG 2.2 accessibility failures and get the fix for each one.
Shared terms: wcag, accessibility, axe, browser
Check WCAG colour contrast, test whole palettes, and generate accessible 50-950 colour scales.
Shared terms: wcag, accessibility, browser, checker
---
name: get-started
description: Use this when the user wants a public website checked for accessibility issues ("check https://example.com for wcag accessibility issues", "Ist unsere Website barrierefrei nach BFSG?", "barrierefreiheit prüfen", "ready for the European Accessibility Act?") or rescanned after fixes. The tool loads the page in a real browser and returns the actual WCAG 2.2 failures with the affected elements and fixes.
---
1. Ask only for what is missing: the public URL of the page to check. If they want "the whole site", use `maxPages` 3 to 5 (the URL plus pages linked from it).
2. Call `check_accessibility`. If a page could not be checked (bot protection, timeout, private address), say why and suggest the free axe DevTools or WAVE browser extension for that page.
3. Lead with the three most important fixes in plain words, in the user's language: what is wrong, where (selector or example), and how to fix it. Then the counts by severity.
4. Always mention the manual checks (keyboard, alt-text quality, forms, captions, zoom), and that automated checks find only part of all issues.
5. Never say the site is compliant, certified or safe from complaints or lawsuits. The report is not a legal conformity assessment. Do not recommend overlay widgets as a fix.
6. When the user has fixed things and asks to rescan, call the tool again with `compareWith` set to the `compareKey` from the earlier result, and summarise what was fixed, what is new and what changed.
7. Pages behind a login, localhost, intranets, PDFs and mobile apps cannot be checked. Say so instead of guessing.
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.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 3, 2026.
plugin_asdk_app_6ac3c07576c48191a8e6013257a624cf
Download plugin data (JSON)