On 20/1/09 23:13, Anthony Ziebell wrote:
because an implementation of ARIA without using
JavaScript to do so would essentially mean a drop of support of legacy
browsers
If all you are doing is adding some unrecognized ARIA attributes to
_existing_ HTML or XHTML content, then such attributes
H Ben
I think the more serious compatibility problem with ARIA is the immaturity
and rapid pace of change of the draft specifications and implementations.
The ARIA spec is expected to go to last call end of february, so the
spec will be pretty stable by this point. From my understanding the
On 20/1/09 06:24, Anthony Ziebell wrote:
Is it true XHTML 1.1 supports modularization and thus, ARIA, except for
the role attribute / values?
I'm not sure I understand the question.
Modularization, in XHTML's case, refers to the splitting of XHTML
itself into modules. This allows the
Thanks Benjamin. The only troubles we face with
= XHTML 1.1 and = HTML5 is related to progressive enhancement.
It's more of a business decision... do we enhance our sites and make
them a whole lot more accessible, meanwhile dropping support for older
browsers? Or do we sit and wait until older
2009/1/21 Anthony Ziebell anth...@fatpublisher.com.au:
Someone mentioned using JavaScript to implement ARIA parameters. This is a
good idea... but just how accessible would that be to a vision impaired
visitor with JavaScript turned off?
I think the idea behind it is that because you also have
On 20/1/09 22:47, Anthony Ziebell wrote:
It's more of a business decision... do we enhance our sites and make
them a whole lot more accessible, meanwhile dropping support for
older browsers?
Other than an accessibility technology inspecting the DOM for ARIA
attributes, what makes you think
Oh, also... there is a requirement for our pages to validate (hence I
can only see JavaScript as a valid option at this point?)
Benjamin Hawkes-Lewis wrote:
On 20/1/09 22:47, Anthony Ziebell wrote:
It's more of a business decision... do we enhance our sites and make
them a whole lot more
On Wed, 21 Jan 2009 10:15:38 +1100, Anthony Ziebell wrote:
Oh, also... there is a requirement for our pages to validate (hence I can
only see
JavaScript as a valid option at this point?)
*Is* there a requirement for our pages to validate? I would have
thought that making a page more
Hi All,
If you haven't seen this yet, it may be of practical use when and if needed:
Validating (X)HTML + ARIA: http://www.paciellogroup.com/blog/?p=107
Written by Steve Faulkner, Technical Director - TPG (The Paciello Group)
Europe, Director - Web Accessibility Tools Consortium from his blog.
Is it true XHTML 1.1 supports modularization and thus, ARIA, except for
the role attribute / values? XHTML 1.1 (latest draft) allows XHTML 1.1
to be served as text/html as defined in RFC2854 or application/xhtml+xml
as defined in RFC3236. This is exciting as it looks like we are so close
to
10 matches
Mail list logo
