> For the complete documentation index, see [llms.txt](https://themedocs.zenit.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themedocs.zenit.design/en/faq/accessibility/images.md).

# Images

## Images and Accessibility

To optimize accessibility in your store, you should consider the following points when using images:

1. **Add alt text:**\
   Images that convey important information should be provided with meaningful alt text. This text describes the content of the image and ensures that users with visual impairments also receive the information. You can store alt text in the metadata of Shopware's media management.\
   [Shopware documentation on the metadata area](https://docs.shopware.com/en/shopware-6-en/content/media#meta-data)
2. **Use titles for images:**\
   In addition to the alt text, you can give each image in the Shopware media area a title. The title provides additional information and is often displayed as a tooltip when the user hovers over the image. You can store title texts in the metadata of Shopware's media management.\
   [Shopware documentation on the metadata area](https://docs.shopware.com/en/shopware-6-en/content/media#meta-data)
3. **Mark decorative images:**\
   Make sure that the alt text is only used if it actually provides added value. Avoid adding alt text to purely decorative images – these should be marked as decorative.\
   \
   In our CMS elements, you can mark images as **decorative**. This will cause screen readers to ignore these images if they offer no added value and serve only as a visual design. Once an image is marked as decorative, it receives empty alt and title attributes, so it is skipped by screen readers.\
   \
   This setting does not remove the information stored in the metadata, so the image can still be used as a non-decorative image elsewhere.

\
With these simple yet effective measures, you ensure that your images are accessible to all users, regardless of their abilities.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://themedocs.zenit.design/en/faq/accessibility/images.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.