Re: [WSG] XHTML5 polyglot markup and WAI-ARIA, is there a valid way?

[Rob Crowther]

On 01/08/12 00:29, Isabel Santos wrote:

I could generate both xml and html but that isn't very elegant,
and would not optimise the resources.


Unless you serve the XHTML files with a MIME type of application/xml or 
application/xhtml+xml, which will break things in IE<9, the browser will 
treat all the content as HTML anyway.  This is precisely because of 
XHTML's arbitrary strictness.


http://wiki.whatwg.org/wiki/HTML_vs._XHTML#Differences_Between_HTML_and_XHTML

Rob



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

Re: [WSG] XHTML5 polyglot markup and WAI-ARIA, is there a valid way?

[Mathew Robertson]

Hi Isabel,

It sounds like you might be confusing/mixing your requirements... from the
limited information you have provided, this sounds like perfect candidate
to generate two separate files ie: HTML already has accessibility built
in, and you get the XML file contain exactly what you require.

regards,
Mathew Robertson

On 1 August 2012 09:29, Isabel Santos  wrote:

> 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
> strictness
> of xhtml in regards to ARIA.
>
> regards,
>
> isabel
>
>
>
> On Mon, Jul 30, 2012 at 10:56 AM, Rob Crowther 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
>>
>> 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
> ***


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

Re: [WSG] XHTML5 polyglot markup and WAI-ARIA, is there a valid way?

[Isabel Santos]

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
strictness
of xhtml in regards to ARIA.

regards,

isabel



On Mon, Jul 30, 2012 at 10:56 AM, Rob Crowther 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
>
> 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
***