اللغات

Accessibility Tester

Free, no signup. Audit a rendered page with axe-core for WCAG 2.2 A/AA patterns, then turn each finding into a targeted engineering fix.

Built by Patrick Stox

Checks run from our server; we fetch the URL you enter and don't keep the results. This launches a metered browser audit. Stylesheets are allowed for computed accessibility checks; media and fonts are blocked. Automated checks catch only part of WCAG issues and never replace manual testing. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Accessibility Checker? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
Sample report
Illustrative example — axe rule output for fixed markup
CRITICAL · Images must have alternate text (1)
Add a meaningful alt value when the image conveys information, or alt="" when it is decorative.
img.hero<img class="hero" src="product.jpg">
Element does not have an alt attribute.
The example shows an automated rule result, not a judgment about what the correct alternative text should say.
 
 
How to use it
  1. Enter a public page URL and run the metered browser audit.
  2. Start with critical and serious violations, but review every rule and affected selector.
  3. Use the HTML excerpt, error summary, and targeted repair guidance to locate the component.
  4. Retest after fixing, then complete manual keyboard, screen-reader, zoom, content, and task-flow checks.
 
 
       
     
   
What the results mean
Each card is one axe rule with an impact level and affected-node count. Selectors identify elements in the audited DOM; HTML and error summaries explain the observed pattern. A zero-violation run only means no enabled automated rule fired.
How it works
A metered browser loads the public page with stylesheets enabled for computed checks while media and fonts are blocked. It runs axe-core against WCAG 2.2 A/AA-tagged rules and returns bounded violations and nodes. The page formats severity and adds rule-specific repair guidance.
Features
  • Rendered-browser axe-core audit.
  • WCAG 2.2 A/AA rule selection.
  • Impact, selectors, HTML excerpts, and error summaries.
  • Targeted repair guidance for supported axe rules.
  • Explicit not-evaluated state when the browser audit cannot complete.
Limitations
Automation catches only part of accessibility. The audit does not use your login, perform interactions, cover every application state, judge meaningful alt text, or replace testing with disabled users and assistive technologies. Blocked media/fonts and dynamic timing can also change the rendered state.
 
Frequently asked questions
Does passing axe mean a page is WCAG compliant?
No. Automated checks detect only a portion of accessibility barriers. WCAG conformance requires manual keyboard, screen-reader, content, focus, error, and task-flow testing in addition to automation.
Which WCAG level does this test?
The browser run uses axe-core rules tagged for WCAG 2.2 Level A and AA. The result is a rule-violation report, not a conformance certificate.
Why might the audit miss a modal or logged-in screen?
The metered browser loads the supplied public URL without your authenticated session or scripted interaction. Hidden states, personalized flows, consent choices, and components opened later may not be evaluated.
What does a violation severity mean?
Critical, serious, moderate, and minor are axe impact levels used to prioritize review. Impact does not replace the associated WCAG criterion, user context, or engineering investigation.
People also explore
ToolMobile-Friendly TesterToolColor Contrast CheckerToolHeading Structure CheckerArticleSEO and AccessibilityArticleOn-Page SEO: Complete GuideArticleAlt Text
 
 
 
Feature requests for Accessibility Checker
 

Upvote what you want most. New ideas can be submitted from the floating Feedback menu;
      requests appear here once approved, and the most-wanted rise to the top.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
   
  
حول الأداة
شغّل واحد معروضًا في المتصفح axe-core WCAG 2.2 واحد/AA تحقّق مع شدة, متأثر selectors, و إصلاح إرشادات.
مجاني, من دون تسجيل. تدقيق واحد معروض صفحة مع axe-core من أجل WCAG 2.2 واحد/AA أنماط, ثم يحوّل كل نتيجة إلى واحد موجّه هندسة أصلح.
الميزات
  • Rendered-browser axe-core تدقيق.
  • WCAG 2.2 واحد/AA قاعدة اختيار.
  • Impact, selectors, HTML مقتطفات, و خطأ ملخصات.
  • موجّه إصلاح إرشادات من أجل مدعوم axe قواعد.
  • صريح not-evaluated حالة عندما ال متصفح تدقيق لا يمكن مكتمل.
كيفية العمل
كل بطاقة هو واحد axe قاعدة مع واحد impact مستوى و affected-node عدد. Selectors حدّد عناصر في ال خاضع للتدقيق DOM; HTML و خطأ ملخصات اشرح ال مرصود نمط. واحد مقاس متصفح يحمّل ال عام صفحة مع أوراق أنماط مفعّل من أجل محسوب تحقّقات بينما وسائط و fonts هي محظور. إنه تشغيل axe-core مقابل WCAG 2.2 واحد/AA-tagged قواعد و يعيد محدود violations و nodes. ال صفحة تنسيقات شدة و يضيف rule-specific إصلاح إرشادات.
القيود
  • Automation يلتقط فقط جزء من إمكانية الوصول. ال تدقيق يفعل ليس استخدم الخاص بك تسجيل الدخول, perform تفاعلات, يغطي كل تطبيق حالة, judge مهم alt نص, أو استبدال اختبار مع معطّل مستخدمون و assistive technologies. محظور وسائط/fonts و dynamic توقيت يمكن أيضًا غيّر ال معروض حالة.
الأسئلة الشائعة
يفعل اجتياز axe يعني واحد صفحة هو WCAG ممتثل?
لا. آلي تحقّقات يكتشف فقط واحد portion من إمكانية الوصول حواجز. WCAG conformance يتطلب manual لوحة المفاتيح, screen-reader, محتوى, تركيز, خطأ, و task-flow اختبار في إضافة إلى automation.
أي WCAG مستوى يفعل هذا اختبار?
ال متصفح شغّل يستخدم axe-core قواعد tagged من أجل WCAG 2.2 مستوى واحد و AA. ال نتيجة هو واحد rule-violation تقرير, ليس واحد conformance certificate.
لماذا ربما ال تدقيق يفوّت واحد modal أو logged-in شاشة?
ال مقاس متصفح يحمّل ال مقدّم عام عنوان URL من دون الخاص بك موثّق جلسة أو scripted تفاعل. مخفي حالات, personalized تدفقات, consent خيارات, و مكوّنات opened لاحقًا قد ليس يكون مُقيَّم.
ما يفعل واحد violation شدة يعني?
حرج, serious, moderate, و minor هي axe impact levels مستخدم إلى يعطي الأولوية مراجعة. Impact يفعل ليس استبدال ال associated WCAG criterion, مستخدم سياق, أو هندسة تحقيق.