Greetings,
I'm sending you this email hoping that you can help us clarify some things about the Nu Html Checker validation process.
We are currently trying to guarantee that a web site developed with SharePoint Server 2013 for a customer will pass the WAI-AA WCAG 2.0 validation, but as SharePoint is a platform that has a vast amount of out-of-the-box of functionality, it has some custom html tag attributes on valid html tags (like DIV), that are required to ensure the platform's correct behavior. Obviously, this custom attributes fail the validation.
The thing is, apparently, we can ensure that after page load is completed on the end user's internet browser, the web site will have a compliant html structure with the W3C required standards for the WAI-AA WCAG 2.0 mark, but it seems that the validator always runs before page load is concluded, or that it simply ignores javascript completely.
Having this in mind, we would like you to help us with answers for the following questions:
1. Considering the web page life cycle, when does in fact the validator run, and does it ignore javascript?
2. Do custom attributes really have to be marked as errors instead of warnings, when the html tag is in fact a valid one (like DIV)? What is the requirement implied in this validation?
We're looking forward to hearing back from you, and thank you in advance for your time and attention.
Kind regards,
Tiago Lucas
Consultant
|create|it|
Mobile: (+351) 96 252 17 27
Phone: (+351) 21 814 04 88
Web: www.create.pt<http://www.create.pt/>
[cid:image001.jpg@01D1187F.2AC064A0]
[cid:image003.png@01D0EB07.68E1C7B0]<https://www.facebook.com/create.pt> [cid:image004.png@01D0EB07.68E1C7B0] <http://www.linkedin.com/company/create-it> [cid:image005.png@01D0EB07.68E1C7B0] <https://twitter.com/createit_pt>
