> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.churchdesk.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Creating and publishing the accessibility statement for the website

As part of the legal requirements for an accessible website, it is necessary to publish a current **accessibility statement** that is easily available to all visitors.  
Below you’ll find guidance on how to write and publish your statement on your website.

||| Disclaimer: The following is merely a suggestion based on best practices from churches. ChurchDesk does not offer any legal advice. The owner of the website bears sole legal responsibility.
### Recommended content and structure of the accessibility statement
Since there is no single standard format, certain elements must still be included. We recommend structuring your statement as follows:

#### 1. **Statement of Commitment**
* Include an official declaration that your organisation is committed to complying with all applicable accessibility legislation and requirements.

#### 2. **Status of Accessibility & Conformance Standard Used**
* Specify the accessibility standard you aim to follow (e.g. WCAG 2.1 Level AA) and indicate the current compliance status using one of the following:

1. Fully compliant
2. Partially compliant
3. Not compliant

#### 3. **Non-Accessible Content / Known Limitations**
* Describe any content on your website that is currently not accessible and, if possible, explain why.

#### 4. **Explanation of Efforts for Accessibility / Planned Improvements**
* Outline what steps you are taking or planning to take to improve accessibility. Include a timeline where applicable.

#### 5. **Preparation Date and Last Update**
* Indicate when the statement was created, and when the website accessibility was last reviewed or updated. A typical requirement is to review the statement at least once per year.

#### 6. **Feedback Mechanism & Contact Information**
* Make sure visitors can easily reach you if they want to report accessibility issues or ask related questions. Provide a direct contact option (e.g. email address, phone number or contact form) and, if possible, mention a specific accessibility officer or team.

#### 7. **Enforcement Procedure**
* Depending on your church structure or denomination, provide information on how visitors can escalate complaints if they are not satisfied with your response. Mention the relevant authority or ombudsman responsible for dispute resolution.

#### 8. **Evaluation Method**
* Explain how your website’s accessibility was assessed

|| We recommend publishing your accessibility statement as a separate page on your website and linking to it clearly in the footer of all pages. 

### 
You’ll find more helpful articles here:
* [How to add a link to your website footer (e.g. for the accessibility statement)](https://support.churchdesk.com/en/article/how-do-i-insert-a-link-in-the-footer-of-my-website-eg-for-the-accessibility-statement-q76i92/)
* [How to make your website accessible](https://support.churchdesk.com/en/article/how-to-make-your-website-accessible-1wuvx08/)
* [Navigate dropdown menus using only a keyboard](https://support.churchdesk.com/en/article/navigating-dropdown-menu-with-keyboard-930lnb/)
* [Global colors – How to change your website's color scheme](https://support.churchdesk.com/en/article/global-colors-how-to-change-website-colors-1lfibxw/)
* [Insert alt text for images](https://support.churchdesk.com/en/article/add-alt-text-to-images-c3r6zw/)