[{"data":1,"prerenderedAt":147},["ShallowReactive",2],{"guide:accessibility-statement-example-before-you-publish":3},{"slug":4,"title":5,"description":8,"keywords":11,"updatedAt":14,"summary":15,"sections":24,"relatedPages":106},"accessibility-statement-example-before-you-publish",{"zh-Hant-TW":6,"en":7},"無障礙聲明範例：發布前應該先確認什麼？","Accessibility Statement Example: What to Include Before You Publish",{"zh-Hant-TW":9,"en":10},"範例和產生器可以幫助起稿，但一份有用的無障礙聲明不能只貼上漂亮文字。這篇說明網站維護者發布前應確認的範圍、標準、限制、回報管道與維護節奏。","Examples and generators can help you start, but a useful accessibility statement is not just polished text. This guide explains the scope, standards, limits, feedback path, and maintenance rhythm to check before publishing.",{"zh-Hant-TW":12,"en":13},"無障礙聲明範例, 無障礙聲明範本, 網站無障礙聲明, accessibility statement example, accessibility statement generator","accessibility statement example, website accessibility statement example, accessibility statement template, accessibility statement generator, what to include in an accessibility statement","2026-07-24",{"zh-Hant-TW":16,"en":20},[17,18,19],"好的無障礙聲明範例不是一段保證文字，而是讓使用者知道範圍、標準、限制與回報方式。","W3C WAI generator 適合用來起稿；發布前仍要依網站實際狀態補上具體內容。","Accesserty Signal 會把清楚、可找到的聲明視為公開訊號，但它仍不是認證或完整符合保證。",[21,22,23],"A good accessibility statement example is not a promise paragraph; it helps users understand scope, standards, limits, and feedback options.","The W3C WAI generator is a useful starting point, but teams still need to fill it with site-specific evidence before publishing.","Accesserty Signal treats clear and findable statements as public signals, not certifications or whole-site guarantees.",[25,36,62,73,84,95],{"title":26,"body":29},{"zh-Hant-TW":27,"en":28},"先決定這份聲明要幫誰","Start with who the statement is for",{"zh-Hant-TW":30,"en":33},[31,32],"無障礙聲明常被拿來當合規文件，但它首先應該服務遇到阻礙的人。當使用者無法送出表單、看不懂錯誤提示、操作不了選單或需要替代方式時，聲明應該能提供下一步。","所以，範例或範本只能當起點。發布前要確認文字是否真的回答使用者會問的問題：這個網站涵蓋哪些範圍、目前依照什麼標準、哪裡可能還有限制、遇到問題要找誰。",[34,35],"Accessibility statements are often treated as compliance documents, but they should first serve people who encounter barriers. When someone cannot submit a form, understand an error message, operate a menu, or needs an alternative path, the statement should provide a next step.","That means an example or template is only a starting point. Before publishing, check whether the text answers the questions users actually have: what the statement covers, which standard the site uses, where limits may remain, and who to contact when something fails.",{"title":37,"body":40,"items":47},{"zh-Hant-TW":38,"en":39},"一份可用聲明至少應該包含什麼","What a usable statement should include",{"zh-Hant-TW":41,"en":44},[42,43],"W3C WAI 的 accessibility statement guidance 建議，聲明至少應包含對身心障礙者無障礙的承諾、適用的無障礙標準，以及使用者遇到問題時的聯絡方式。這是最低基礎，不是完整終點。","更實用的聲明通常還會補上已知限制、組織已採取的措施、技術前提、測試過的環境，以及適用的在地法規或政策。這些資訊不需要寫得像檢測報告，但要具體到使用者和維護者都能理解。",[45,46],"W3C WAI guidance says an accessibility statement should at least include a commitment to accessibility for people with disabilities, the accessibility standard applied, and contact information for users who encounter problems. That is the minimum base, not the full endpoint.","A more practical statement often also includes known limitations, measures the organization has taken, technical prerequisites, tested environments, and applicable national or local laws or policies. It does not need to read like an audit report, but it should be specific enough for users and maintainers to understand.",{"zh-Hant-TW":48,"en":55},[49,50,51,52,53,54],"網站或服務名稱：清楚指出這份聲明涵蓋哪個網站、App、服務或版本。","適用範圍：說明是否涵蓋整站、部分頁面、登入後流程、PDF、第三方內容或行動 App。","標準與狀態：說明參考 WCAG 2.2、WCAG 2.1、EN 301 549 或在地要求，以及目前是完全符合、部分符合、尚在改善或尚未完整評估。","已知限制與替代方式：用使用者能理解的語言描述問題，不只列出成功準則編號。","回報管道：提供可用的表單、email、電話或其他聯絡方式，並說明預期回應方式或時間。","維護資訊：列出更新日期、評估方式、負責部門或後續改善節奏。",[56,57,58,59,60,61],"Website or service name: identify which website, app, service, or version the statement covers.","Scope: explain whether it covers the whole site, selected pages, authenticated flows, PDFs, third-party content, or mobile apps.","Standard and status: name WCAG 2.2, WCAG 2.1, EN 301 549, or local requirements where relevant, and say whether the content is fully conformant, partially conformant, still being improved, or not fully assessed.","Known limits and alternatives: describe problems in language users understand, not only by success criterion number.","Feedback path: provide a usable form, email, phone number, or other contact method, and say how or when people can expect follow-up.","Maintenance information: include update date, assessment approach, responsible team, or ongoing improvement rhythm.",{"title":63,"body":66},{"zh-Hant-TW":64,"en":65},"使用 generator 時，不要讓範本替你做判斷","When using a generator, do not let the template make the judgment",{"zh-Hant-TW":67,"en":70},[68,69],"W3C WAI 的 Accessibility Statement Generator 是可靠的起稿工具。它可以協助整理基本資訊、組織已採取的措施、技術資訊、回報與申訴流程，並且是在瀏覽器中產生可下載內容。","但產生器無法知道你的網站實際範圍、哪些頁面測過、哪些流程仍有問題、第三方內容是否在控制範圍內。這些判斷必須由網站維護者、產品團隊、法務或無障礙專家依實際情況補上。",[71,72],"The W3C WAI Accessibility Statement Generator is a reliable drafting tool. It helps organize basic information, measures taken by the organization, technical information, feedback, and complaints process, and it generates downloadable content in the browser.","But the generator cannot know your actual website scope, which pages were reviewed, which flows still have issues, or whether third-party content is under your control. Those judgments must be filled in by maintainers, product teams, legal teams, or accessibility specialists based on the real service.",{"title":74,"body":77},{"zh-Hant-TW":75,"en":76},"避免把聲明寫成過度承諾","Avoid turning the statement into an overclaim",{"zh-Hant-TW":78,"en":81},[79,80],"最危險的聲明不是寫得不夠漂亮，而是寫得過度確定。例如「完全符合所有無障礙標準」或「100% accessibility compliant」如果沒有範圍、日期、測試方式與已知限制，反而會降低可信度。","比較誠實的寫法是：說明目前依據什麼標準、已檢查哪些範圍、哪些問題正在改善、使用者遇到阻礙時可以怎麼聯絡。這樣的聲明比較像維護入口，而不是一次性的品牌宣示。",[82,83],"The riskiest statement is not one that sounds plain; it is one that sounds too certain. Claims such as “fully compliant with all accessibility standards” or “100% accessibility compliant” become less credible when they do not include scope, date, assessment method, and known limits.","A more honest approach is to explain which standard you refer to, what scope was reviewed, what is still being improved, and how users can contact you when they encounter barriers. That makes the statement a maintenance entry point, not a one-time brand promise.",{"title":85,"body":88},{"zh-Hant-TW":86,"en":87},"發布後還要讓它被找到","After publishing, make it findable",{"zh-Hant-TW":89,"en":92},[90,91],"一份寫得好的聲明如果藏在難找的位置，實際效果仍然有限。W3C WAI 建議聲明應該容易找到，可以從頁尾、說明選單、網站地圖、關於頁或其他顯眼位置連到聲明。","連結文字也應一致且清楚，例如 Accessibility 或 Accessibility Statement。不要只放在圖片、PDF、模糊政策頁或需要多次互動才找得到的位置。",[93,94],"A well-written statement has limited value if it is hard to find. W3C WAI recommends making accessibility statements easy to locate, with links from places such as the footer, help menu, sitemap, about page, or other prominent areas.","Link text should also be consistent and clear, such as Accessibility or Accessibility Statement. Avoid placing the only entry point inside images, PDFs, vague policy pages, or interactions that require several steps to discover.",{"title":96,"body":99},{"zh-Hant-TW":97,"en":98},"Accesserty 如何看待這類聲明","How Accesserty treats these statements",{"zh-Hant-TW":100,"en":103},[101,102],"Accesserty Signal 會把找到的公開無障礙聲明視為一種可追溯訊號。這代表使用者可以更快看到網站有公開說明與回報入口，但不代表 Accesserty 認證該網站，也不代表整站沒有問題。","對網站維護者來說，目標不是寫出一段最安全、最漂亮的文字，而是建立一個能被找到、能被理解、能持續更新的公開入口。這比單純追求「範例長得像不像」更重要。",[104,105],"Accesserty Signal treats discovered public accessibility statements as traceable signals. That means users can more quickly see that a website has a public explanation and feedback entry point. It does not mean Accesserty certifies the site, and it does not mean the whole site has no barriers.","For maintainers, the goal is not to write the safest or most polished paragraph. The goal is to create a public entry point that can be found, understood, and maintained over time. That matters more than whether the statement looks like a generic example.",[107,112,119,127,132,137,142],{"label":108,"path":111},{"zh-Hant-TW":109,"en":110},"無障礙聲明術語頁","Accessibility statement glossary page","\u002Fglossary\u002Faccessibility-statement",{"label":113,"path":115,"description":116},{"zh-Hant-TW":114,"en":114},"Accesserty Signal","\u002Fsignal",{"zh-Hant-TW":117,"en":118},"在搜尋結果中顯示公開無障礙訊號，並讓使用者回報遇到的阻礙。","Show public accessibility signals in search results and let users report barriers.",{"label":120,"path":123,"description":124},{"zh-Hant-TW":121,"en":122},"Accesserty 如何理解無障礙訊號","How Accesserty understands accessibility signals","\u002Fpublic-data",{"zh-Hant-TW":125,"en":126},"了解公開標章、聲明、ALLY、回報與機器掃描摘要的差異與限制。","Understand the differences and limits of public badges, statements, ALLY, reports, and machine scan summaries.",{"label":128,"path":131},{"zh-Hant-TW":129,"en":130},"如何閱讀無障礙聲明","How to read an accessibility statement","\u002Fguides\u002Fhow-to-read-accessibility-statements",{"label":133,"path":136},{"zh-Hant-TW":134,"en":135},"為什麼無障礙聲明應該容易被找到","Why accessibility statements should be easy to find","\u002Fguides\u002Fwhy-accessibility-statements-should-be-easy-to-find",{"label":138,"path":141},{"zh-Hant-TW":139,"en":140},"W3C WAI：Developing an Accessibility Statement","W3C WAI: Developing an Accessibility Statement","https:\u002F\u002Fwww.w3.org\u002FWAI\u002Fplanning\u002Fstatements\u002F",{"label":143,"path":146},{"zh-Hant-TW":144,"en":145},"W3C WAI 無障礙聲明產生器","W3C WAI accessibility statement generator","https:\u002F\u002Fwww.w3.org\u002FWAI\u002Fplanning\u002Fstatements\u002Fgenerator\u002F",1789828081171]