Heh, as I said, wrong place to say this. I meant if the app were being developed for a specific client with specific (known) requirements/user environment. Obviously there's the hypothetical "what if they hire someone who uses these technologies in the future who ends up needing to use the CMS", but that may not be a concern depending on the business and anticipated life cycle of the product.
I did most emphatically NOT suggest this as a blanket approach, and never would. It was practical advice that may or may not have been useful depending on circumstances best evaluated by Andreas, nothing more. On 1/29/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote: > Joshua Street wrote: > > The other thing (this list is definitely the wrong place for me to say > > this) is if this is for a content management system or the like, where > > the client's browsing capabilities are a well known quantity, > > What? How can you possibly assume that any user of a CMS will not have > accessibility requirements? Is there some restriction on the web that I > don't know about in which users of Lynx, JAWS or other assistive > technology can't publish on the web, and therefore have no use for a CMS? > > -- > Lachlan Hunt > http://lachy.id.au/ ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
