[wp-testers] 2.6.3 + Strict Doc Type + "aria-required='true' = failed validation

[Otto]

On Mon, Nov 17, 2008 at 9:47 PM, Otto <otto at ottodestruct.com> wrote:
> On Mon, Nov 17, 2008 at 7:00 PM, Idled Soul <idledsoul at gmail.com> wrote:
>>
>> Otto wrote:
>>>
>>> You need to change your doctype, I expect:
>>>
>>> http://www.w3.org/TR/2007/WD-aria-state-20071019/#module_element_xhtml
>>
>> Thanks Otto. Just curious though, will that mean all future themes besides Default and Classic need to follow the Transitional Doc Type, when following Default and Classic coding methods? I mean, I'm sure most will view Default and Classic theme code structuring in order to update their own themes to work properly for 2.7.
>>
>> Same as when they want to make sure their themes work for the built-in Thread Comments. When they see the "aria-required" element, they'll think... "Well, my theme better have this too!" Of course, if their themes are using Strict, then what? They'll all basically have to be switched from Strict to Transitional doc types...?
>>
>> Just wondering..
>
> I really don't understand what you mean, exactly. If you don't want to
> put the aria-* stuff into your theme, then don't. You can be any
> doctype you please. The whole aria spec is an optional thing, for
> accessibility purposes. It's not quite possible to make it validate
> yet, as the spec is still being developed. However, some browsers
> already understand it, which it why it's been implemented in the
> default theme.


Also, XHTML 1.1 doesn't have "Strict" and "Transitional", so that
doesn't make any sense. You cannot validate aria-* with XHTML 1.0
anything, period.