Update statements.md

_playbook/statements.md

@@ -1,7 +1,7 @@
 ---
 layout: playbook
-title: Update accessibility statements
-description: 
+title: Accessibility statements
+description: Information about accessibility statements, what they are, why a website should have one and what type of information should be included.
 excerpt: 
 sidenav: docs
 categories:
@@ -11,29 +11,40 @@ roles:
   - Operations
 ---
 
-Accessibility statements are concise declarations that highlight your commitment to inclusion, and ensure that there is a clear feedback loop for users who find barriers.
+A complete, well rounded accessibility strategy should include an accessibility statement. But what exactly is an accessibility statement? How do you write one and what type of information should be included?
 
-Accessibility statements should be clearly identified in the footer of every page of the website, and at a minimum they should include:
+## What is an accessibility statement?
 
-* why the department cares about people with disabilities;
-* a reference to the standards followed;
-* examples of accessible implementations;
-* contact information, should there be a problem or question.
+An accessibility statement is a public declaration that highlights the commitment of a company or organization to accessibility and inclusion. 
 
-As leaders in the field, the [European Union](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32018D1523) and the UK now require accessibility statements on all of their government sites. In an effort to grow the practice, the UK published a [useful guide](https://www.gov.uk/guidance/make-your-website-or-app-accessible-and-publish-an-accessibility-statement) on writing accessibility statements that meet their requirements, and there are more approaches available in this [repository](https://github.com/accessibility/Accessibility-Statement). All [USA Federal agencies must also include an accessibility statement](https://digital.gov/resources/required-web-content-and-links/#accessibility-statement), but the regulations are not as well defined. 
+Accessibility statements are intended to provide site visitors with information about the accessibility of the website. This information can help people use and navigate the site by setting expectations around site standards and providing details about potential known barriers or technical compatibility.
 
-As the final piece of the feedback loop, accessibility statements ultimately determine how well your organization is meeting its accessibility goals. They can help people who simply have their systems configured differently than the testing infrastructure or those who have more unique requirements, and they make it clear that there is always more to do. Ultimately, the goal is improving the site for all users and encouraging visitors to be a part of that process.
+The [CivicActions accessibility statement](https://civicactions.com/accessibility-statement/) can be found in the footer of our main website. 
 
-## Checklist
+## Why provide an accessibility statement?
 
-* Appears in the footer of every page of the website.
-* Highlights information that will help the user navigate the site more easily.
-* Includes a feedback loop and encouragement for users to report barriers.
-* Is there anything about PDFs or other digital content which is generally inaccessible?
+In some cases there is a legal requirement, which is a very compelling reason to have one. For example, all US Federal agencies must maintain an accessibility statement with certain information as defined by the [Office of Management and Budget (OMB) memorandum](https://www.whitehouse.gov/omb/management/ofcio/m-24-08-strengthening-digital-accessibility-and-the-management-of-section-508-of-the-rehabilitation-act/) from December 2023.
 
-## Key questions
+However, even if there isn’t a legally mandated requirement, providing an accessibility statement on your website shows site visitors that you value accessibility as a  social responsibility and that providing access to information is a priority for your organization.
 
-* What happens with messages (phone calls or emails) with errors that are submitted via the accessibility statement?
-* Is it being reviewed regularly to see that it is still relevant for the site and it's users?
-* Are extra efforts made to ensure that the accessibility page is accessible? 
-* Are there regulations about accessibility statements that apply to you? 
+## Writing an accessibility statement
+At a minimum, the following information should be included in your statement:
+* A commitment to accessibility
+* The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag/) standard that the website or product adheres to (e.g. WCAG 2.1 AA)
+* Any known limitations or existing issues that site visitors should be aware of to help to prevent frustration for the user
+* Contact information for what to do if/when a user encounters a barrier or issue
+
+The following additional information would also be good to include:
+* Technical specifications, such as which browser/devices work well and which may have known compatibility issues
+* Remediation plans for any known or existing accessibility issues
+* Any links or references to applicable laws and policies
+* Date the statement was last updated
+
+Based on your particular website/product, there may be additional minimum requirements or some of the additional information mentioned above may be mandatory. For example, US Federal agencies must include (among other things) the date the statement was last updated and also a specific feedback mechanism for reporting issues to the appropriate 508 program office. When drafting your own accessibility statement, it is important to research specific requirements for your region and sector that may impact the information that should be provided.
+
+Also, remember that an accessibility statement is for site users, so it is important to write for that audience. Use [plain language](https://accessibility.civicactions.com/guide/plain-language) when writing your statement to allow users to easily understand the information you are telling them.
+
+## Resources
+* [W3C- Developing an Accessibility Statement](https://www.w3.org/WAI/planning/statements/)
+* [Section508.gov - Developing an Accessibility Statement](https://www.section508.gov/manage/laws-and-policies/website-accessibility-statement/)
+* [Model accessibility statement from GOV.UK](https://www.gov.uk/guidance/model-accessibility-statement)