What is normative? That really is the issue. I am less concerned informative notes because they are non-binding. Having attempted to explain Level A and Level AA many times to managers and programmers, I have found the logic of Understanding WCAG 2.0, very difficult and not compelling. Phill is correct. There is a gap that needs filling. We need clear language. I think, normative. In my opinion it needs to be clear in its responsibility to stake holders, with the user with a disability being at the center. Web content in all formats is be profoundly robust. The migration to mobile formats has proven this. There is no need that essential functionality needs cannot be met, but we need to address concepts like the American terms, undue burden and fundamental alteration, carefully and land on normative language. Like all statements in natural language we need to allow for interpretation. Perhaps we need a formal elastic clause that permits variation. I think what we can all agree on is that, level differentiation needs clarification. Now that WCAG is beyond the crazy flurry of criticism that it faced in 2008, WCAG WG can revisit these definitions. Phill has identifies a gap, that has confused many implementers. Wayne
Received on Friday, 14 August 2015 16:37:06 UTC