RE: Information on accessibility issues of XFORMS

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I haven't been on this list long but this doesn't sound like the
> sort of answer I would have expected to this question regardless of
> how 
> accurate it
> is.
[snip]
Has the 
> accessiblity
> of XFORMS really not been considered or any guidelines produced? By
> all means advise people seeking information of potential pitfalls
> and issues regarding accessibility but surely we want to be taking
> a more positive approach?

Well it on what kind of guidelines and accessibility issues Robert is
looking for. If he is interested in guidelines for current use for
sites that will be public (rather than closed intranet systems where
you may know that all users will have XFORMS capable browsers) then
I'd agree with David's guideline to not use them at all 100%.

Maybe Robert is looking for accessibility issues on a technology that
is still emerging which as such would be largely theoretical. That's
also a valid point of discussion for a list like this, but it doesn't
invalidate David's advice.

Question: How easy is it to detect if XFORMS are available and set
content appropriately?

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPBX3c4Fpv9f1Mr0YEQIItwCg6RDewOxT9fmyGMlGjsrTPuHUr48An0Oi
Tf29/ryWw7jhGLZlFMSz6agZ
=7JCQ
-----END PGP SIGNATURE-----

Received on Tuesday, 11 December 2001 07:02:23 UTC