# WProofreader or SCAYT icons are broken on the product interface

### Problem and Symptoms <a href="#wproofreaderorscayticonsarebrokenontheproductinterface-problemandsymptoms" id="wproofreaderorscayticonsarebrokenontheproductinterface-problemandsymptoms"></a>

WProofreader or SCAYT products work properly but the icons are not loaded correctly.

![](/files/lc9mff5moWChDY2gKrwI)

Pic.1) WProofreader with broken icons

### Root cause <a href="#wproofreaderorscayticonsarebrokenontheproductinterface-rootcause" id="wproofreaderorscayticonsarebrokenontheproductinterface-rootcause"></a>

There are several reasons for such type of a case:

1. Content Security Policy (CSP) restrictions;
2. CORS issue;
3. Some CSS style breaks/overwrites the product styles.

### Solution <a href="#wproofreaderorscayticonsarebrokenontheproductinterface-solution" id="wproofreaderorscayticonsarebrokenontheproductinterface-solution"></a>

1. **Content Security Policy (CSP)** that is added on your side can be the root cause of the issue as it doesn't take into account the work with our product and blocked loading the icons. Please add [**https://svc.webspellchecker.net**](https://svc.webspellchecker.net/) to your content-security-policy. Also, depending on your security settings, you might need to add **font-src** there.
2. **CORS issue**. Please check the errors in your console tab with the details of the CORS issue for troubleshooting.
3. If the problem with other **CSS styles**, please turn off the extra plugins that are in use on your side in the browser and check the details about the issue in the development tool.

\
\
\
\ <br>


---

# Agent Instructions: 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:

```
GET https://docs.wproofreader.com/v6.12.0/troubleshooting/client-side/wproofreader-or-scayt-icons-are-broken-on-the-product-interface.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.