13 comments

  • INTPenis8 minutes ago
    As someone who valued that "Validated by w3c" button on my website back in the day, if a website today has FULLY valid HTML, I gaurantee you the admin is a massive nerd.
  • alt22735 minutes ago
    This is exactly why HTML is so ubiquitous, because it is so tolerant of mistakes in formatting, syntax, and just about anything else.<p>Most browsers will even read and process most of the things listed on this page because even if the spec doesnt say so, it just makes sense to anyway.
    • dylan60428 minutes ago
      Is HTML that way because of it being HTML, or have browsers just decided to brute force their way into handling the slop so that people won&#x27;t blame the browser for not doing it correctly?
      • alt22723 minutes ago
        In my experience a lot of the &quot;best practice&quot; warnings are reductive.<p>A couple examples from this list are not requiring a type parameter on certain tags, or style tags being valid under html and body tags but not div tags. These types of things would take extra coding in a browser to check for certain singular tags not requiring things that all others do. Therefore it is simpler to leave these checks out and leave sloppy syntax checking as it does no harm at all to the rendered markup.<p>You may be right in some situations, but the nature of HTML having everything applied to all tags and then selectively reduced definitely helps make it a more resilient and accommodating language.
      • ndiddy6 minutes ago
        Well it&#x27;s obviously a better experience for someone who&#x27;s not the page author if the browser tries to render an invalid page rather than throwing up its hands and showing an error. That way you can at least try to read the page rather than not being able to and having to track down the author and try to get him to fix his site. The &quot;strict parsing&quot; fans tried to force correctness with XHTML, but it was a failure and didn&#x27;t see much use.<p>The main problem with &quot;handling the slop&quot; used to be that different browsers would render invalid HTML differently, so poorly written sites could look very different depending on the browser you used. Modern HTML standardizes how browsers handle invalid HTML so this isn&#x27;t a problem anymore. See <a href="https:&#x2F;&#x2F;html.spec.whatwg.org&#x2F;multipage&#x2F;parsing.html" rel="nofollow">https:&#x2F;&#x2F;html.spec.whatwg.org&#x2F;multipage&#x2F;parsing.html</a>
  • personalityson36 minutes ago
    HN is not one of them <a href="https:&#x2F;&#x2F;validator.w3.org&#x2F;nu&#x2F;?doc=https%3A%2F%2Fnews.ycombinator.com%2F" rel="nofollow">https:&#x2F;&#x2F;validator.w3.org&#x2F;nu&#x2F;?doc=https%3A%2F%2Fnews.ycombina...</a>
  • JSR_FDED31 minutes ago
    50% of my errors are “&lt;font&gt; is deprecated”. If browsers stop supporting that I’m guessing huge swathes of the web will be affected, so I’m guessing it will never happen.
  • blakesterz40 minutes ago
    <p><pre><code> &quot;Accessibility failures are near-universal.&quot; </code></pre> Why does it seem like Accessibility is always an after thought? It is usually so easy to do while a site is built. We just don&#x27;t think about it until someone complains?
    • zamadatix0 minutes ago
      prefers-color-scheme has shipped for something like 7 years now and not even all of the major sites I frequent which already have a dark theme toggle support it yet. Obviously accessibility is more important than a dark theme (though it can be part of an accessibility story), but if it takes a minute to ship it and it&#x27;s been so many years you get the idea of how little it&#x27;s about when something is easy.
    • kps1 minute ago
      Ironically the site does not support `:prefers-color-scheme`.
    • tdeck35 minutes ago
      Almost nobody is testing their website with a screen reader so they don&#x27;t think of it as part of the user experience. In fact, I think most developers are only vaguely aware of what web accessibility actually is for and how it affects users.
    • iLoveOncall7 minutes ago
      Because 0.5% of the world population is blind and it costs much more than an extra 0.5% to make a website accessible?<p>Everytime this question is asked I wonder if people are genuinely not understanding that. It&#x27;s just not financially worth it.<p>I&#x27;m not defending this position, but it&#x27;s just glaringly obvious.
  • cyanbane44 minutes ago
    I would def argue this is a feature of the net ( that people from all walks of browsers can see mostly the same thing ) and not a bug.
  • collabs40 minutes ago
    I would be interested to see if the metric moves meaningfully based on switching to a different set of parameters for example running from the US vs the EU and multiple attempts over multiple days to see if anything changes...
  • shevy-java7 minutes ago
    The question is how important it is to have fully valid HTML.<p>The HTML validator complains about a ton of useless crap IMO. At one point I simply gave up on that. Just blindly adhering to that validator makes little sense really.
  • rogix38 minutes ago
    At this point, with all the tools available, if your site does not have fully valid HTML, it is because you don&#x27;t care. LLMs are your friends, dev.
  • hodder43 minutes ago
    And not a single person cares. What does fully valid even mean anymore?
  • theo_dcrx1 hour ago
    [flagged]
  • mervz10 minutes ago
    Legit who cares? It&#x27;s not stopping people from visiting them