RE: Accessibility

Does that sound like a bad idea:

To optimize the user experience for both sets of users, we're thinking of
having a separate url (like accessible.company.com) which would basically be
the print-only version of the site, plus some form of navigation.  It seems
like the CMS we select should make this pretty easy to implement.  

One remaining issue would be the front page - the marketing people here like
flash and other media on the front page, but WAI seems to discourage it.  Does
the browser send anything to the server that could be used to identify clients
with various accessibility issues, so we could redirect them to
accessible.company.com if they went to www.company.com?  I know I can detect
browsers like lynx or other less-common clients, but I don't think the common
browsers send this type of info.  It seems like there should be a standard for
this type of information.