Re: Re: Re: W3C markup validation

Posted by Erik Bruchez on
URL: https://discuss.orbeon.com/W3C-markup-validation-tp4348637p4389541.html

Antek,

I have entered a new issue to track this:

https://github.com/orbeon/orbeon-forms/issues/35

We certainly think it would be nice to fix those errors, even though
they don't prevent screen readers such as JAWS to function properly.

-Erik

On Mon, Feb 13, 2012 at 11:49 PM, Antek Jaworski <[hidden email]> wrote:

> Thanks for your reactions. In our case we have to comply as much as possible
> to the HTML4 or XHTML1 validation, so the HTML5 validation doesnt apply to
> us, and also the doctype in Orbeon declares one of the two I mentioned.
>
> It is a pity that we are facing so many errors when we validate a form, and
> we are trying to leave the source code as much as it is. But, even for the
> new validation service we see a lot of the same errors (even bad syntax on
> ID attributes):
> http://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.orbeon.com%2Forbeon%2Ffr%2Forbeon%2Fdmv-14%2Fedit%2F6b01fa4cd1605b8f736fac09be6cf9b2
>
> I understand that it can be hard to solve some of the errors the validation
> service recognizes, but since Orbeon even provides an accessible entry for
> forms, I would expect more eagerness on solving HTML validation issues.
>
> Kind regards,
>
> Antek Jaworski
>
>
> 2012/2/9 Erik Bruchez <[hidden email]>
>>
>> Funnily enough, W3C just announced their new validation service today,
>> see:
>>
>> http://www.w3.org/News/2012#entry-9353
>> http://validator.w3.org/nu/
>>
>> It uses the same validation software I was pointing at in my previous
>> message.
>>
>> -Erik
>>
>> On Wed, Feb 1, 2012 at 10:17 PM, Erik Bruchez <[hidden email]> wrote:
>> > Antek,
>> >
>> > In our opinion the W3C validator is needlessly restrictive.
>> >
>> > With regards to ids, for example: HTML 5 is relaxing the characters
>> > you can put in the id attribute (pretty much allowing anything in
>> > there as there is no reason not to). Also, every HTML element can
>> > support id, as it should be (but the W3C validator reports errors for
>> > those). And of course there is more.
>> >
>> > You could change  the code in Orbeon Forms to replace the "$" with
>> > something else, but that would require recompiling the source code.
>> >
>> > Now on the other hand I think that what this HTML 5 validator is
>> > reporting is interesting:
>> >
>> >
>> > http://html5.validator.nu/?doc=http%3A%2F%2Fwww.orbeon.com%2Forbeon%2Ffr%2Forbeon%2Fdmv-14%2Fedit%2F6b01fa4cd1605b8f736fac09be6cf9b2
>> >
>> > It reports 51 errors and 12 warnings (if I counted right), most of
>> > them being "Element div not allowed as child of element span in". We
>> > are aware of this one and should definitely fix it, although browsers
>> > deal with this without any problem.
>> >
>> > We are likely to address that kind of HTML 5 issues as we go, but
>> > unfortunately unlikely to make lots of efforts to comply with the W3C
>> > validator.
>> >
>> > On the topic of accessibility, we are aware that some governments in
>> > particular have some pretty strict rules. Unfortunately sometimes they
>> > do not reflect how screen readers actually deal with web pages (for
>> > example, JAWS has no issues with ids containing "$").
>> >
>> > -Erik
>> >
>> > On Wed, Feb 1, 2012 at 3:35 AM, Antek Jaworski <[hidden email]>
>> > wrote:
>> >> Hi  all,
>> >>
>> >> We're trying to comply to guidelines for accessibility on our forms and
>> >> we're facing a couple of validation issues after using
>> >> http://validator.w3.org/.
>> >>
>> >> For example, this can be seen if you try to validate the DMV-14 demo
>> >> form
>> >> using this url:
>> >>
>> >> http://validator.w3.org/check?uri=http%3A%2F%2Fwww.orbeon.com%2Forbeon%2Ffr%2Forbeon%2Fdmv-14%2Fedit%2F6b01fa4cd1605b8f736fac09be6cf9b2&charset=%28detect+automatically%29&doctype=Inline&group=0
>> >>
>> >> One of the issues is the use of a dollar sign $ in the "ID" attribute.
>> >> Line 159, Column 450: character "$" is not allowed in the value of
>> >> attribute
>> >> "ID"
>> >>
>> >> Are there possibilities to bypass this?
>> >>
>> >> Another question: to what extend are you trying to resolve the
>> >> validation
>> >> errors that the W3C validator shows?
>> >>
>> >> Kind regards,
>> >>
>> >> Antek
>> >>
>> >>
>> >>
>> >> --
>> >> You receive this message as a subscriber of the [hidden email]
>> >> mailing
>> >> list.
>> >> To unsubscribe: mailto:[hidden email]
>> >> For general help: mailto:[hidden email]?subject=help
>> >> OW2 mailing lists service home page: http://www.ow2.org/wws
>> >>
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email] mailing
>> list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing
> list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws