Hi Rob,

thank you, and sorry for the delayed answer.

The need for xml comes from the site being
a web application for an academic work.
The idea is to generate xml both to the site and for exchange purposes.

I could generate both xml and html but that isn't very elegant,
and would not optimise the resources.
In fact, accessibility, validity, design and usability are my own concerns,
they aren't part of the work, won't be evaluated,
and are taking more time then they should.

Anyway, as long as it is possible to do,
the more difficult a work, the more one learns.

I gess I've lost a good part of the WAI-ARIA development history,
it's kind of hard to understand the excessive and aparently arbitrary
of xhtml in regards to ARIA.



On Mon, Jul 30, 2012 at 10:56 AM, Rob Crowther <robe...@boogdesign.com>wrote:

> What XML content do you need to include?  If you just stick to regular
> HTML5 then all the ARIA stuff is valid (with some sanity restrictions) and
> you won't have to work around the strict parsing:
> http://www.whatwg.org/specs/**web-apps/current-work/**
> multipage/elements.html#wai-**aria<http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria>
> XML elements will be parsed into the HTML5 document tree, albeit slightly
> differently to how an XML document would be parsed, but maybe close enough
> for your purposes depending on what XML you'll be including.
> Rob

List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org

Reply via email to