RE: "stray end tag" errors at https://www.w3.org/WAI/demos/bad/before/home.html

I failed to mention at first that I'm using the Check serialized DOM of current page<javascript:(function()%7bfunction%20c(a,b)%7bvar%20c=document.createElement(%22textarea%22);c.name=a;c.value=b;d.appendChild(c)%7dvar%20e=function(a)%7bfor(var%20b=%22%22,a=a.firstChild;a;)%7bswitch(a.nodeType)%7bcase%20Node.ELEMENT_NODE:b+=a.outerHTML;break;case%20Node.TEXT_NODE:b+=a.nodeValue;break;case%20Node.CDATA_SECTION_NODE:b+=%22%3c![CDATA[%22+a.nodeValue+%22]]\%3e%22;break;case%20Node.COMMENT_NODE:b+=%22%3c\!--%22+a.nodeValue+%22--\%3e%22;break;case%20Node.DOCUMENT_TYPE_NODE:b+=%22%3c!DOCTYPE%20%22+a.name+%22%3e\n%22%7da=a.nextSibling%7dreturn%20b%7d(document),d=document.createElement(%22form%22);d.method=%22POST%22;d.action=%22https://validator.w3.org/nu/%22;d.enctype=%22multipart/form-data%22;d.target=%22_blank%22;d.acceptCharset=%22utf-8%22;c(%22showsource%22,%22yes%22);c(%22content%22,e);document.body.appendChild(d);d.submit()%7d)();> bookmarklet rather than typing the test page URL into the Nu HTML Checker<https://validator.w3.org/nu/> page. I had assumed they would generate identical results, but they don't; only the bookmarklet generates the "unclosed element" errors (and one fatal error). ☹
LL

From: O'Guin, Jules D. <JDO09280@ccv.vsc.edu>
Sent: Thursday, July 18, 2019 5:58 PM
To: Lisa Louise Davis (Aquent) <v-lidav@microsoft.com>; www-validator@w3.org
Cc: shadi@w3.org; wai@w3.org
Subject: RE: "stray end tag" errors at https://www.w3.org/WAI/demos/bad/before/home.html


I see no false positives for unclosed elements on this page: https://www.uwb.edu/brand/website/accessibility/examples/inaccessible-page<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.uwb.edu%2Fbrand%2Fwebsite%2Faccessibility%2Fexamples%2Finaccessible-page&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575813803&sdata=Nn8EOM7XgN9IeBeAHdPQd4ZvfD%2FLErq5mJP13Qbazsg%3D&reserved=0>
All the warnings and errors are valid which are mostly "attribute is unnecessary" warnings (which you can simply ignore) and a few " element is obsolete" errors (which you should correct by not using obsolete tags if this is your website).

As for  https://www.w3.org/WAI/demos/bad/before/home.html<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2Fdemos%2Fbad%2Fbefore%2Fhome.html&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575813803&sdata=DAFyt8wTEWx3vdYrwY%2FYW82lnVEmNKmxaAuYBqJu%2BpA%3D&reserved=0>, in HTML 4.01, the <noscript> tag can only be used inside the <body> element, so if we move the <noscript> segment to the body where it belongs it should resolve those "stray end tag noscript" and  "stray end tag head". The HTML <noscript> element defines a section of HTML to be inserted if a script type on the page is unsupported or if scripting is currently turned off in the browser – it should be in the body, not the head, since it is meant to display what is inside it.
https://www.w3.org/TR/REC-html40/interact/scripts.html#edef-NOSCRIPT<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FREC-html40%2Finteract%2Fscripts.html%23edef-NOSCRIPT&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575823799&sdata=G5YlGVce6X9%2F3EarHD1h5CJAb5p6lhC6RAQOPP4%2Bl9I%3D&reserved=0>:
The NOSCRIPT element allows authors to provide alternate content when a script is not executed. The content of a NOSCRIPT element should only be rendered by a script-aware user agent in the following cases:
    The user agent is configured not to evaluate scripts.
    The user agent doesn't support a scripting language invoked by a SCRIPT element earlier in the document.
User agents that do not support client-side scripts must render this element's contents.
See also: https://www.tutorialspoint.com/html/html_noscript_tag.htm<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.tutorialspoint.com%2Fhtml%2Fhtml_noscript_tag.htm&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575823799&sdata=BxY%2BYil%2FJZdmeluc21jjrIt%2BVgXl1HqKbS1I0i3Bw9A%3D&reserved=0> for an example of proper placement inside the body. Additionally, one cannot use <font> or <b> inside it.
The problem is likely that the page was created in 2012 and never updated, so it's severely outdated: it's an outdated example. The site's purpose, according to the site, is to improve a web site using "Web Content Accessibility Guidelines (WCAG) 2.0". Web Content Accessibility Guidelines (WCAG) 2.0 (https://www.w3.org/TR/WCAG20/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FWCAG20%2F&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575833790&sdata=Z%2BHJhWJCf3tlyJxir5zdbgEHd5ZFAUkxjeEMOM9mRiQ%3D&reserved=0>) is from 2008, and it's been replaced with https://www.w3.org/TR/WCAG21/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FWCAG21%2F&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575833790&sdata=9D6pP9%2By7lxyKzxghlmNuJ9iSHLsBO9FvSMpVaatsAg%3D&reserved=0>.
w3.org should be removing outdated examples, but alas, it's up to the user to read the publication date at the bottom and decide if it's still valid. It has a changlog: https://www.w3.org/WAI/demos/bad/changelog.html<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2Fdemos%2Fbad%2Fchangelog.html&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575843785&sdata=IvXMvctJ2AET8hm6dASZLyPFK7aMCD1seWHhCukuX0w%3D&reserved=0>, the creator: shadi@w3.org<mailto:shadi@w3.org>, and lists the correct person to contact in regard to this specific resource: wai@w3.org<mailto:wai@w3.org>.

I have copied the above parties on this response so they may address your concerns. You may have better luck reaching out to one of the editors at the modern version at https://www.w3.org/WAI/WCAG21/Understanding/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FWCAG21%2FUnderstanding%2F&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575843785&sdata=MaTkAf%2Fj077k47iIPCj4m9nPnfP1VgMZFMTGDTGutNQ%3D&reserved=0> and asking them to guide you to appropriate tutorials or examples.

The problem is not with the NU HTML validator: it's that you're validating a website from 2012 which was written using standards from 2008: it's outdated/obsolete coding.

Regards,

Jules D. O’Guin

From: Lisa Louise Davis (Aquent) <v-lidav@microsoft.com<mailto:v-lidav@microsoft.com>>
Sent: Thursday, July 18, 2019 6:14 PM - 18:14 PM
To: www-validator@w3.org<mailto:www-validator@w3.org>
Subject: False positives for "stray end tag" rule

This message is from an external sender. Please be careful when clicking on links and attachments.

Greetings!
This morning I filed a bug on false positives I'm seeing in the Nu HTML Checker: https://github.com/validator/validator/issues/841<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvalidator%2Fvalidator%2Fissues%2F841&data=02%7C01%7Cv-lidav%40microsoft.com%7C02a152d128594bfadb7008d70be4164f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636990946575843785&sdata=eI779rzvn%2Bo09rUymkA%2B7M5jfAy8dCjsdn1WyaiEI%2Fg%3D&reserved=0>
I'm not seeing a lot of activity on the github site. Could you tell me when I'm likely to get a response?
Thanks!

- Lisa Louise

Lisa Louise Davis, Accessibility Tools PM (Microsoft)

Received on Friday, 19 July 2019 15:43:17 UTC