[{"data":1,"prerenderedAt":149},["ShallowReactive",2],{"guide:what-wcag-3-is-changing":3},{"slug":4,"title":5,"description":8,"keywords":11,"updatedAt":14,"summary":15,"sections":24,"relatedPages":105},"what-wcag-3-is-changing",{"zh-Hant-TW":6,"en":7},"WCAG 3.0 正在改變什麼？從檢查清單走向真實使用判斷","What WCAG 3.0 Is Changing: From Checklists to Real-Use Accessibility Judgment",{"zh-Hant-TW":9,"en":10},"WCAG 3.0 仍是 W3C 草案，不能當成正式符合清單。這篇指南說明它和 WCAG 2 的差異、顏色對比案例透露的方向，以及現在網站維護與產品人員該如何務實看待。","WCAG 3.0 is still a W3C draft, not a formal compliance checklist. This guide explains how it differs from WCAG 2, what the color contrast discussion reveals, and how maintainers and product people can respond pragmatically.",{"zh-Hant-TW":12,"en":13},"WCAG 3.0, WCAG 3.0 草案, WCAG 3.0 和 WCAG 2 差異, WCAG 3.0 顏色對比, APCA 對比, Lc 對比","WCAG 3.0, WCAG 3, WCAG 3.0 draft, WCAG 3.0 vs WCAG 2, WCAG 3.0 contrast, APCA contrast, Lc contrast","2026-07-03",{"zh-Hant-TW":16,"en":20},[17,18,19],"WCAG 3.0 目前是 W3C Working Draft，不是正式 Recommendation，也不應被當成現行符合要求。","它值得關注的地方，不是多一張檢查表，而是無障礙評估可能更重視真實使用、人工判斷與不同使用者需求。","顏色對比是一個好例子：WCAG 2 的 ratio 很實用，但 WCAG 3.0 討論中的方向更接近人眼實際閱讀感受。",[21,22,23],"WCAG 3.0 is currently a W3C Working Draft, not a formal Recommendation, and should not be treated as a current compliance requirement.","Its value is not another checklist. It signals a shift toward real use, human judgment, and a wider range of user needs.","Color contrast is a useful example: WCAG 2 ratios remain practical, while WCAG 3.0 discussions point toward models closer to perceived readability.",[25,38,51,64,79,92],{"title":26,"body":29},{"zh-Hant-TW":27,"en":28},"WCAG 3.0 目前是什麼狀態","What status WCAG 3.0 has today",{"zh-Hant-TW":30,"en":34},[31,32,33],"WCAG 3.0 目前仍是 W3C 的 Working Draft。它不是正式 Recommendation，也不是網站現在應該拿來宣稱符合要求的檢查清單。草案中的章節、評分方式、測試方法與術語，都仍可能繼續調整。","因此，網站維護與產品人員現在不需要問「我們是否已符合 WCAG 3.0」。比較務實的問題是：WCAG 3.0 正在透露無障礙評估未來會重視什麼，而我們現在能不能先把基礎做好。","在法規、採購與正式檢測情境中，現階段仍應以被引用的 WCAG 2.1 或 WCAG 2.2 AA 為主要基準。",[35,36,37],"WCAG 3.0 is still a W3C Working Draft. It is not a formal Recommendation and it is not a checklist that websites should use to claim current conformance. Its structure, scoring model, test methods, and terminology can still change.","That means the practical question is not “do we conform to WCAG 3.0?” The better question is what the draft reveals about where accessibility evaluation is moving, and whether teams can improve the basics now.","For legal, procurement, and formal audit contexts, WCAG 2.1 or WCAG 2.2 AA remains the realistic reference where those standards are required or adopted.",{"title":39,"body":42},{"zh-Hant-TW":40,"en":41},"WCAG 3.0 和 WCAG 2 最大差異","The main difference from WCAG 2",{"zh-Hant-TW":43,"en":47},[44,45,46],"WCAG 2 的強項是穩定、明確、可引用。它用成功準則和 A、AA、AAA 等級，讓團隊可以檢查特定問題是否通過。這套模型對檢測、採購、工程修復和自動化工具都很有價值。","但真實使用不一定能完全被「通過或失敗」描述。有些問題需要看流程、有些問題需要看使用者目標、有些問題需要人判斷內容是否真的清楚。WCAG 3.0 嘗試處理的，就是這種更廣、更接近真實使用的評估方式。","這不代表 WCAG 2 失效。比較準確的說法是：WCAG 2 仍是現實基準，而 WCAG 3.0 讓我們看到未來可能需要更完整的判斷方式。",[48,49,50],"WCAG 2 is valuable because it is stable, explicit, and easy to cite. Its success criteria and A, AA, and AAA levels give teams a way to check whether specific requirements pass or fail. That model works well for audits, procurement, engineering fixes, and automated tools.","Real use is harder to describe only as pass or fail. Some issues depend on a flow, some depend on the user goal, and some require a person to judge whether the content is actually clear. WCAG 3.0 is trying to address that broader and more realistic evaluation space.","This does not make WCAG 2 obsolete. A more accurate reading is that WCAG 2 remains the practical baseline, while WCAG 3.0 shows where accessibility judgment may need to become more complete.",{"title":52,"body":55},{"zh-Hant-TW":53,"en":54},"WCAG 3.0 更加注重什麼","What WCAG 3.0 seems to emphasize more",{"zh-Hant-TW":56,"en":60},[57,58,59],"WCAG 3.0 值得注意的不是「多一套規則」，而是它把焦點拉向更接近人的使用經驗。無障礙不只是在某個元素上確認一條規則，也要看使用者是否能理解、操作、完成任務。","這也讓自動化檢測和人工判斷的關係變得更清楚。自動化工具可以快速找到很多明確問題，但它很難完整判斷內容是否有意義、流程是否合理、使用者是否真的知道下一步該做什麼。","換句話說，WCAG 3.0 提醒我們：符合規範是重要基礎，但真正的目標仍然是讓人順利使用。",[61,62,63],"The important part of WCAG 3.0 is not simply “more rules.” It moves attention closer to human experience: whether people can understand, operate, and complete tasks, not only whether one element satisfies one rule.","It also makes the relationship between automated testing and human judgment clearer. Automated tools can find many concrete issues quickly, but they cannot fully decide whether content is meaningful, a flow makes sense, or a user can understand the next step.","In other words, WCAG 3.0 reminds us that conformance is an important foundation, but the real goal is still successful use.",{"title":65,"body":68},{"zh-Hant-TW":66,"en":67},"用顏色對比理解這個轉變","Color contrast as a simple example",{"zh-Hant-TW":69,"en":74},[70,71,72,73],"顏色對比是一個容易理解的例子。WCAG 2 會看文字前景色和背景色之間的 contrast ratio，例如一般文字常見的 AA 門檻是 4.5:1。這個模型很清楚，也很適合自動化工具。","但真實閱讀不只是一個比例。相同的前景色和背景色，放在不同字級、字重、深色模式、淺色模式、按鈕、卡片或圖片背景上，人的感受可能不同。某組顏色在大標題上看起來可以，在小尺寸細字上卻可能很吃力。","近年常被討論的 APCA，也就是 Advanced Perceptual Contrast Algorithm，會用 Lc 這類數值描述感知上的亮度對比。它代表一種方向：對比評估可能不只看固定比例，而是更接近人眼閱讀文字時感受到的清晰程度。","但這裡必須保留界線。WCAG 3.0 草案中的對比演算法尚未定案，不能說 APCA 已經是 WCAG 3.0 的正式要求。比較誠實的說法是：APCA 和 Lc 的討論，讓我們看到未來對比評估可能更重視實際可讀性。",[75,76,77,78],"Color contrast is an easy example. WCAG 2 compares the foreground and background colors of text using a contrast ratio. For normal text, a common AA threshold is 4.5:1. This model is clear and works well for automated tools.","But real readability is not only a ratio. The same foreground and background colors can feel different depending on text size, font weight, light or dark mode, buttons, cards, or image backgrounds. A color pair that works for a large heading may be difficult for small, thin text.","APCA, the Advanced Perceptual Contrast Algorithm, is often discussed in this context. It uses values such as Lc to describe perceived lightness contrast. It points toward a model that may be closer to how people experience text clarity in actual reading.","The boundary matters. The contrast algorithm for WCAG 3.0 is not yet settled, and APCA should not be described as a formal WCAG 3.0 requirement. A more honest statement is that APCA and Lc show where contrast evaluation may be moving: closer to perceived readability.",{"title":80,"body":83},{"zh-Hant-TW":81,"en":82},"這和 Accesserty 有什麼關係","How this relates to Accesserty",{"zh-Hant-TW":84,"en":88},[85,86,87],"Accesserty 不會宣稱自己支援 WCAG 3.0 符合檢查，因為 WCAG 3.0 還不是正式標準。這篇文章也不是要把草案包裝成產品功能。","比較接近的關係是方向。Signal 讓公開無障礙訊號與使用者回報更容易被看見；Pulse 讓網站維護者觀察上線後的操作困難跡象；DevCheck 讓不同角色能在瀏覽器內做初步掃描、焦點路徑、情境模擬與語意檢查；UI Kit 則從元件層減少重複出現的錯誤。","這些工具都不是完整檢測，也不是未來標準的捷徑。它們比較像是把無障礙從少數人的專案，移回網站日常維護流程裡。",[89,90,91],"Accesserty does not claim WCAG 3.0 conformance support, because WCAG 3.0 is not a formal standard yet. This article is not trying to turn a draft into a product claim.","The connection is direction. Signal makes public accessibility signals and user reports easier to notice. Pulse helps maintainers observe post-launch interaction barriers. DevCheck helps different roles run preliminary scans, manual review aids, simulations, and semantic checks in the browser. UI Kit reduces repeated defects at the component layer.","None of these tools is a complete audit or a shortcut to a future standard. They are closer to a way of bringing accessibility back into everyday website maintenance.",{"title":93,"body":96},{"zh-Hant-TW":94,"en":95},"現在可以怎麼做","What to do now",{"zh-Hant-TW":97,"en":101},[98,99,100],"不用等 WCAG 3.0 正式發布才開始改善。現在最務實的做法，是繼續用 WCAG 2.1 或 2.2 AA 當基準，同時建立更日常的檢查、回報和追蹤方式。","自動化掃描可以當起點，但不要把掃描結果當成結論。顏色對比、焦點順序、可及名稱、圖片替代文字、PDF 結構、登入後流程和表單錯誤狀態，都需要在真實畫面中被確認。","如果 WCAG 3.0 的方向有一個值得提前學習的地方，那就是：無障礙不只是符合規則，而是讓更多人能更穩定地完成他們原本想做的事。",[102,103,104],"Teams do not need to wait for WCAG 3.0 to become final before improving. The practical approach is to keep using WCAG 2.1 or 2.2 AA as the baseline, while building more regular ways to check, report, and track issues.","Automated scans can be a starting point, but scan results should not be the conclusion. Color contrast, focus order, accessible names, image alt text, PDF structure, authenticated flows, and form error states all need to be confirmed in real screens.","If WCAG 3.0 offers one lesson worth learning early, it is this: accessibility is not only about satisfying rules. It is about helping more people complete what they came to do.",[106,113,120,125,130,135,140,145],{"label":107,"path":109,"description":110},{"zh-Hant-TW":108,"en":108},"Accesserty DevCheck","\u002Fdevcheck",{"zh-Hant-TW":111,"en":112},"用瀏覽器內工具檢查本機、測試站、登入後頁面與互動狀態。","Run browser-based checks on local builds, staging pages, authenticated screens, and interactive states.",{"label":114,"path":116,"description":117},{"zh-Hant-TW":115,"en":115},"Accesserty Pulse","\u002Fpulse",{"zh-Hant-TW":118,"en":119},"觀察上線後的操作困難訊號、機器掃描摘要與使用者回報。","Observe post-launch interaction signals, machine scan summaries, and user reports.",{"label":121,"path":124},{"zh-Hant-TW":122,"en":123},"WCAG 術語頁","WCAG glossary page","\u002Fglossary\u002Fwcag",{"label":126,"path":129},{"zh-Hant-TW":127,"en":128},"自動化與人工檢測術語頁","Automated vs manual testing glossary page","\u002Fglossary\u002Fautomated-vs-manual-accessibility-testing",{"label":131,"path":134},{"zh-Hant-TW":132,"en":133},"自動化檢測限制指南","Automated accessibility checks limits guide","\u002Fguides\u002Fautomated-accessibility-checks-limits",{"label":136,"path":139},{"zh-Hant-TW":137,"en":138},"焦點路徑檢查指南","Focus path review guide","\u002Fguides\u002Fhow-to-check-keyboard-focus-path",{"label":141,"path":144},{"zh-Hant-TW":142,"en":143},"上線後無障礙監測指南","Post-launch accessibility monitoring guide","\u002Fguides\u002Fpost-launch-accessibility-monitoring",{"label":146,"path":148},{"zh-Hant-TW":147,"en":147},"W3C WCAG 3.0 Working Draft","https:\u002F\u002Fwww.w3.org\u002FTR\u002Fwcag-3.0\u002F",1789828082018]