[{"data":1,"prerenderedAt":117},["ShallowReactive",2],{"glossary:automated-vs-manual-accessibility-testing":3},{"slug":4,"term":5,"title":6,"description":8,"keywords":11,"updatedAt":14,"tldr":15,"sections":24,"faqs":58,"relatedPages":73,"references":108},"automated-vs-manual-accessibility-testing","Automated vs Manual Accessibility Testing",{"zh-Hant-TW":7,"en":5},"自動化無障礙檢測與人工檢測差在哪？",{"zh-Hant-TW":9,"en":10},"自動化檢測可以快速找出部分 WCAG 與最佳實務問題，但人工檢測仍負責理解內容、任務流程、鍵盤操作與輔助科技使用情境。","Automated accessibility testing can quickly surface some WCAG and best-practice issues, while manual testing is still needed for content meaning, task flow, keyboard use, and assistive technology context.",{"zh-Hant-TW":12,"en":13},"自動化無障礙檢測, 人工無障礙檢測, axe-core, WCAG 檢測限制, 輔助科技測試","automated accessibility testing, manual accessibility testing, axe-core limitations, accessibility testing limits, assistive technology testing","2026-06-29",{"zh-Hant-TW":16,"en":20},[17,18,19],"自動化檢測適合快速找出可被機器判斷的問題，例如缺少標籤、ARIA 錯誤、部分對比與結構問題。","人工檢測負責判斷內容是否清楚、流程是否可完成、鍵盤操作是否合理，以及輔助科技使用者是否真的理解。","比較可靠的流程不是二選一，而是先用自動化縮小範圍，再用人工檢查完成判斷。",[21,22,23],"Automated checks are useful for machine-detectable issues such as missing labels, ARIA errors, some contrast problems, and structural issues.","Manual review is still needed to judge clarity, task completion, keyboard behavior, and assistive technology experience.","A reliable workflow uses automation to narrow the surface, then manual review to make the actual judgment.",[25,36,47],{"title":26,"body":29},{"zh-Hant-TW":27,"en":28},"自動化檢測能做什麼？","What automated testing can do",{"zh-Hant-TW":30,"en":33},[31,32],"自動化檢測擅長處理規則明確、能由 DOM、CSS 或可計算狀態判斷的問題。它可以在開發、QA、內容上架或 release 前快速提醒團隊：哪些頁面和元件需要先看。","這類檢查很適合當作第一層防線，但不應被當成完整檢測。掃描結果為零，不代表使用者一定能完成任務。",[34,35],"Automated testing works best when the rule can be evaluated from DOM, CSS, or a computable state. It can quickly tell a team which pages and components deserve attention during development, QA, content publishing, or release review.","It is a strong first layer, but it is not a full audit. A scan with no findings does not prove that users can complete the task.",{"title":37,"body":40},{"zh-Hant-TW":38,"en":39},"人工檢測負責哪些判斷？","What manual review is responsible for",{"zh-Hant-TW":41,"en":44},[42,43],"人工檢測會看機器不容易理解的事情：連結文字是否有脈絡、替代文字是否說到重點、錯誤訊息是否足以讓人繼續、對話框焦點是否符合操作預期。","它也會確認使用者能否在真實任務中完成流程，例如登入、搜尋、加入購物車、填寫表單、取消操作或下載文件。",[45,46],"Manual review covers things machines cannot reliably understand: whether link text has context, alt text is useful, error messages help users continue, or dialog focus matches the expected interaction.","It also checks whether users can complete real tasks such as signing in, searching, adding to cart, filling forms, cancelling actions, or downloading documents.",{"title":48,"body":51},{"zh-Hant-TW":49,"en":50},"Accesserty 的實務位置","Where Accesserty fits",{"zh-Hant-TW":52,"en":55},[53,54],"DevCheck 把自動化檢查放在瀏覽器內，讓團隊能在本機、測試站、登入後頁面與互動狀態中先找出可被機器偵測的風險。它也提供人工檢視輔助、情境模擬與語意輔助，協助人工判斷更具體。","Pulse 則接續上線後的情境：如果使用者在真實頁面反覆點擊、出現疑似鍵盤操作未明或表單反覆嘗試，這些訊號可以提醒團隊回頭做人工確認。",[56,57],"DevCheck brings automated checks into the browser so teams can inspect local builds, staging pages, authenticated views, and interactive states. Its manual review aids, simulations, and semantic assistance help make manual review more concrete.","Pulse continues after launch: repeated clicks, possible keyboard dead interactions, or repeated form attempts can point teams back to pages that need manual review.",[59,66],{"question":60,"answer":63},{"zh-Hant-TW":61,"en":62},"自動化檢測可以取代人工檢測嗎？","Can automated testing replace manual testing?",{"zh-Hant-TW":64,"en":65},"不可以。它能加速發現部分問題，但不能完整判斷內容意義、流程可用性、輔助科技體驗或法規要求。","No. It speeds up finding some issues, but it cannot fully judge meaning, task usability, assistive technology experience, or legal compliance.",{"question":67,"answer":70},{"zh-Hant-TW":68,"en":69},"應該先做哪一種？","Which should come first?",{"zh-Hant-TW":71,"en":72},"通常先跑自動化檢測找出明顯風險，再用人工檢查主要任務與互動狀態。兩者應該在修正後都重新確認。","Usually start with automated checks to find obvious risks, then manually review key tasks and interaction states. Re-test both after fixes.",[74,81,86,91,98,103],{"label":75,"path":77,"description":78},{"zh-Hant-TW":76,"en":76},"Accesserty DevCheck","\u002Fdevcheck",{"zh-Hant-TW":79,"en":80},"用瀏覽器內工具檢查網站無障礙、WCAG、ARIA、鍵盤操作、焦點路徑、AI 語意與 PDF 結構訊號。","Run browser-based checks for web accessibility, WCAG, ARIA, keyboard access, focus paths, AI semantic review, and PDF structure signals.",{"label":82,"path":85},{"zh-Hant-TW":83,"en":84},"自動化檢測限制指南","Automated accessibility checks limits guide","\u002Fguides\u002Fautomated-accessibility-checks-limits",{"label":87,"path":90},{"zh-Hant-TW":88,"en":89},"上線後無障礙監測指南","Post-launch accessibility monitoring guide","\u002Fguides\u002Fpost-launch-accessibility-monitoring",{"label":92,"path":94,"description":95},{"zh-Hant-TW":93,"en":93},"Accesserty Pulse","\u002Fpulse",{"zh-Hant-TW":96,"en":97},"觀察上線後的操作困難訊號、機器掃描摘要與使用者回報。","Observe post-launch interaction signals, machine scan summaries, and user reports.",{"label":99,"path":102},{"zh-Hant-TW":100,"en":101},"網站上線前無障礙檢測指南","Accessibility testing before launch guide","\u002Fguides\u002Faccessibility-testing-before-launch",{"label":104,"path":107},{"zh-Hant-TW":105,"en":106},"WCAG 檢測工具","WCAG compliance tool","\u002Fwcag-compliance-tool",[109,113],{"label":110,"path":112},{"zh-Hant-TW":111,"en":111},"W3C WAI - Easy Checks","https:\u002F\u002Fwww.w3.org\u002FWAI\u002Ftest-evaluate\u002Feasy-checks\u002F",{"label":114,"path":116},{"zh-Hant-TW":115,"en":115},"W3C WAI - Evaluation Tools","https:\u002F\u002Fwww.w3.org\u002FWAI\u002Ftest-evaluate\u002Ftools\u002F",1789828082656]