[{"data":1,"prerenderedAt":181},["ShallowReactive",2],{"guide:why-accessibility-statements-should-be-easy-to-find":3},{"slug":4,"title":5,"description":8,"keywords":11,"updatedAt":14,"summary":15,"sections":26,"relatedPages":125},"why-accessibility-statements-should-be-easy-to-find",{"zh-Hant-TW":6,"en":7},"為什麼無障礙聲明應該容易被找到？","Why Accessibility Statements Should Be Easy to Find",{"zh-Hant-TW":9,"en":10},"無障礙聲明的問題不只在於有沒有寫，而在於使用者、搜尋引擎與輔助工具是否能在需要時找到。這篇研究型文章說明聲明可見性為什麼是一種公開無障礙訊號。","The issue with accessibility statements is not only whether they exist, but whether people, search engines, and assistive tools can find them when needed. This research-oriented guide explains why statement findability is a public accessibility signal.",{"zh-Hant-TW":12,"en":13},"無障礙聲明, 網站無障礙聲明, 找不到無障礙聲明, 無障礙聲明範例, 無障礙回報, 公開無障礙訊號, accessibility statement","accessibility statement, website accessibility statement, accessibility statement example, find accessibility statement, public accessibility signals, accessibility feedback","2026-07-25",{"zh-Hant-TW":16,"en":21},[17,18,19,20],"無障礙聲明不是資料集、標章或保證書；它比較像網站對外公開的一條可追溯線索。","W3C WAI 建議 accessibility statement 應容易找到，EU model accessibility statement 也明確把可存取、可找到與定期更新放進制度設計。","在實務觀察中，聲明可能藏在頁尾、政策頁、PDF、語言版本或客服流程裡；「存在」不等於「可被需要的人找到」。","Accesserty 把聲明視為公開無障礙訊號：找到它不代表整站無障礙，找不到它也不代表網站沒有做事。",[22,23,24,25],"An accessibility statement is not a dataset, badge, or guarantee. It is better understood as a traceable public clue.","W3C WAI recommends that accessibility statements be easy to find, and the EU model accessibility statement embeds access, findability, and regular review into its public-sector model.","In practice, statements may be buried in footers, policy pages, PDFs, language versions, or support flows. Existing is not the same as being findable when needed.","Accesserty treats statements as public accessibility signals: finding one does not prove whole-site accessibility, and not finding one does not prove that no accessibility work exists.",[27,40,53,64,88,101,114],{"title":28,"body":31},{"zh-Hant-TW":29,"en":30},"研究問題：聲明存在，為什麼還是不容易被看見？","Research question: why can a statement exist and still be hard to see?",{"zh-Hant-TW":32,"en":36},[33,34,35],"很多討論會先問網站有沒有 accessibility statement。這個問題重要，但不完整。對真正遇到阻礙的人來說，更直接的問題是：我現在能不能找到它？它有沒有告訴我下一步？","Accesserty 在整理公開無障礙訊號時，反覆看到一個實務現象：聲明可能存在，但入口不穩定。它可能在頁尾、政策頁、法規頁、PDF、客服說明、特定語言版本，或只有站內搜尋才找得到。這不代表網站沒有做無障礙，也不代表聲明沒有價值；但它會降低聲明被使用的機率。","因此這篇文章不把無障礙聲明當成「有或沒有」的二元資料，而是把它放進公開訊號的問題來看：一個網站對外提供了什麼線索？那些線索是否能被需要的人、搜尋引擎、輔助工具與維護者找到？",[37,38,39],"Many discussions begin by asking whether a site has an accessibility statement. That question matters, but it is incomplete. For someone who has just encountered a barrier, the more immediate question is: can I find it now, and does it tell me what to do next?","While organizing public accessibility signals, Accesserty repeatedly sees a practical pattern: a statement may exist, but the entry point is unstable. It may live in a footer, policy page, legal page, PDF, support article, a specific language version, or only be discoverable through site search. That does not mean the site has done nothing, and it does not make the statement worthless. It does reduce the chance that the statement will be used.","This article therefore does not treat accessibility statements as a simple yes-or-no field. It treats them as public signals: what clues does a website expose, and can those clues be found by people, search engines, assistive tools, and maintainers when they are needed?",{"title":41,"body":44},{"zh-Hant-TW":42,"en":43},"官方指引其實已經把可見性放進要求裡","Official guidance already treats findability as part of the work",{"zh-Hant-TW":45,"en":49},[46,47,48],"W3C WAI 在 accessibility statement 指引中，明確把「容易找到」列為聲明應被處理的位置問題，並建議可從頁尾、help menu、sitemap、about page 等多個地方連到聲明。這不是裝飾性建議，而是使用者能否在遇到問題時找到入口的基礎。","EU 的 model accessibility statement 也有類似邏輯。Commission Implementing Decision (EU) 2018\u002F1523 說明，public sector bodies 應使用 model accessibility statement，並鼓勵聲明定期、至少每年檢視更新；也鼓勵讓聲明可從網站每一頁容易取得。這表示制度關心的不只是內容格式，也關心可取得性與可重用性。","這些官方資料提供了一個保守但清楚的結論：無障礙聲明不是只要「有一頁」就結束。它應該是一個使用者能預期找到、能理解、能用來採取下一步的公開入口。",[50,51,52],"W3C WAI guidance on accessibility statements explicitly treats findability as part of statement placement. It recommends linking from multiple places, such as the footer, help menu, sitemap, about page, and other prominent areas. This is not a cosmetic recommendation; it affects whether people can find an entry point when they encounter a barrier.","The EU model accessibility statement follows a similar logic. Commission Implementing Decision (EU) 2018\u002F1523 establishes a model accessibility statement for public sector bodies, encourages regular review and updates at least annually, and encourages statements to be easily accessible from each web page. That means the model is concerned not only with wording, but also with access and re-use.","These official sources support a conservative conclusion: an accessibility statement is not finished merely because one page exists. It should be a public entry point that people can predictably find, understand, and use to take the next step.",{"title":54,"body":57},{"zh-Hant-TW":55,"en":56},"使用者需要的是下一步，不是漂亮承諾","People need a next step, not polished promises",{"zh-Hant-TW":58,"en":61},[59,60],"當使用者遇到無法操作、看不清楚、聽不到、送不出表單或無法完成任務的情況時，他通常不是在尋找一篇品牌宣言。他需要知道是否有替代方式、是否可以回報、需要提供哪些資訊，以及是否有人會處理。","這也是為什麼聲明的內容和入口必須一起看。一份文字很完整但很難找到的聲明，對使用者的幫助有限；一份入口明確但內容只寫「我們重視無障礙」的聲明，也無法提供足夠線索。",[62,63],"When someone cannot operate a control, read content, hear media, submit a form, or complete a task, they are usually not looking for a brand statement. They need to know whether there is an alternate path, whether they can report the barrier, what information would help, and whether someone will handle it.","That is why the content and entry point of a statement need to be evaluated together. A complete statement that is hard to find has limited value for users. A visible statement that only says “we care about accessibility” also fails to provide enough clues.",{"title":65,"body":68,"items":75},{"zh-Hant-TW":66,"en":67},"從可見性判斷一份聲明是否比較有用","How visibility helps judge whether a statement is useful",{"zh-Hant-TW":69,"en":72},[70,71],"可見性不是單純的 SEO 技巧。它是一組能幫助使用者和維護者判斷公開資訊是否可用的訊號。這些訊號不會證明網站完全無障礙，但能讓網站是否願意公開限制、回報方式與維護責任變得比較清楚。","對多語系網站來說，語言尤其重要。使用者在英文頁面遇到阻礙，卻只能找到另一種語言的聲明；或在地方政府、教育、金融、交通服務中，聲明只存在 PDF 版本，都會提高使用者找到下一步的成本。",[73,74],"Visibility is not merely an SEO technique. It is a set of signals that help users and maintainers judge whether public information is usable. These signals do not prove whole-site accessibility, but they make it clearer whether the site exposes known limits, feedback paths, and maintenance responsibility.","Language is especially important for multilingual sites. If a user encounters a barrier on an English page but can find a statement only in another language, or if a government, education, finance, or transport service exposes the statement only as a PDF, the cost of finding the next step increases.",{"zh-Hant-TW":76,"en":82},[77,78,79,80,81],"使用清楚連結文字，例如「無障礙聲明」或「Accessibility Statement」。","放在使用者自然會找說明與聯絡方式的位置，例如頁尾、說明中心或聯絡頁。","讓聲明盡量使用目前頁面的語言，或至少提供可理解的跨語言入口。","標示更新日期、適用範圍、已知限制與回報方式。","避免把唯一入口藏在圖片、PDF、腳本互動或難以搜尋的位置。",[83,84,85,86,87],"Use clear link text such as “Accessibility” or “Accessibility Statement.”","Place it where people naturally look for help or contact information, such as the footer, help center, or contact page.","Keep the statement in the current page language when possible, or provide a clear cross-language path.","Expose the update date, scope, known limitations, and feedback path.","Avoid making images, PDFs, scripted interactions, or hard-to-search locations the only entry point.",{"title":89,"body":92},{"zh-Hant-TW":90,"en":91},"找得到仍然不是完整保證","Findable still does not mean fully accessible",{"zh-Hant-TW":93,"en":97},[94,95,96],"容易找到的無障礙聲明是一個好訊號，但它不是完整保證。聲明可能只涵蓋部分服務、特定網域、特定版本或特定期間，也可能尚未反映最近更新。相反地，找不到聲明也不能直接推論網站沒有做任何無障礙工作。","這個界線很重要。如果把「找到聲明」說成「網站無障礙」，會誇大聲明的證明力；如果把「找不到聲明」說成「網站不重視無障礙」，也可能錯怪沒有用公開聲明形式呈現工作的團隊。","比較負責任的說法是：聲明是一種可追溯的公開訊號。它能幫助使用者知道網站怎麼說明自己，也能幫助維護者檢查外界是否找得到那些說明，但它不能取代檢測、使用者回報、輔助科技測試或持續維護。",[98,99,100],"A findable accessibility statement is a useful signal, but it is not a complete guarantee. It may cover only part of a service, a specific domain, a specific version, or a specific period. It may not reflect a recent update. Conversely, not finding a statement does not prove that no accessibility work exists.","This boundary matters. Treating a found statement as proof that a site is accessible overstates what the statement can prove. Treating a missing statement as proof that a site does not care may also misread teams whose work is not exposed through a public statement.","A more responsible framing is this: a statement is a traceable public signal. It helps users see how a website explains itself, and it helps maintainers check whether those explanations can be found. It does not replace audits, user reports, assistive technology testing, or ongoing maintenance.",{"title":102,"body":105},{"zh-Hant-TW":103,"en":104},"Accesserty 為什麼收集聲明網址","Why Accesserty collects statement URLs",{"zh-Hant-TW":106,"en":110},[107,108,109],"Accesserty Signal 收集公開無障礙聲明網址，是為了讓使用者在搜尋結果或目前頁面更容易看見可追溯線索。這不是替網站評分，也不是宣稱該網站完全符合標準。","在資料還不完整時，Accesserty 不應把收集結果包裝成全球排名或完整資料集。比較誠實的價值是：當使用者需要更多資訊時，可以更快找到聲明與回報入口；當網站維護者想理解外界看見什麼訊號時，也能更清楚地檢查自己的公開資訊是否可被找到。","這也讓 Accesserty 的產品方向和一般 checker 不同。DevCheck 協助 release 前與頁面內初步檢查；Pulse 協助上線後觀察回報與操作困難；Signal 則處理公開訊號的可見性。三者都不是最後判決，而是讓團隊比較清楚知道目前看見什麼、還缺什麼。",[111,112,113],"Accesserty Signal collects public accessibility statement URLs so people can notice traceable clues in search results or on the current page. It is not a rating system, and it does not claim that a site fully conforms to a standard.","While the collection is still incomplete, Accesserty should not package the result as a global ranking or complete dataset. The more honest value is narrower: people can find statements and feedback paths faster, and maintainers can check whether their own public accessibility information is visible enough to be found.","This also makes Accesserty different from a generic checker. DevCheck supports pre-release and in-page preliminary review. Pulse supports post-launch monitoring of reports and interaction barriers. Signal works on the visibility of public signals. None of these is the final verdict; each helps teams see what is known and what is still missing.",{"title":115,"body":118},{"zh-Hant-TW":116,"en":117},"這篇文章的保守結論","The conservative conclusion",{"zh-Hant-TW":119,"en":122},[120,121],"如果一個網站已經發布無障礙聲明，下一個問題不應只是「內容夠不夠漂亮」。更值得問的是：使用者能不能從主要頁面找到它？搜尋引擎和輔助工具能不能理解它是無障礙資訊？聲明是否說明範圍、限制、更新日期與回報方式？","這些問題不會讓聲明變成認證，也不會讓網站自動符合 WCAG。它們的作用比較務實：降低使用者遇到阻礙後的搜尋成本，讓維護者更容易收到線索，也讓公開無障礙資訊從形式上的存在，變成更可能被使用的訊號。",[123,124],"If a website has published an accessibility statement, the next question should not only be whether the wording looks polished. Better questions are: can users find it from major pages, can search engines and assistive tools recognize it as accessibility information, and does it explain scope, limitations, update date, and feedback path?","These questions do not turn a statement into a certification, and they do not make a website automatically conform to WCAG. Their value is more practical: reducing the search cost after a user encounters a barrier, helping maintainers receive clues, and moving public accessibility information from mere existence toward a signal that is more likely to be used.",[126,134,139,146,151,156,161,166,171,176],{"label":127,"path":130,"description":131},{"zh-Hant-TW":128,"en":129},"Accesserty 如何理解無障礙訊號","How Accesserty understands accessibility signals","\u002Fpublic-data",{"zh-Hant-TW":132,"en":133},"了解公開標章、聲明、ALLY、回報與機器掃描摘要的差異與限制。","Understand the differences and limits of public badges, statements, ALLY, reports, and machine scan summaries.",{"label":135,"path":138},{"zh-Hant-TW":136,"en":137},"無障礙聲明術語頁","Accessibility statement glossary page","\u002Fglossary\u002Faccessibility-statement",{"label":140,"path":142,"description":143},{"zh-Hant-TW":141,"en":141},"Accesserty Signal","\u002Fsignal",{"zh-Hant-TW":144,"en":145},"在搜尋結果中顯示公開無障礙訊號，並讓使用者回報遇到的阻礙。","Show public accessibility signals in search results and let users report barriers.",{"label":147,"path":150},{"zh-Hant-TW":148,"en":149},"無障礙聲明資料來源","Accessibility statement sources","\u002Fpublic-data\u002Fstatements",{"label":152,"path":155},{"zh-Hant-TW":153,"en":154},"如何閱讀無障礙聲明","How to read an accessibility statement","\u002Fguides\u002Fhow-to-read-accessibility-statements",{"label":157,"path":160},{"zh-Hant-TW":158,"en":159},"無障礙聲明範例：發布前應確認什麼","Accessibility statement example: what to include before publishing","\u002Fguides\u002Faccessibility-statement-example-before-you-publish",{"label":162,"path":165},{"zh-Hant-TW":163,"en":164},"為什麼「有沒有找到」不等於「有沒有做」","Why “not found” does not mean “not accessible”","\u002Fguides\u002Fwhy-not-found-does-not-mean-not-accessible",{"label":167,"path":170},{"zh-Hant-TW":168,"en":169},"W3C WAI：Developing an Accessibility Statement","W3C WAI: Developing an Accessibility Statement","https:\u002F\u002Fwww.w3.org\u002FWAI\u002Fplanning\u002Fstatements\u002F",{"label":172,"path":175},{"zh-Hant-TW":173,"en":174},"W3C WAI 無障礙聲明產生器","W3C WAI accessibility statement generator","https:\u002F\u002Fwww.w3.org\u002FWAI\u002Fplanning\u002Fstatements\u002Fgenerator\u002F",{"label":177,"path":180},{"zh-Hant-TW":178,"en":179},"EU 2018\u002F1523：Model accessibility statement","EU 2018\u002F1523: Model accessibility statement","https:\u002F\u002Feur-lex.europa.eu\u002Flegal-content\u002FEN\u002FTXT\u002F?uri=CELEX%3A32018D1523",1789828081432]