Full Code of thedaviddias/Front-End-Checklist for AI

Repository: thedaviddias/Front-End-Checklist
Branch: main
Commit: 09d56dfe20c9
Files: 17
Total size: 56.5 KB

Directory structure:
gitextract_q4tcr243/

├── .editorconfig
├── .github/
│   ├── FUNDING.yml
│   ├── ISSUE_TEMPLATE.md
│   ├── PULL_REQUEST_TEMPLATE.md
│   └── workflows/
│       ├── links-checker.yml
│       ├── readme-check.yml
│       └── stale.yml
├── .gitignore
├── .husky/
│   └── pre-push
├── .markdownlint.json
├── .prettierrc
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── lychee.toml
└── package.json

================================================
FILE CONTENTS
================================================

================================================
FILE: .editorconfig
================================================
root = true

[*]
charset = utf-8
indent_style = space
indent_size = 2
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true


================================================
FILE: .github/FUNDING.yml
================================================
open_collective: front-end-checklist
github: thedaviddias
thanks_dev: thedaviddias


================================================
FILE: .github/ISSUE_TEMPLATE.md
================================================
<!-- Love front-end-checklist? Please consider supporting our collective:
👉  https://opencollective.com/front-end-checklist/donate -->

================================================
FILE: .github/PULL_REQUEST_TEMPLATE.md
================================================
<!-- Love Front-End Checklist? Please consider supporting our collective:
👉  https://opencollective.com/front-end-checklist/donate -->

**Fixes**: #

🚨 Please review the [guidelines for contributing](CONTRIBUTING.md) and our [code of conduct](../CODE_OF_CONDUCT.md) to this repository. 🚨
**Please complete these steps and check these boxes (by putting an x inside the brackets) before filing your PR:**

- [ ] Check the commit's or even all commits' message styles matches our requested structure.
- [ ] Check your code additions will fail neither code linting checks nor unit test.

#### Short description of what this resolves:


#### Proposed changes:

-
-
-

👍 Thank you!


================================================
FILE: .github/workflows/links-checker.yml
================================================
name: Links Checker

on:
  repository_dispatch:
  workflow_dispatch:
  schedule:
    - cron: '0 0 * * 1' # bi weekly on Monday

env:
  HUSKY: 0

jobs:
  links-checker:
    runs-on: ubuntu-latest
    name: Links Checker
    permissions:
      issues: write

    steps:
      - uses: actions/checkout@v4

      - name: Link Checker
        id: lychee
        uses: lycheeverse/lychee-action@v2.0.2
        with:
          args: --config ./lychee.toml --verbose --no-progress README.md
          fail: true

      - name: Create Issue From File
        if: env.exit_code != 0
        uses: peter-evans/create-issue-from-file@v5
        with:
          title: Link Checker Report
          content-filepath: ./lychee-out.md
          labels: report, automated issue


================================================
FILE: .github/workflows/readme-check.yml
================================================
name: Readme Check

on:
  pull_request:
    paths:
      - 'README.md'

env:
  HUSKY: 0

jobs:
  readme-check:
    runs-on: ubuntu-latest
    name: Readme Check

    steps:
      - uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '22'

      - name: Setup pnpm
        uses: pnpm/action-setup@v4
        with:
          version: 9

      - name: Install dependencies
        run: pnpm i

      - name: Check Markdown formatting
        run: pnpm format:check

      - name: Link Checker
        uses: lycheeverse/lychee-action@v2.0.2
        with:
          args: --config ./lychee.toml --verbose --no-progress README.md
          fail: true


================================================
FILE: .github/workflows/stale.yml
================================================
name: 'Close stale issues and PRs'

on:
  schedule:
    - cron: '30 1 * * 6'
  workflow_dispatch:

permissions:
  issues: write
  pull-requests: write

env:
  HUSKY: 0

jobs:
  stale:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/stale@v8
        with:
          stale-issue-message: 'This issue has been automatically marked as stale because it has been open 40 days with no activity. Remove stale label or comment or this will be closed in 10 days. Thank you for your contributions!'
          stale-pr-message: 'This PR has been automatically marked as stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.'
          close-issue-message: 'This issue was closed because it has been stalled for 10 days with no activity. You can always contact the maintainers directly for more information.'
          close-pr-message: 'This PR was closed because it has been stalled for 10 days with no activity. You can always contact the maintainers directly for more information.'
          days-before-stale: 40
          days-before-pr-stale: 45
          days-before-close: 10
          exempt-issue-assignees: 'thedaviddias'
          exempt-pr-assignees: 'thedaviddias'
          exempt-all-pr-assignees: true
          stale-issue-label: 'stale'
          stale-pr-label: 'stale'
          exempt-pr-labels: 'keep-unstale,security,dependabot,wip,need-help'
          exempt-issue-labels: 'keep-unstale,security'
          close-issue-label: 'wontfix'


================================================
FILE: .gitignore
================================================
.DS_Store
node_modules
.lycheecache
lychee-out.md


================================================
FILE: .husky/pre-push
================================================
pnpm format:fix


================================================
FILE: .markdownlint.json
================================================
{
  "MD013": false,
  "MD024": false,
  "MD033": false
}


================================================
FILE: .prettierrc
================================================
{
  "trailingComma": "none",
  "tabWidth": 2,
  "semi": true,
  "singleQuote": true,
  "printWidth": 150,
  "endOfLine": "lf",
  "overrides": [
    {
      "files": "*.md",
      "options": {
        "htmlWhitespaceSensitivity": "ignore",
        "proseWrap": "preserve",
        "embeddedLanguageFormatting": "off"
      }
    }
  ]
}


================================================
FILE: CODE_OF_CONDUCT.md
================================================
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at thedaviddias@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/


================================================
FILE: CONTRIBUTING.md
================================================
# Contribute

## Introduction

First, thank you for considering contributing to front-end-checklist! It's people like you that make the open source community such a great community! 😊

