- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Fri, 19 Jul 2019 13:58:08 +0200
- To: "O'Guin, Jules D." <JDO09280@ccv.vsc.edu>, "Lisa Louise Davis (Aquent)" <v-lidav@microsoft.com>, "www-validator@w3.org" <www-validator@w3.org>
- Cc: "wai@w3.org" <wai@w3.org>
Dear Jules, Many thanks for your feedback! We are working on a revised version of this demo but currently we do not have a confirmed release date. Here are ways to get announcements: - https://www.w3.org/WAI/news/subscribe/ Best, Shadi On 19/07/2019 02:57, O'Guin, Jules D. wrote: > I see no false positives for unclosed elements on this page: > https://www.uwb.edu/brand/website/accessibility/examples/inaccessible-page > 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, 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: > > 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 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/) is from 2008, and > it's been replaced with https://www.w3.org/TR/WCAG21/. > > 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, 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/ 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> > *Sent:* Thursday, July 18, 2019 6:14 PM - 18:14 PM > *To:* 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 > > 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) > -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Accessibility Strategy and Technology Specialist Web Accessibility Initiative (WAI) World Wide Web Consortium (W3C)
Received on Friday, 19 July 2019 11:58:17 UTC