Issue with Markup Validator W3c

[gohar717]

Reproduction

I've found this issue when was checking the Markup Validator issues, I've tested the latest version of remix (2.16.0) and the new created project throw this issues.

Steps to reproduce:

1. Run npx create-remix@latest.
2. Run npm run dev in the newly created project (i.e., without modifying any files).
3. Load the project in the web browser.
4. Copy the whole code from dev tools in the network.
5. Paste the code here and run test.

System Info

System:
    OS: Windows 10
    CPU: Intel(R) Celeron(R) G4930 CPU 3.20GHz
    Memory: 10 GB / 16.00 GB
    Shell: GNU bash, version 4.4.23(1)-release (x86_64-pc-msys)
Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
Browsers:
    Brave Browser: 133.1.75.180
    Chrome: 133.0.6943.142
    Safari: 18.2
npmPackages:
    @remix-run/dev: ^2.16.0 => 2.16.0
    @remix-run/node: ^2.16.0 => 2.16.0
    @remix-run/react: ^2.16.0 => 2.16.0
    @remix-run/serve: ^2.16.0 => 2.16.0
    vite: ^6.0.0 => 6.2.0

Used Package Manager

npm

Expected Behavior

Creating a new project, running it, and testing the code in the W3c validator and there should be no errors.

Actual Behavior

Creating a new project, running it, and testing the code in a W3c and got the errors.

[sergiodxa]

Those elements are generated by React, not Remix.

[github-actions]

Thank you for opening this issue, and our apologies we haven't gotten around to it yet!

With the release of React Router v7 we are sun-setting continued development/maintenance on Remix v2. If you have not already upgraded to React Router v7, we recommend you do so. We've tried to make the upgrade process as smooth as possible with our Future Flags. We are now in the process of cleaning up outdated issues and pull requests to improve the overall hygiene of our repositories.

We plan to continue to address 2 types of issues in Remix v2:

• Bugs that pose security concerns
• Bugs that prevent upgrading to React Router v7

If you believe this issue meets one of those criteria, please respond or create a new issue.

For all other issues, ongoing maintenance will be happening in React Router v7, so:

• If this is a bug, please reopen this issue in that repo with a new minimal reproduction against v7
• If this is a feature request, please open a new Proposal Discussion in React Router, and if it gets enough community support it can be considered for implementation

If you have any questions you can always reach out on Discord. Thanks again for providing feedback and helping us make our framework even better!