> For the complete documentation index, see [llms.txt](https://docs.codpeller.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codpeller.com/en/html-validator/user-guide.md).

# User Guide

HTML Validator checks the HTML of an open webpage in Chrome's Side Panel. This guide explains what is checked, how to interpret the results, and how to use the HTML Viewer, local-file support, settings, and support tools.

## Validate the Current DOM

1. Open the webpage you want to check in Google Chrome.
2. Open **HTML Validator** from the Chrome toolbar.
3. On the **Validate** tab, keep **Current DOM** selected under **HTML to validate**.
4. Select a **Validation engine** and click **Validate HTML**.

**Current DOM** is a snapshot of the HTML currently represented in the browser, including changes JavaScript has already made. The reported results belong to the snapshot captured for that validation. It is not a copy of the original HTTP response, and HTML Validator does not edit your webpage.

![Validate tab showing Current DOM, W3C Nu and the Validate HTML button](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/fODLusbtgZ6Fu4V1hTDL/images%2F02_sidepanel_validate.png)

## Choose a validation engine

### W3C Nu — online

Select **W3C Nu** for standards-based validation. The extension sends the HTML being checked to the external W3C Nu service at `validator.w3.org`. An internet connection is required.

If the external service or network is temporarily unavailable, validation may fail or return an HTTP error such as **429** (rate limiting). This does not, by itself, mean that your HTML contains errors. Try again later if needed.

### HTML Tidy — local/offline

Select **HTML Tidy** for basic checks performed locally in the extension, without sending HTML to an external validator. It can work without an internet connection when the webpage HTML is accessible to the extension.

HTML Tidy has important limitations: it may report valid modern HTML as problematic, or miss some HTML conformance errors. For standards-based validation, use W3C Nu where sending the HTML to an external service is appropriate.

![Validate tab with HTML Tidy selected and its limitation notice](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/EGfTIqPrZBdlrcgAHXRC/images%2F03_html_tidy.png)

The two engines do not necessarily report the same findings. Select the one that fits your task and privacy requirements.

## Read validation results

After a check completes, the **Results** tab displays the outcome. Depending on the selected engine and the page, it may show **Errors**, **Warnings**, or a result with no errors.

Each reported issue provides a validator message and, when available, a **Line** and **Column** position. The numbers refer to the HTML snapshot used for that check.

![Results tab showing errors, warnings, counts and actions](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/J2lVcxZLwXAs3iFYAbDP/images%2F04_results_errors.png)

You can use the actions on an issue card:

* **Expand arrow** — show the surrounding HTML context, when available.
* **Locate** — open the corresponding position in the validated HTML snapshot.
* **Copy** — copy that specific issue's details to your clipboard.

![Expanded issue with surrounding HTML and the problem line highlighted](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/8RRcGrPEmC8gwWQIfLIx/images%2F05_results_expanded.png)

Warnings are separate from errors. In particular, HTML Tidy warnings should be interpreted with its limited modern-HTML coverage in mind.

## Locate a problem in the HTML Viewer

1. On **Results**, find the issue you want to investigate.
2. Click **Locate**.
3. The extension switches to the **HTML** tab and shows the corresponding position in the HTML snapshot from the completed check.

The HTML Viewer is **read-only**. **Locate does not select or highlight a live element on the webpage** and does not change your source files.

![HTML Viewer after Locate, with the related line highlighted](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/p22PboDU6BJrbmP5yMyN/images%2F06_html_viewer_locate.png)

The **HTML** tab also includes:

* **Search HTML…** — find matching text in the displayed snapshot.
* **Copy HTML** — copy the validated HTML snapshot to your clipboard.

Check copied HTML before sharing it, especially when the webpage contains private content.

## Copy an individual issue

Click **Copy** once on an issue card. HTML Validator copies structured plain text, including the validator, source, severity, message, and available line/column information. Copying only puts the information on your clipboard; it does **not** send a report to support.

The `Page:` field follows these rules:

| Page type                         | Information included in a copied issue                                 |
| --------------------------------- | ---------------------------------------------------------------------- |
| HTTP(S) webpage                   | Origin and pathname; **query parameters and URL fragment are omitted** |
| Local HTML file                   | Filename only, without the directory path                              |
| Restricted or unavailable address | Address omitted rather than guessed                                    |

For example, a check of `https://example.com/catalog?sort=price#top` would identify the page as `https://example.com/catalog` in copied issue details.

Even a pathname or filename can reveal information. Review what you paste into an email, issue tracker, or public discussion.

## Revalidate after making changes

HTML Validator reports problems; it does not fix code for you.

1. Correct the HTML in your own project or editor.
2. Reload the webpage if needed so Chrome displays the updated content.
3. Return to **Results** and click **Revalidate**.
4. Read the new result.

**Revalidate** captures and checks the page again. Previous results do not update themselves when you edit a file or webpage. If a new validation fails because of a network/service error, do not mistake an earlier result for a successful new check; the interface may indicate that previous results are stale.

![Results screen with the Revalidate button below reported issues](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/J2lVcxZLwXAs3iFYAbDP/images%2F04_results_errors.png)

## Validate local HTML files

You can open a local `.html` file in Chrome and validate its accessible Current DOM. Chrome must allow HTML Validator to access local file URLs.

If Chrome blocks access, you may see **Local file access is disabled.** The extension cannot read the file until you grant the permission. It does not replace missing HTML with another source.

To enable access:

1. Open the extension's **Settings** using the gear icon.
2. In **Local HTML files**, review the access status and use **Manage in Chrome** to open Chrome's extension settings.
3. In Chrome, enable **Allow access to file URLs**. The label can differ when Chrome is displayed in another language.
4. If Chrome reloads the extension and closes the Side Panel, open HTML Validator again and retry the validation.

![Local file access disabled — use the extension settings action](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/Nq7V2QTUMl9HG1myuFed/images%2F13_local_access_disabled.png)

![Allow access to file URLs in Chrome extension settings](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/aTLPikaW45U92VG7cQB1/images%2F14_chrome_file_permission.png)

*These two images are annotated, language-specific guidance. Use the corresponding permission label in your own Chrome interface.*

![Settings with the Local HTML files permission status and Manage in Chrome link](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/Yzisd6Vq9OxgLSgJzGoY/images%2F08_settings.png)

For an accessible local file, **HTML Tidy** checks locally. Choosing **W3C Nu** still sends the HTML to the external service and requires internet access.

## Customize Settings

Open **Settings** using the gear icon in the Side Panel header. Changes are saved automatically.

### Default validation engine

Under **General**, choose **W3C Nu — Recommended** or **HTML Tidy — Offline**. The default is used for new tabs unless you select a different engine.

### Appearance

Select **System**, **Light**, or **Dark**. **System** follows your operating system's appearance preference.

### Results

* **Show warnings** — controls whether warnings appear in the results list.
* **Highlight error lines in HTML viewer** — controls highlighting of the relevant lines in the HTML code.

![Settings showing the default engine, appearance and results options](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/Yzisd6Vq9OxgLSgJzGoY/images%2F08_settings.png)

The lower part of Settings includes a **Privacy** explanation of W3C Nu and HTML Tidy, and an **About HTML Validator** button.

![Settings privacy note, About HTML Validator and automatic saving message](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/r4qj2d2gscnDyFGx1PPN/images%2F09_settings_privacy.png)

## About, diagnostics, and support

### About HTML Validator

From Settings, click **About HTML Validator**. This screen identifies the installed version, explains the available validation engines, and provides feedback and documentation options.

![About HTML Validator screen with version and validation engines](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/z6KE2mJNmR2OxkfkmMOm/images%2F11_about.png)

In the lower part of About you can find **Support**, **Useful links**, **What's new in 2.0**, and **Copy diagnostic info**.

![About screen with Support, useful links and Copy diagnostic info](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/1WZmCRj5O4TRkrhqLUP3/images%2F12_about_support.png)

**Copy diagnostic info** copies technical context such as extension version, validation source and engine, theme, browser, and operating system. It **omits the actual webpage address and local file path**. Copying does not automatically send these details to anyone.

For support, the screen offers **Copy support email** and **Compose email**. An email is not sent merely by opening the screen or copying an address. Do not attach confidential HTML, private page contents, or secrets to a report unless you have deliberately reviewed what you share.

### Help & Feedback

Click the **?** icon in the Side Panel header to open **Help & Feedback**. The available actions are **Contact Support**, **Suggest a Feature**, and **Rate & Review**.

![Help & Feedback menu with the three available actions](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/5RnQx6WcNEs4l5fU6TOv/images%2F10_help_feedback.png)

## Things to remember

HTML Validator validates the **Current DOM snapshot**, not the original network response. **Locate** refers to the validated snapshot, not the live page. **Revalidate** runs a new check; it does not fix HTML. For standards-based validation use **W3C Nu**, taking into account that the checked HTML is sent to an external service. **HTML Tidy** is a local, more limited alternative.

For a first-time walkthrough, see [Getting Started](https://docs.codpeller.com/en/html-validator/getting-started.md). For common error states, see [Troubleshooting](https://docs.codpeller.com/en/html-validator/troubleshooting.md) and [FAQ](https://docs.codpeller.com/en/html-validator/faq.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.codpeller.com/en/html-validator/user-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