We welcome any type of contribution, not only code. You can help with
- **QA**: file bug reports, the more details you can give the better (e.g. screenshots with the console open)
- **Marketing**: writing blog posts, howto's, printing stickers, ...
- **Community**: presenting the project at meetups, organizing a dedicated meetup for the local community, ...
- **Code**: take a look at the [open issues](https://github.com/thedaviddias/Front-End-Checklist/issues). Even if you can't write code, commenting on them, showing that you care about a given issue matters. It helps us triage them.
- **Money**: we welcome financial contributions in full transparency on our [open collective](https://opencollective.com/front-end-checklist).

## Your First Contribution

Working on your first Pull Request? You can learn how from this *free* series, [How to Contribute to an Open Source Project on GitHub](https://app.egghead.io/playlists/how-to-contribute-to-an-open-source-project-on-github).

## Submitting code

Any code change should be submitted as a pull request. The description should explain what the code does and give steps to execute it. The pull request should also contain tests.

## Code review process

The bigger the pull request, the longer it will take to review and merge. Try to break down large pull requests in smaller chunks that are easier to review and merge.
It is also always helpful to have some context for your pull request. What was the purpose? Why does it matter to you?

## Financial contributions

We also welcome financial contributions in full transparency on our [open collective](https://opencollective.com/front-end-checklist).
Anyone can file an expense. If the expense makes sense for the development of the community, it will be "merged" in the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed.

## Questions

If you have any questions, create an [issue](https://github.com/thedaviddias/Front-End-Checklist/issues) (protip: do a quick search first to see if someone else didn't ask the same question before!).
You can also reach us at hello@front-end-checklist.opencollective.com.

## Credits

### Contributors

Thank you to all the people who have already contributed to front-end-checklist!
<a href="https://github.com/thedaviddias/Front-End-Checklist/graphs/contributors"><img src="https://opencollective.com/front-end-checklist/contributors.svg?width=890" /></a>


### Backers

Thank you to all our backers! [[Become a backer](https://opencollective.com/front-end-checklist#backer)]

<a href="https://opencollective.com/front-end-checklist#backers" target="_blank"><img src="https://opencollective.com/front-end-checklist/backers.svg?width=890"></a>


### Sponsors

Thank you to all our sponsors! (please ask your company to also support this open source project by [becoming a sponsor](https://opencollective.com/front-end-checklist#sponsor))

<a href="https://opencollective.com/front-end-checklist" target="_blank"><img src="https://opencollective.com/front-end-checklist/sponsor/1/avatar.svg" /></a>
<!-- This `CONTRIBUTING.md` is based on @nayafia's template https://github.com/nayafia/contributing-template -->


================================================
FILE: LICENSE
================================================
CC0 1.0 Universal

Statement of Purpose

The laws of most jurisdictions throughout the world automatically confer
exclusive Copyright and Related Rights (defined below) upon the creator and
subsequent owner(s) (each and all, an "owner") of an original work of
authorship and/or a database (each, a "Work").

Certain owners wish to permanently relinquish those rights to a Work for the
purpose of contributing to a commons of creative, cultural and scientific
works ("Commons") that the public can reliably and without fear of later
claims of infringement build upon, modify, incorporate in other works, reuse
and redistribute as freely as possible in any form whatsoever and for any
purposes, including without limitation commercial purposes. These owners may
contribute to the Commons to promote the ideal of a free culture and the
further production of creative, cultural and scientific works, or to gain
reputation or greater distribution for their Work in part through the use and
efforts of others.

For these and/or other purposes and motivations, and without any expectation
of additional consideration or compensation, the person associating CC0 with a
Work (the "Affirmer"), to the extent that he or she is an owner of Copyright
and Related Rights in the Work, voluntarily elects to apply CC0 to the Work
and publicly distribute the Work under its terms, with knowledge of his or her
Copyright and Related Rights in the Work and the meaning and intended legal
effect of CC0 on those rights.

1. Copyright and Related Rights. A Work made available under CC0 may be
protected by copyright and related or neighboring rights ("Copyright and
Related Rights"). Copyright and Related Rights include, but are not limited
to, the following:

  i. the right to reproduce, adapt, distribute, perform, display, communicate,
  and translate a Work;

  ii. moral rights retained by the original author(s) and/or performer(s);

  iii. publicity and privacy rights pertaining to a person's image or likeness
  depicted in a Work;

  iv. rights protecting against unfair competition in regards to a Work,
  subject to the limitations in paragraph 4(a), below;

  v. rights protecting the extraction, dissemination, use and reuse of data in
  a Work;

  vi. database rights (such as those arising under Directive 96/9/EC of the
  European Parliament and of the Council of 11 March 1996 on the legal
  protection of databases, and under any national implementation thereof,
  including any amended or successor version of such directive); and

  vii. other similar, equivalent or corresponding rights throughout the world
  based on applicable law or treaty, and any national implementations thereof.

2. Waiver. To the greatest extent permitted by, but not in contravention of,
applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and
unconditionally waives, abandons, and surrenders all of Affirmer's Copyright
and Related Rights and associated claims and causes of action, whether now
known or unknown (including existing as well as future claims and causes of
action), in the Work (i) in all territories worldwide, (ii) for the maximum
duration provided by applicable law or treaty (including future time
extensions), (iii) in any current or future medium and for any number of
copies, and (iv) for any purpose whatsoever, including without limitation
commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes
the Waiver for the benefit of each member of the public at large and to the
detriment of Affirmer's heirs and successors, fully intending that such Waiver
shall not be subject to revocation, rescission, cancellation, termination, or
any other legal or equitable action to disrupt the quiet enjoyment of the Work
by the public as contemplated by Affirmer's express Statement of Purpose.

3. Public License Fallback. Should any part of the Waiver for any reason be
judged legally invalid or ineffective under applicable law, then the Waiver
shall be preserved to the maximum extent permitted taking into account
Affirmer's express Statement of Purpose. In addition, to the extent the Waiver
is so judged Affirmer hereby grants to each affected person a royalty-free,
non transferable, non sublicensable, non exclusive, irrevocable and
unconditional license to exercise Affirmer's Copyright and Related Rights in
the Work (i) in all territories worldwide, (ii) for the maximum duration
provided by applicable law or treaty (including future time extensions), (iii)
in any current or future medium and for any number of copies, and (iv) for any
purpose whatsoever, including without limitation commercial, advertising or
promotional purposes (the "License"). The License shall be deemed effective as
of the date CC0 was applied by Affirmer to the Work. Should any part of the
License for any reason be judged legally invalid or ineffective under
applicable law, such partial invalidity or ineffectiveness shall not
invalidate the remainder of the License, and in such case Affirmer hereby
affirms that he or she will not (i) exercise any of his or her remaining
Copyright and Related Rights in the Work or (ii) assert any associated claims
and causes of action with respect to the Work, in either case contrary to
Affirmer's express Statement of Purpose.

4. Limitations and Disclaimers.

  a. No trademark or patent rights held by Affirmer are waived, abandoned,
  surrendered, licensed or otherwise affected by this document.

  b. Affirmer offers the Work as-is and makes no representations or warranties
  of any kind concerning the Work, express, implied, statutory or otherwise,
  including without limitation warranties of title, merchantability, fitness
  for a particular purpose, non infringement, or the absence of latent or
  other defects, accuracy, or the present or absence of errors, whether or not
  discoverable, all to the greatest extent permissible under applicable law.

  c. Affirmer disclaims responsibility for clearing rights of other persons
  that may apply to the Work or any use thereof, including without limitation
  any person's Copyright and Related Rights in the Work. Further, Affirmer
  disclaims responsibility for obtaining any necessary consents, permissions
  or other rights required for any use of the Work.

  d. Affirmer understands and acknowledges that Creative Commons is not a
  party to this document and has no duty or obligation with respect to this
  CC0 or use of the Work.

For more information, please see
<http://creativecommons.org/publicdomain/zero/1.0/>


================================================
FILE: README.md
================================================
# 🗂 Front-End Checklist

The Front-End Checklist is an exhaustive list of all elements you need to have / to test before launching your website /
HTML page to production.

**Other Checklists:**

- [🎮 Front-End Performance Checklist](https://github.com/thedaviddias/Front-End-Performance-Checklist#---------front-end-performance-checklist-)
- [💎 Front-End Design Checklist](https://github.com/thedaviddias/Front-End-Design-Checklist#front-end-design-checklist)

> [!TIP]
> ⭐️ Dev-friendly UX patterns you wish you knew. 👉 [UX Patterns for Devs](https://uxpatterns.dev/en) ⭐️

## 📚 Table of Contents

- [How to use](#how-to-use)
- [Head](#head)
- [HTML](#html)
- [Webfonts](#webfonts)
- [CSS](#css)
- [JavaScript](#javascript)
- [Accessibility](#accessibility)

## How to use?

<!-- prettier-ignore-start -->
> [!IMPORTANT]
> **Disclaimer:** This checklist is based on Front-End developers' years of experience, with additions from other open-source checklists.
<!-- prettier-ignore-end -->

All items in the **Front-End Checklist** are required for the majority of the projects, but some elements can be omitted
or are not essential (in the case of an administration web app, you may not need RSS feed for example). We choose to use
3 levels of flexibility:

- ![Low][low_img] indicates that the item is recommended but can be omitted in certain situations.
- ![Medium][medium_img] indicates that the item is highly recommended but can potentially be omitted in very specific
  cases. However, omitting these elements can negatively impact performance or SEO.
- ![High][high_img] indicates that the item cannot be omitted under any circumstances. Removing these elements may
  result in page malfunctions or cause accessibility and SEO issues. Testing should prioritize these elements first.

Some resources possess an emoticon to help you understand which type of content / help you may find on the checklist:

- 📖: documentation or article
- 🛠: online tool / testing tool
- 📹: media or video content

## Head

<!-- prettier-ignore-start -->
> [!NOTE]
> You can find [a list of everything](https://github.com/joshbuchea/HEAD) that could be found in the `<head>` of an HTML document.
<!-- prettier-ignore-end -->

### Meta tag

- [ ] **Doctype:** ![High][high_img] The Doctype is HTML5 and is at the top of all your HTML pages.

<!-- prettier-ignore-start -->
```html
<!doctype html><!-- HTML5 -->
```
<!-- prettier-ignore-end -->

- 📖
  [Determining the character encoding - HTML5 W3C](https://www.w3.org/TR/html5/syntax.html#determining-the-character-encoding)

_The next 2 meta tags (Charset and Viewport) need to come first in the head._

- [ ] **Charset:** ![High][high_img] The charset (UTF-8) is declared correctly.

<!-- prettier-ignore-start -->
```html
<!-- Set character encoding for the document -->
<meta charset="utf-8">
```
<!-- prettier-ignore-end -->

- [ ] **Viewport:** ![High][high_img] The viewport is declared correctly.

<!-- prettier-ignore-start -->
```html
<!-- Viewport for responsive web design -->
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
```
<!-- prettier-ignore-end -->

- [ ] **Title:** ![High][high_img] A title is used on all pages (SEO: Google calculates the pixel width of the characters used in the title, and it cuts off between 472 and 482 pixels. The average character limit would be around 55-characters).

```html
<!-- Document Title -->
<title>Page Title less than 55 characters</title>
```

- 📖 [Title - HTML - MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/title)
- 🛠 [SERP Snippet Generator](https://www.sistrix.com/serp-snippet-generator/)

- [ ] **Description:** ![High][high_img] A meta description is provided, it is unique and doesn't possess more than 150
      characters.

<!-- prettier-ignore-start -->
```html
<!-- Meta Description -->
<meta name="description" content="Description of the page less than 150 characters">
```
<!-- prettier-ignore-end -->

- 📖
  [Meta Description - HTML - MDN](https://developer.mozilla.org/en-US/docs/Learn/HTML/Introduction_to_HTML/The_head_metadata_in_HTML#Adding_an_author_and_description)

- [ ] **Favicons:** ![Medium][medium_img] Each favicon has been created and displays correctly. If you have only a
      `favicon.ico`, put it at the root of your site. Normally you won't need to use any markup. However, it's still
      good practice to link to it using the example below. Today, **PNG format is recommended** over `.ico` format
      (dimensions: 32x32px).

<!-- prettier-ignore-start -->
```html
<!-- Standard favicon -->
<link rel="icon" type="image/x-icon" href="https://example.com/favicon.ico">
<!-- Recommended favicon format -->
<link rel="icon" type="image/png" href="https://example.com/favicon.png">
<!-- Recommended modern favicon format (not recommended for legacy browsers) -->
<link rel="icon" type="image/svg+xml" href="https://example.com/favicon.svg">
```
<!-- prettier-ignore-end -->

- 🛠 [Favicon Generator](https://www.favicon-generator.org/)
- 🛠 [RealFaviconGenerator](https://realfavicongenerator.net/)
- 📖 [Favicon Cheat Sheet](https://github.com/audreyr/favicon-cheat-sheet)
- 📖 [Favicons, Touch Icons, Tile Icons, etc. Which Do You Need? - CSS Tricks](https://css-tricks.com/favicon-quiz/)
- 📖 [PNG favicons - caniuse](https://caniuse.com/link-icon-png)

- [ ] **Apple Web App Meta:** ![Low][low_img] Apple meta-tags are present.

<!-- prettier-ignore-start -->
```html
<!-- Apple Touch Icon (at least 200x200px) -->
<link rel="apple-touch-icon" href="/custom-icon.png">

<!-- To run the web application in full-screen -->
<meta name="apple-mobile-web-app-capable" content="yes">

<!-- Status Bar Style (see Supported Meta Tags below for available values) -->
<!-- Has no effect unless you have the previous meta tag -->
<meta name="apple-mobile-web-app-status-bar-style" content="black">
```
<!-- prettier-ignore-end -->

- 📖 [Configuring Web Applications](https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html)
- 📖 [Supported Meta Tags](https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariHTMLRef/Articles/MetaTags.html)

- [ ] **Windows Tiles:** ![Low][low_img] Windows tiles are present and linked.

<!-- prettier-ignore-start -->
```html
<!-- Microsoft Tiles -->
<meta name="msapplication-config" content="browserconfig.xml">
```
<!-- prettier-ignore-end -->

Minimum required xml markup for the `browserconfig.xml` file is as follows:

```xml
<?xml version="1.0" encoding="utf-8"?>
<browserconfig>
   <msapplication>
     <tile>
        <square70x70logo src="small.png"/>
        <square150x150logo src="medium.png"/>
        <wide310x150logo src="wide.png"/>
        <square310x310logo src="large.png"/>
     </tile>
   </msapplication>
</browserconfig>
```

<!-- prettier-ignore-start -->
- 📖 [Browser configuration schema reference](https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/dn320426(v=vs.85))
<!-- prettier-ignore-end -->

- [ ] **Canonical:** ![Medium][medium_img] Use `rel="canonical"` to avoid duplicate content.

<!-- prettier-ignore-start -->
```html
<!-- Helps prevent duplicate content issues -->
<link rel="canonical" href="http://example.com/2017/09/a-new-article-to-read.html">
```
<!-- prettier-ignore-end -->

- 📖
  [Use canonical URLs - Search Console Help - Google Support](https://support.google.com/webmasters/answer/139066?hl=en)
- 📖
  [5 common mistakes with rel=canonical - Google Webmaster Blog](https://webmasters.googleblog.com/2013/04/5-common-mistakes-with-relcanonical.html)

### HTML tags

- [ ] **Language attribute:** ![High][high_img] The `lang` attribute of your website is specified and related to the
      language of the current page.

```html
<html lang="en"></html>
```

- [ ] **Direction attribute:** ![Medium][medium_img] The direction of lecture is specified on the html tag (It can be
      used on another HTML tag).

```html
<html dir="rtl">
  <!-- ... -->
</html>
```

- 📖 [dir - HTML - MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/dir)

- [ ] **Alternate language:** ![Low][low_img] The language tag of your website is specified and related to the language
      of the current page.

<!-- prettier-ignore-start -->
```html
<link rel="alternate" href="https://es.example.com/" hreflang="es">
```
<!-- prettier-ignore-end -->

- [ ] **x-default:** ![Low][low_img] The language tag of your website for international landing pages.

```html
<link rel="alternate" href="https://example.com/" hreflang="x-default" />
```

- 📖 [x-default - Google](https://webmasters.googleblog.com/2013/04/x-default-hreflang-for-international-pages.html)

- [ ] **Conditional comments:** ![Low][low_img] Conditional comments are present for IE if needed.

- 📖
  [About conditional comments (Internet Explorer) - MSDN - Microsoft](<https://msdn.microsoft.com/en-us/library/ms537512(v=vs.85).aspx>)

- [ ] **RSS feed:** ![Low][low_img] If your project is a blog or has articles, an RSS link was provided.

- [ ] **CSS Critical:** ![Medium][medium_img] The CSS critical (or "above the fold") collects all the CSS used to render
      the visible portion of the page. It is embedded before your principal CSS call and between `<style></style>` in a
      single line (minified).

- 🛠 [Critical by Addy Osmani on GitHub](https://github.com/addyosmani/critical) automates this.

- [ ] **CSS order:** ![High][high_img] All CSS files are loaded before any JavaScript files in the `<head>`. (Except the
      case where sometimes JS files are loaded asynchronously on top of your page).

### Social meta

Visualize and generate automatically our social meta tags with [Meta Tags](https://metatags.io/)

**_Facebook OG_** and **_Twitter Cards_** are, for any website, highly recommended. The other social media tags can be
considered if you target a particular presence on those and want to ensure the display.

- [ ] **Facebook Open Graph:** ![Low][low_img] All Facebook Open Graph (OG) are tested and no one is missing or with
      false information. Images need to be at least 600 x 315 pixels, although 1200 x 630 pixels is recommended.

<!-- prettier-ignore-start -->
> [!NOTE]
> Using `og:image:width` and `og:image:height` will specify the image dimensions to the crawler so that it can render the image immediately without having to asynchronously download and process it.
<!-- prettier-ignore-end -->

<!-- prettier-ignore-start -->
```html
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/page.html">
<meta property="og:title" content="Content Title">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:description" content="Description Here" />
<meta property="og:site_name" content="Site Name">
<meta property="og:locale" content="en_US">
<!-- Next tags are optional but recommended -->
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
```
<!-- prettier-ignore-end -->

- 📖 [A Guide to Sharing for Webmasters](https://developers.facebook.com/docs/sharing/webmasters/)
- 📖 [Best Practices - Sharing](https://developers.facebook.com/docs/sharing/best-practices/)
- 🛠 Test your page with the [Facebook OG testing](https://developers.facebook.com/tools/debug/)

- [ ] **Twitter Card:** ![Low][low_img]

<!-- prettier-ignore-start -->
```html
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@site_account">
<meta name="twitter:creator" content="@individual_account">
<meta name="twitter:url" content="https://example.com/page.html">
<meta name="twitter:title" content="Content Title">
<meta name="twitter:description" content="Content description less than 200 characters">
<meta name="twitter:image" content="https://example.com/image.jpg">
```
<!-- prettier-ignore-end -->

- 📖
  [Getting started with cards — Twitter Developers](https://developer.twitter.com/en/docs/tweets/optimize-with-cards/guides/getting-started)
- 🛠 Test your page with the [Twitter card validator](https://cards-dev.twitter.com/validator)

**[⬆ back to top](#-table-of-contents)**

## HTML

### Best practices

- [ ] **HTML5 Semantic Elements:** ![High][high_img] HTML5 Semantic Elements are used appropriately (header, section,
      footer, main...).

- 📖 [HTML Reference](http://htmlreference.io/)

- [ ] **Error pages:** ![High][high_img] Error 404 page and 5xx exist. Remember that the 5xx error pages need to have
      their CSS integrated (no external call on the current server).

- [ ] **Noopener:** ![Medium][medium_img] In case you are using external links with `target="_blank"`, your link should
      have a `rel="noopener"` attribute to prevent tab nabbing. If you need to support older versions of Firefox, use
      `rel="noopener noreferrer"`.

- 📖 [About rel=noopener](https://mathiasbynens.github.io/rel-noopener/)

- [ ] **Clean up comments:** ![Low][low_img] Unnecessary code needs to be removed before sending the page to production.

### HTML testing

- [ ] **W3C compliant:** ![High][high_img] All pages need to be tested with the W3C validator to identify possible
      issues in the HTML code.

- 🛠 [W3C validator](https://validator.w3.org/)

- [ ] **HTML Lint:** ![High][high_img] I use tools to help me analyze any issues I could have on my HTML code.

- 🛠 [Dirty markup](https://www.10bestdesign.com/dirtymarkup/)

- 🛠 [webhint](https://webhint.io/)

- [ ] **Link checker:** ![High][high_img] There are no broken links in my page, verify that you don't have any 404
      error.

- 🛠 [W3C Link Checker](https://validator.w3.org/checklink)

- [ ] **Adblockers test:** ![Medium][medium_img] Your website shows your content correctly with adblockers enabled (You
      can provide a message encouraging people to disable their adblocker).

- 📖
  [Use AdBlocking in your Dev Environment](https://andreicioara.com/use-adblocking-in-your-dev-environment-48db500d9b86)

**[⬆ back to top](#-table-of-contents)**

---

## Webfonts

> [!NOTE]
> Using web fonts may cause Flash Of Unstyled Text/Flash Of Invisible Text - consider having fallback fonts
> and/or utilizing web font loaders to control behavior.

- 📖 [Google Technical considerations about webfonts](https://developers.google.com/fonts/docs/technical_considerations)

- [ ] **Webfont format:** ![High][high_img] WOFF, WOFF2 and TTF are supported by all modern browsers.

- 📖 [WOFF - Web Open Font Format - Caniuse](https://caniuse.com/woff).
- 📖 [WOFF 2.0 - Web Open Font Format - Caniuse](https://caniuse.com/woff2).
- 📖 [TTF/OTF - TrueType and OpenType font support](https://caniuse.com/ttf)
- 📖 [Using @font-face - CSS-Tricks](https://css-tricks.com/snippets/css/using-font-face/)

- [ ] **Webfont size:** ![High][high_img] Webfont sizes don't exceed 2 MB (all variants included).

- [ ] **Webfont loader:** ![Low][low_img] Control loading behavior with a webfont loader

- 🛠 [Typekit Web Font Loader](https://github.com/typekit/webfontloader)

**[⬆ back to top](#-table-of-contents)**

---

## CSS

> **Notes:** Take a look at [CSS guidelines](https://cssguidelin.es/) and [Sass Guidelines](https://sass-guidelin.es/)
> followed by most Front-End developers. If you have a doubt about CSS properties, you can visit
> [CSS Reference](http://cssreference.io/). There is also a short [Code Guide](http://codeguide.co/) for consistency.

- [ ] **Responsive Web Design:** ![High][high_img] The website is using responsive web design.
- [ ] **CSS Print:** ![Medium][medium_img] A print stylesheet is provided and is correct on each page.
- [ ] **Preprocessors:** ![Low][low_img] Your project is using a CSS preprocessor (e.g [Sass](http://sass-lang.com/),
      [Less](http://lesscss.org/), [Stylus](http://stylus-lang.com/)).
- [ ] **Unique ID:** ![High][high_img] If IDs are used, they are unique to a page.
- [ ] **Reset CSS:** ![High][high_img] A CSS reset (reset, normalize or reboot) is used and up to date. _(If you are
      using a CSS Framework like Bootstrap or Foundation, a Normalize is already included into it.)_

- 📖 [Reset.css](https://meyerweb.com/eric/tools/css/reset/)
- 📖 [Normalize.css](https://necolas.github.io/normalize.css/)
- 📖 [Reboot](https://getbootstrap.com/docs/4.0/content/reboot/)

- [ ] **JS prefix:** ![Low][low_img] All classes (or id- used in JavaScript files) begin with **js-** and are not styled
      into the CSS files.

```html
<div id="js-slider" class="my-slider">
  <!-- Or -->
  <div id="id-used-by-cms" class="js-slider my-slider"></div>
</div>
```

- [ ] **embedded or inline CSS:** ![High][high_img] Avoid at all cost embedding CSS in `<style>` tags or using inline
      CSS: only use for valid reasons (e.g. background-image for slider, critical CSS).
- [ ] **Vendor prefixes:** ![High][high_img] CSS vendor prefixes are used and are generated accordingly with your
      browser support compatibility.

- 🛠 [Autoprefixer CSS online](https://autoprefixer.github.io/)

### Performance

- [ ] **Concatenation:** ![High][high_img] CSS files are concatenated in a single file _(Not for HTTP/2)_.
- [ ] **Minification:** ![High][high_img] All CSS files are minified.
- [ ] **Non-blocking:** ![Medium][medium_img] CSS files need to be non-blocking to prevent the DOM from taking time to
      load.

- 📖 [loadCSS by filament group](https://github.com/filamentgroup/loadCSS)
- 📖 [Example of preload CSS using loadCSS](https://gist.github.com/thedaviddias/c24763b82b9991e53928e66a0bafc9bf)

- [ ] **Unused CSS:** ![Low][low_img] Remove unused CSS.

- 🛠 [UnCSS Online](https://uncss-online.com/)
- 🛠 [PurifyCSS](https://github.com/purifycss/purifycss)
- 🛠 [PurgeCSS](https://github.com/FullHuman/purgecss)
- 🛠 [Chrome DevTools Coverage](https://developer.chrome.com/docs/devtools/coverage/)

### CSS testing

- [ ] **Stylelint:** ![High][high_img] All CSS or SCSS files are without any errors.

- 🛠 [stylelint, a CSS linter](https://stylelint.io/)
- 📖 [Sass guidelines](https://sass-guidelin.es/)

- [ ] **Responsive web design:** ![High][high_img] All pages were tested at the following breakpoints: 320px, 768px,
      1024px (can be more / different according to your analytics). **Responsive Checker -**

  - 🛠 [Am I Responsive?](http://ami.responsivedesign.is/)
  - 🛠 [Mobile Friendly Test](https://search.google.com/test/mobile-friendly)
  - 🛠 [Responsive Website Design Tester](https://responsivedesignchecker.com/)

- [ ] **CSS Validator:** ![Medium][medium_img] The CSS was tested and pertinent errors were corrected.

- 🛠 [CSS Validator](https://jigsaw.w3.org/css-validator/)

- [ ] **Desktop Browsers:** ![High][high_img] All pages were tested on all current desktop browsers (Safari, Firefox,
      Chrome, Internet Explorer, EDGE...).
- [ ] **Mobile Browsers:** ![High][high_img] All pages were tested on all current mobile browsers (Native browser,
      Chrome, Safari...).
- [ ] **OS:** ![High][high_img] All pages were tested on all current OS (Windows, Android, iOS, Mac...).

- [ ] **Design fidelity:** ![Low][low_img] Depending on the project and the quality of the creatives, you may be asked
      to be close to the design. You can use some tools to compare creatives with your code implementation and ensure
      consistency.

> [Pixel Perfect - Chrome Extension](https://chrome.google.com/webstore/detail/perfectpixel-by-welldonec/dkaagdgjmgdmbnecmcefdhjekcoceebi?hl=en)

- [ ] **Reading direction:** ![High][high_img] All pages need to be tested for LTR and RTL languages if they need to be
      supported.

- 📖
  [Building RTL-Aware Web Apps & Websites: Part 1 - Mozilla Hacks](https://hacks.mozilla.org/2015/09/building-rtl-aware-web-apps-and-websites-part-1/)
- 📖
  [Building RTL-Aware Web Apps & Websites: Part 2 - Mozilla Hacks](https://hacks.mozilla.org/2015/10/building-rtl-aware-web-apps-websites-part-2/)

**[⬆ back to top](#-table-of-contents)**

---

## Images

> **Notes:** For a complete understanding of image optimization, check the free ebook
> **[Essential Image Optimization](https://images.guide/)** from Addy Osmani.

### Best practices

- [ ] **Optimization:** ![High][high_img] All images are optimized to be rendered in the browser. WebP format could be
      used for critical pages (like Homepage).

- 🛠 [Imagemin](https://github.com/imagemin/imagemin)
- 🛠 Use [ImageOptim](https://imageoptim.com/) to optimise your images for free.
- 🛠 Use [KeyCDN Image Processing](https://www.keycdn.com/support/image-processing) for image optimization in real time.
- 🛠 [TinyPNG](https://tinypng.com/) optimises png, apng (animated png) and jpg images with very small loss in quality.
  Free and paid version available.
- 🛠 [ZorroSVG](http://quasimondo.com/ZorroSVG/) jpg-like compression for transparent images using svg masking.
- 🛠 [SVGO](https://github.com/svg/svgo) a Nodejs-based tool for optimizing SVG vector graphics files.
- 🛠 [SVGOMG](https://jakearchibald.github.io/svgomg/) a web-based GUI version of SVGO for optimising your svgs online.

- [ ] **Picture/Srcset:** ![Medium][medium_img] You use picture/srcset to provide the most appropriate image for the
      current viewport of the user.

- 📖 [How to Build Responsive Images with srcset](https://www.sitepoint.com/how-to-build-responsive-images-with-srcset/)

- [ ] **Retina:** ![Low][low_img] You provide layout images 2x or 3x, support retina display.
- [ ] **Sprite:** ![Medium][medium_img] Small images are in a sprite file (in the case of icons, they can be in an SVG
      sprite image).
- [ ] **Width and Height:** ![High][high_img] Set `width` and `height` attributes on `<img>` if the final rendered image
      size is known (can be omitted for CSS sizing).
- [ ] **Alternative text:** ![High][high_img] All `<img>` have an alternative text which describes the image visually.

- 📖 [Alt-texts: The Ultimate Guide](https://axesslab.com/alt-texts/)

- [ ] **Lazy loading:** ![Medium][medium_img] Images are lazyloaded (A noscript fallback is always provided).
  - 🛠 [Native lazy loading polyfill](https://github.com/mfranzke/loading-attribute-polyfill/)

**[⬆ back to top](#-table-of-contents)**

---

## JavaScript

### Best practices

- [ ] **JavaScript Inline:** ![High][high_img] You don't have any JavaScript code inline (mixed with your HTML code).
- [ ] **Concatenation:** ![High][high_img] JavaScript files are concatenated.
- [ ] **Minification:** ![High][high_img] JavaScript files are minified (you can add the `.min` suffix).

- 📖 [Minify Resources (HTML, CSS, and JavaScript)](https://developers.google.com/speed/docs/insights/MinifyResources)

- [ ] **JavaScript security:** ![High][high_img]

- 📖
  [Guidelines for Developing Secure Applications Utilizing JavaScript](https://www.owasp.org/index.php/DOM_based_XSS_Prevention_Cheat_Sheet#Guidelines_for_Developing_Secure_Applications_Utilizing_JavaScript)

- [ ] **`noscript` tag:** ![Medium][medium_img] Use `<noscript>` tag in the HTML body if a script type on the page is
      unsupported or if scripting is currently turned off in the browser. This will be helpful in client-side rendering
      heavy apps such as React.js, see
      [examples](https://webdesign.tutsplus.com/tutorials/quick-tip-dont-forget-the-noscript-element--cms-25498).

```html
<noscript> You need to enable JavaScript to run this app. </noscript>
```

- [ ] **Non-blocking:** ![Medium][medium_img] JavaScript files are loaded asynchronously using `async` or deferred using
      `defer` attribute.

- 📖 [Remove Render-Blocking JavaScript](https://developers.google.com/speed/docs/insights/BlockingJS)

- [ ] **Optimized and updated JS libraries:** ![Medium][medium_img] All JavaScript libraries used in your project are
      necessary (prefer Vanilla Javascript for simple functionalities), updated to their latest version and don't
      overwhelm your JavaScript with unnecessary methods.

- 📖 [You may not need jQuery](http://youmightnotneedjquery.com/)
- 📖 [Vanilla JavaScript for building powerful web applications](https://plainjs.com/)

- [ ] **Modernizr:** ![Low][low_img] If you need to target some specific features you can use a custom Modernizr to add
      classes in your `<html>` tag.

- 🛠 [Customize your Modernizr](https://modernizr.com/download?setclasses)

### JavaScript testing

- [ ] **ESLint:** ![High][high_img] No errors are flagged by ESLint (based on your configuration or standards rules).

- 📖 [ESLint - The pluggable linting utility for JavaScript and JSX](https://eslint.org/)

**[⬆ back to top](#-table-of-contents)**

---

## Security

### Scan and check your web site

- [securityheaders.io](https://securityheaders.io/)
- [Observatory by Mozilla](https://observatory.mozilla.org/)

### Best practices

- [ ] **HTTPS:** ![High][high_img] HTTPS is used on every page and for all external content (plugins, images...).

- 🛠 [Let's Encrypt - Free SSL/TLS Certificates](https://letsencrypt.org/)
- 🛠 [Free SSL Server Test](https://www.ssllabs.com/ssltest/index.html)
- 📖 [Strict Transport Security](http://caniuse.com/#feat=stricttransportsecurity)

- [ ] **HTTP Strict Transport Security (HSTS):** ![Medium][medium_img] The HTTP header is set to
      'Strict-Transport-Security'.

- 🛠 [Check HSTS preload status and eligibility](https://hstspreload.org/)
- 📖
  [HTTP Strict Transport Security Cheat Sheet - OWASP](https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html)
- 📖
  [Transport Layer Protection Cheat Sheet - OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Protection_Cheat_Sheet.html)

- [ ] **Cross Site Request Forgery (CSRF):** ![High][high_img] You ensure that requests made to your server-side are
      legitimate and originate from your website / app to prevent CSRF attacks.

- 📖
  [Cross-Site Request Forgery (CSRF) Prevention Cheat Sheet - OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html)

- [ ] **Cross Site Scripting (XSS):** ![High][high_img] Your page or website is free from XSS possible issues.

- 📖
  [XSS (Cross Site Scripting) Prevention Cheat Sheet - OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html)
- 📖
  [DOM based XSS Prevention Cheat Sheet - OWASP](https://cheatsheetseries.owasp.org/cheatsheets/DOM_based_XSS_Prevention_Cheat_Sheet.html)

- [ ] **Content Type Options:** ![Medium][medium_img] Prevents Google Chrome and Internet Explorer from trying to
      mime-sniff the content-type of a response away from the one being declared by the server.

- 📖
  [X-Content-Type-Options - Scott Helme](https://scotthelme.co.uk/hardening-your-http-response-headers/#x-content-type-options)

- [ ] **X-Frame-Options (XFO):** ![Medium][medium_img] Protects your visitors against clickjacking attacks.

- 📖 [X-Frame-Options - Scott Helme](https://scotthelme.co.uk/hardening-your-http-response-headers/#x-frame-options)
- 📖 [RFC7034 - HTTP Header Field X-Frame-Options](https://tools.ietf.org/html/rfc7034)

- [ ] **Content Security Policy:** ![Medium][medium_img] Defines how content is loaded on your site and from where it is
      permitted to be loaded. Can also be used to protect against clickjacking attacks.

- 📖
  [Content Security Policy - An Introduction - Scott Helme](https://scotthelme.co.uk/content-security-policy-an-introduction/)
- 📖 [CSP Cheat Sheet - Scott Helme](https://scotthelme.co.uk/csp-cheat-sheet/)
- 📖 [CSP Cheat Sheet - OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)
- 📖 [Content Security Policy Reference](https://content-security-policy.com/)

**[⬆ back to top](#-table-of-contents)**

---

## Performance

### Best practices

- [ ] **Goals to achieve:** ![Medium][medium_img] Your pages should reach these goals:

  - First Meaningful Paint under 1 second
  - Time To Interactive under 5 seconds for the "average" configuration (a $200 Android on a slow 3G network with 400ms
    RTT and 400kbps transfer speed) and under 2 seconds for repeat visits
  - Critical file size under 170Kb gzipped

- 🛠 [Website Page Analysis](https://tools.pingdom.com)
- 🛠 [WebPageTest](https://www.webpagetest.org/)
- 📖 [Size Limit: Make the Web lighter](https://evilmartians.com/chronicles/size-limit-make-the-web-lighter)

- [ ] **Minified HTML:** ![Medium][medium_img] Your HTML is minified.

- [ ] **Lazy loading:** ![Medium][medium_img] Images, scripts and CSS need to be lazy loaded to improve the response
      time of the current page (See details in their respective sections).

- [ ] **Cookie size:** ![Medium][medium_img] If you are using cookies be sure each cookie doesn't exceed 4096 bytes and
      your domain name doesn't have more than 20 cookies.

- 📖 [Cookie specification: RFC 6265](https://tools.ietf.org/html/rfc6265)
- 📖 [Cookies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies)
- 🛠 [Browser Cookie Limits](http://browsercookielimits.squawky.net/)

- [ ] **Third party components:** ![Medium][medium_img] Third party iframes or components relying on external JS (like
      sharing buttons) are replaced by static components when possible, thus limiting calls to external APIs and keeping
      your user's activity private.

- 🛠 [Simple sharing buttons generator](https://simplesharingbuttons.com/)

### Preparing upcoming requests

- 📖 [Explanation of the following techniques](https://css-tricks.com/prefetching-preloading-prebrowsing/)

- [ ] **DNS resolution:** ![Low][low_img] DNS of third-party services that may be needed are resolved in advance during
      idle time using `dns-prefetch`.

```html
<link rel="dns-prefetch" href="https://example.com" />
```

- [ ] **Preconnection:** ![Low][low_img] DNS lookup, TCP handshake and TLS negotiation with services that will be needed
      soon is done in advance during idle time using `preconnect`.

```html
<link rel="preconnect" href="https://example.com" />
```

- [ ] **Prefetching:** ![Low][low_img] Resources that will be needed soon (e.g. lazy loaded images) are requested in
      advance during idle time using `prefetch`.

```html
<link rel="prefetch" href="image.png" />
```

- [ ] **Preloading:** ![Low][low_img] Resources needed in the current page (e.g. scripts placed at the end of `<body>`)
      in advance using `preload`.

```html
<link rel="preload" href="app.js" />
```

- 📖
  [Difference between prefetch and preload](https://medium.com/reloading/preload-prefetch-and-priorities-in-chrome-776165961bbf)

### Performance testing

- [ ] **Google PageSpeed:** ![High][high_img] All your pages were tested (not only the homepage) and have a score of at
      least 90/100.

- 🛠 [Google PageSpeed](https://developers.google.com/speed/pagespeed/insights/)
- 🛠 [Test your mobile speed with Google](https://testmysite.withgoogle.com)
- 🛠 [WebPagetest - Website Performance and Optimization Test](https://www.webpagetest.org/)
- 🛠 [GTmetrix - Website speed and performance optimization](https://gtmetrix.com/)
- 🛠 [Speedrank - Improve the performance of your website](https://speedrank.app/)

**[⬆ back to top](#-table-of-contents)**

## Accessibility

> **Notes:** You can watch the playlist
> [A11ycasts with Rob Dodson](https://www.youtube.com/playlist?list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g) 📹

### Best practices

- [ ] **Progressive enhancement:** ![Medium][medium_img] Major functionality like main navigation and search should work
      without JavaScript enabled.

- 📖 [Enable / Disable JavaScript in Chrome Developer Tools](https://www.youtube.com/watch?v=kBmvq2cE0D8)

- [ ] **Color contrast:** ![Medium][medium_img] Color contrast should at least pass WCAG AA (AAA for mobile).

- 🛠 [Contrast ratio](https://www.siegemedia.com/contrast-ratio)

#### Headings

- [ ] **H1:** ![High][high_img] All pages have an H1 which is not the title of the website.
- [ ] **Headings:** ![High][high_img] Headings should be used properly and in the right order (H1 to H6).

- 📹
  [Why headings and landmarks are so important -- A11ycasts #18](https://www.youtube.com/watch?v=vAAzdi1xuUY&index=9&list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g)

### Semantics

- [ ] **Specific HTML5 input types are used:** ![Medium][medium_img] This is especially important for mobile devices
      that show customized keypads and widgets for different types.

- 📖 [Mobile Input Types](http://mobileinputtypes.com/)

### Form

- [ ] **Label:** ![High][high_img] A label is associated with each input form element. In case a label can't be
      displayed, use `aria-label` instead.

- 📖
  [Using the aria-label attribute - MDN](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label)

### Accessibility testing

- [ ] **Accessibility standards testing:** ![High][high_img] Use the WAVE tool to test if your page respects the
      accessibility standards.

- 🛠 [Wave testing](http://wave.webaim.org/)

- [ ] **Keyboard navigation:** ![High][high_img] Test your website using only your keyboard in a previsible order. All
      interactive elements are reachable and usable.
- [ ] **Screen-reader:** ![Medium][medium_img] All pages were tested in a screen-reader (VoiceOver, ChromeVox, NVDA or
      Lynx).
- [ ] **Focus style:** ![High][high_img] If the focus is disabled, it is replaced by visible state in CSS.

- 📹
  [Managing Focus - A11ycasts #22](https://www.youtube.com/watch?v=srLRSQg6Jgg&index=5&list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g)

**[⬆ back to top](#-table-of-contents)**

## SEO

- [ ] **Google Analytics:** ![Low][low_img] Google Analytics is installed and correctly configured.

- 🛠 [Google Analytics](https://analytics.google.com/analytics/web/)
- 🛠 [GA Checker (and others)](http://www.gachecker.com/)

- [ ] **Search Console:** ![Low][low_img] Search Console is installed and correctly configured. It is a free service
      offered by Google that helps you monitor, maintain, and troubleshoot your site's presence in Google Search
      results.

- 🛠 [Search Console](https://search.google.com/search-console/about)

- [ ] **Headings logic:** ![Medium][medium_img] Heading text helps to understand the content in the current page.

- 🛠 [Tota11y, tab Headings](http://khan.github.io/tota11y/#Try-it)

- [ ] **sitemap.xml:** ![High][high_img] A sitemap.xml exists and was submitted to Google Search Console (previously
      Google Webmaster Tools).

- 🛠 [Sitemap generator](https://websiteseochecker.com/html-sitemap-generator/)

- [ ] **robots.txt:** ![High][high_img] The robots.txt is not blocking webpages.

- 🛠 Test your robots.txt with [Google Robots Testing Tool](https://www.google.com/webmasters/tools/robots-testing-tool)

- [ ] **Structured Data:** ![High][high_img] Pages using structured data are tested and are without errors. Structured
      data helps crawlers understand the content in the current page.

- 📖
  [Introduction to Structured Data - Search - Google Developers](https://developers.google.com/search/docs/guides/intro-structured-data)
- 📖 [JSON-LD](https://json-ld.org/)
- 📖 [Microdata](https://www.w3.org/TR/microdata/)
- 🛠 Test your page with the [Rich Results Test](https://search.google.com/test/rich-results)
- 🛠 Complete list of vocabularies that can be used as structured data.
  [Schema.org Full Hierarchy](http://schema.org/docs/full.html)

- [ ] **Sitemap HTML:** ![Medium][medium_img] An HTML sitemap is provided and is accessible via a link in the footer of
      your website.

- 📖 [Sitemap guidelines - Google Support](https://support.google.com/webmasters/answer/183668?hl=en)

**[⬆ back to top](#-table-of-contents)**

## Translations

The Front-End Checklist is also available in other languages. Thanks for all translators and their awesome work!

- 🇯🇵 Japanese: [miya0001/Front-End-Checklist](https://github.com/miya0001/Front-End-Checklist)
- 🇪🇸 Spanish: [eoasakura/Front-End-Checklist-ES](https://github.com/eoasakura/Front-End-Checklist-ES)
- 🇨🇳 Chinese: [JohnsenZhou/Front-End-Checklist](https://github.com/JohnsenZhou/Front-End-Checklist)
- 🇰🇷 Korean: [kesuskim/Front-End-Checklist](https://github.com/kesuskim/Front-End-Checklist)
- 🇧🇷 Portuguese: [jcezarms/Front-End-Checklist](https://github.com/jcezarms/Front-End-Checklist)
- 🇻🇳 Vietnamese: [euclid1990/Front-End-Checklist](https://github.com/euclid1990/Front-End-Checklist)
- 🇹🇼 Traditional Chinese: [EngineLin/Front-End-Checklist](https://github.com/EngineLin/Front-End-Checklist)
- 🇫🇷 French: [ynizon/Front-End-Checklist](https://github.com/ynizon/Front-End-Checklist)
- 🇷🇺 Russian: [ungear/Front-End-Checklist](https://github.com/ungear/Front-End-Checklist)
- 🇹🇷 Turkish: [eraycetinay/Front-End-Checklist](https://github.com/eraycetinay/Front-End-Checklist)
- 🇩🇪 German: [xfuture603/Front-End-Checklist](https://github.com/xFuture603/Front-End-Checklist)
- 🇵🇱 Polish: [mbiesiad/Front-End-Checklist](https://github.com/mbiesiad/Front-End-Checklist)
- 🇮🇩 Indonesian: [nniinnoo/Front-End-Checklist](https://github.com/nniinnoo/Front-End-Checklist)

## Support

If you have any question or suggestion, don't hesitate to reach me on X:

- [X (formerly Twitter)](https://ddias.link/x)
- [Chat on Discord](https://ddias.link/discord)

## Contributors

This project exists thanks to all the people who contribute. ([Contribute](https://github.com/thedaviddias/Front-End-Checklist/blob/main/CONTRIBUTING.md)).
<a href="https://github.com/thedaviddias/Front-End-Checklist/graphs/contributors"><img src="https://opencollective.com/front-end-checklist/contributors.svg?width=890" alt="Contributors" /></a>

## Backers

Thank you to all our backers! 🙏 [[Become a backer](https://opencollective.com/front-end-checklist#backer)]

<a href="https://opencollective.com/front-end-checklist#backers" target="_blank"><img src="https://opencollective.com/front-end-checklist/backers.svg?width=890" alt="Backers" /></a>

## Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website.
[[Become a sponsor](https://opencollective.com/front-end-checklist#sponsor)]

<a href="https://opencollective.com/front-end-checklist" target="_blank"><img src="https://opencollective.com/front-end-checklist/sponsor/1/avatar.svg" alt="Sponsors" /></a>

## License

[![CC0](https://i.creativecommons.org/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)

**[⬆ back to top](#-table-of-contents)**

[low_img]: https://raw.githubusercontent.com/thedaviddias/Front-End-Checklist/refs/heads/main/data/images/priority/low.svg
[medium_img]: https://raw.githubusercontent.com/thedaviddias/Front-End-Checklist/refs/heads/main/data/images/priority/medium.svg
[high_img]: https://raw.githubusercontent.com/thedaviddias/Front-End-Checklist/refs/heads/main/data/images/priority/high.svg


================================================
FILE: lychee.toml
================================================
#############################  Display  #############################
verbose = "info"
output = "./lychee-out.md"

#############################  Cache  ###############################
cache = true
max_cache_age = "2d"

#############################  Runtime  #############################
max_concurrency = 14

#############################  Requests  ############################
user_agent = "curl/7.83.1"
timeout = 20
accept = ["200", "429", "403"]
scheme = ["https"]

#############################  Exclusions  ##########################
base = "https://github.com/thedaviddias/Front-End-Checklist/"
exclude = ["https://caniuse.com"]


================================================
FILE: package.json
================================================
{
  "name": "front-end-checklist",
  "version": "1.0.0",
  "description": "The perfect Front-End Checklist for modern websites and meticulous developers",
  "scripts": {
    "format:check": "prettier --check README.md",
    "format:fix": "prettier --write README.md && markdownlint README.md",
    "prepare": "husky || true"
  },
  "keywords": [
    "front-end",
    "checklist",
    "html",
    "css",
    "javascript",
    "accessibility",
    "lists",
    "developer",
    "developer-tools"
  ],
  "author": "David Dias (https://thedaviddias.com/)",
  "license": "CC-BY-4.0",
  "devDependencies": {
    "husky": "^9.1.6",
    "markdownlint-cli": "^0.42.0",
    "prettier": "^3.3.3"
  }
}