> ## 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).

# Checklist - Accessibility of your website

With this **checklist**, you can check whether you have considered all steps for accessibility adjustments on your website, your site is accessible, and all relevant information is up-to-date.

1.  **Have you added the Accessibility Statement?**
    * [Create and publish the Accessibility Statement for the Website](https://support.churchdesk.com/en/article/creating-and-publishing-the-accessibility-statement-for-the-website-100jch3/)
    * [How do I add a link to the footer of my website? (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/)

2.  **Is your content up-to-date, with all the steps you need to take?**
    * **Responsibilities**: ChurchDesk is responsible for and handles all technical requirements. However, churches are responsible for the accessibility of all content on the website. If you are unsure whether your website meets the standard, we recommend testing it for free (e.g., with [this tool](https://wave.webaim.org/)). It's not necessary to pay an external company for this test, as this would be unnecessary and expensive. The free test with Wave is sufficient.

    Further articles on the topic:
    * [How to make your Website accessible](https://support.churchdesk.com/en/article/how-to-make-your-website-accessible-1wuvx08/)
    * [Global Colors - How to change website colors](https://support.churchdesk.com/en/article/global-colors-how-to-change-website-colors-1lfibxw/)
    * [Inserting Alt-Texts for Images](https://support.churchdesk.com/en/article/add-alt-text-to-images-c3r6zw/)

3.  **Have you already activated these settings?**
    * [Technical settings for accessible websites,](https://support.churchdesk.com/en/article/technical-setting-for-accessible-websites-930lnb/) which you need to activate once for your website.

4.  **You must republish the website after making adjustments!**

5.  **Add this ChurchDesk limitation to your Accessibility Statement under "Inaccessible Content / Known Limitations":**
    Copy:
> "It is currently not possible to display alt-texts for images directly inserted into the text field of ChurchDesk blog posts or ChurchDesk event entries. The high technical effort is disproportionate to the possibilities of capturing the context of the images in the text field from the event title, the header image's alt-text, and the written content of the published text field."


6.  **Accessibility Service**: If part of the work is being handled by ChurchDesk and the service is not yet completed, you can add a note in your **Accessibility Statement under "Inaccessible Content / Known Limitations"** indicating that the task is in progress and the website will soon comply with accessibility requirements.
    * [Information, pricing, and scope of the ChurchDesk Accessibility Service here](https://churchdesk.com/en/service/web-accessibility-service/)