← กลับไปยังคุณสมบัติ
Pro

ตรวจการเข้าถึง

เรียกใช้การตรวจ WCAG 2.1 Level AA อัตโนมัติ

ตรวจ WCAG อัตโนมัติเพื่อหาปัญหาที่มองไม่เห็น

ตัวอย่างสด
example.com/app
Accessibility Audit
3 Errors5 Warnings12 Passed
Missing alt text on 3 images
Images must have an alt attribute for screen readers. Show elements →
Contrast ratio too low (2.1:1)
Text on .hero-subtitle fails WCAG AA (minimum 4.5:1). Show element →
Form input missing label
input#email has no associated label element. Show element →
Missing landmark regions
Page lacks main and nav landmark elements. Learn more →
12 checks passed
Language attribute, heading hierarchy, link text, focus indicators...
คุณสมบัติหลัก

ตรวจ WCAG 2.1 AA

Runs automated checks against WCAG 2.1 Level AA success criteria including perceivability, operability, understandability, and robustness categories. แต่ละ check shows the specific criterion (e.g., 1.4.3 Contrast, 1.1.1 Non-text Content) and pass/fail status.

วิเคราะห์คอนทราสต์

Calculates the contrast ratio between text and background colors for ทุก text element บนหน้า. Flags elements below 4.5:1 for normal text or 3:1 for large text (18px+ or 14px+ bold). Shows the actual ratio and the minimum required.

ตรวจ Alt Text

Scans ทุก img, svg, and image role element. Flags missing alt attributes, empty alt on non-decorative images, and overly generic alt text ("image", "photo"). Suggests whether each image needs descriptive alt, empty alt (decorative), or role="presentation".

ARIA และ Semantic

Checks for improper ARIA role usage (roles on wrong elements), missing required ARIA attributes (e.g., aria-label on icon buttons), duplicate IDs referenced by aria-labelledby, and missing landmark regions (no main, no nav). Recommends semantic HTML alternatives.

ตรวจ Label ฟอร์ม

Ensures ทุก form input (text, email, password, checkbox, select) has an associated label — either through a label element with matching for/id, aria-label, or aria-labelledby. Unlabeled inputs are inaccessible to screen readers.

จัดลำดับความสำคัญ

Issues are categorized as Errors (must fix — barriers to access), Warnings (should fix — potential barriers), and Passes (confirmed accessible). Error count is prominently displayed. Click ใดก็ได้ issue to highlight the affected element บนหน้า.

กรณีการใช้งานทั่วไป

ตรวจก่อนเปิดตัว

Before launching a new page or feature, run the Accessibility Inspector to catch issues early. Missing alt text, unlabeled form fields, and contrast violations are easy to fix during development but expensive to discover in production.

กฎหมาย

Mใดก็ได้ jurisdictions require WCAG 2.1 Level AA compliance (ADA in the US, EAA in the EU). Run the inspector on your public-facing pages to identify compliance gaps before they become legal risks.

รวมกับ QA

Include accessibility checking as part of your QA process. After visual QA and functional testing, run the Accessibility Inspector to verify that the implementation doesn't introduce accessibility regressions.

ฝึกทีม

Run the inspector on your current site during a team meeting to show real accessibility issues. The visual highlighting and clear explanations help developers understand what accessible markup looks like and why it matters.

ตรวจบุคคลที่สาม

Audit pages that include third-party widgets, embedded content, or user-generated HTML. These sources often introduce accessibility issues (missing alt text, contrast violations) that you're still responsible for as หน้า owner.

วิธีใช้งาน
1

เปิดใช้งาน

เปิด DevSuite Pro dock ลอย and click the Accessibility Inspector icon. The tool scans หน้า DOM for accessibility issues.

2

ดูรายงาน

A categorized report appears with Errors (red), Warnings (yellow), and Passes (green). แต่ละ section lists specific issues with affected elements and WCAG criteria references.

3

ไฮไลท์

Click ใดก็ได้ issue to highlight the affected element บนหน้า with a colored border and scroll to it. The connection between the report and the DOM element is immediate.

4

คำแนะนำ

แต่ละ issue includes a specific recommendation: "Add alt text describing the image content", "Increase font color contrast to at least 4.5:1", "Add a label element with for='email'".

5

แก้ไขและตรวจซ้ำ

Make changes in your code, reload หน้า, and run the audit again. The error count should decrease as issues are resolved. Aim for zero errors.

พร้อมที่จะลองหรือยัง? ตรวจการเข้าถึง?

ติดตั้ง DevSuite Pro ฟรีและปลดล็อกเครื่องมือสำหรับนักพัฒนามากกว่า 39 รายการสำหรับเบราว์เซอร์ของคุณ

เพิ่มใน Chrome เพิ่มไปยัง Edge เพิ่มใน FireFox