HTMHell Newsletter

Subscribe
Archives
November 24, 2021

Issue #19 - Debugging HTML: Linting

I’m a big fan of using different browsers for development. Recently I switched to Edge for several weeks and I discovered some really useful features.

Have a great week,
Manuel

View this issue in the browser.

Issue #19 - Debugging HTML: Linting

One of my favourite features in Edge DevTools is the built-in linter that highlights potential issues in your HTML by marking affected elements with a squiggly yellow line.

Edge dev tools screenshot: A demo site with broken html like empty buttons, img without alt, wrong aria roles, missing aria roles, and aria-hidden on focusable elements.

If you hover over the opening tag, a tooltip with a description of the issue appears. You can Shift + click or right-click it and select “View Issues” to view details about the issue or you can open the issues panel directly (CMD/Ctrl + Shit + P -> Show Issues) to get a list of all issues found on the page. The data is coming from axe, @mdn/browser-compat-data, and webhint.

You can also jump from the issues panel directly to the affected element in the elements or sources panel, and there are links to learning resources.

A list of accessibility issues in the issues panel. The message '<ul> and <ol> must only directly contain <li>, <script> or <template> elements' expanded.

To learn more about this feature, check out the links in the resources section of this page.

Resources

  • Overview of accessibility testing using DevTools
  • Accessibility-testing features in DevTools
  • Microsoft Edge Tools for VS Code

Read this issue in your browser or share it with others: htmhell.dev/tips/debugging-html-linting

Don't miss what's next. Subscribe to HTMHell Newsletter:
YouTube mastodon
This email brought to you by Buttondown, the easiest way to start and grow your newsletter.