-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.1.1 Validity vs. well-formedness #2186
Comments
|
I would be in favor of testing only with https://parsetree.validator.nu/ in the future. The tool seems to me best to check the syntax errors according to 4.1.1. According to this tool A and B are not an error. Otherwise, one can only hope for progress on #770.... |
@detlevhfischer — How is A Do not get me wrong, it is a long standing concern that 4.1.1 requires neither validity nor well-formedness. The idea, as I recall, was to catch well-formedness errors which could be expected to cause difficult for assistive technology. The additional tension is that code which is caught by 4.1.1 still might not be problematic, and puts a11y auditors in a no-win situation. I think your A is an example there. The example I see pretty commonly is duplicate IDs, but none of the IDs are actually attached to content, and there is no effect on AT. |
@bruce-usab With "correctly nested" I meant to express that opening and closing tags of the inner element are fully inside the outer element, as opposed to We've had more discussions of this thorny issue on the BITV-Test GitHub (all in German) and I was asked whether we can fast-track this issue and #770 We will also evaluate whether using https://parsetree.validator.nu/ may solve some of the questions around evaluating content against 4.1.1. |
This issue looks like it can be closed as it relates to 4.1.1. If it needs to be re-opened, please do that and convert it to a Discussion. |
A while ago we had a longish exchange on Github (in German) between testers regarding the difference between syntax and validation errors. There was disagreement how to evaluate cases where the validator (after applying the Validate bookmarklet by @stevefaulkner to parsing results) still shows an error when code is well-formed but not valid. Two examples:
<span><h6>bla bla</h6></span>
(correctly nested, but block-level element inside inline element)<span href="../page.html">bla bla</span>
. (html attribute used on inappropriate element)A narrow definition of 4.1.1 wouls just look at well-formedness and disregard HTML validation requirements. It would thus accept both examples above.
Any views? I am hoping that @stevefaulkner may put this to rest...
The text was updated successfully, but these errors were encountered: