Could be useful depending on the context. For example, if you wanted to show that a field was editable content (within the whole application), but not on the particular screen you are on right now (especially if the user knew that by clicking on "edit" or some other option they would be able to edit those particular fields.)
You could even fine tune this so that if some users were able to edit a limited subset of the fields, they would only be only shown the "disabled input" for those they would be able to edit. As with the bananas, knowing that a shop usually has them but not today could be useful to someone. Cheers, Rebecca -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Kirkwood, Motive Sent: Tuesday, 15 November 2005 5:20 p.m. To: wsg@webstandardsgroup.org Subject: Re: [WSG] Accessibility: Default placeholders Hi Geoff, (To pick up on Patrick's point.) Have you come across a scenario on a website where it seems appropriate to use an input element to indicate that an option exists but cannot be edited by the user? Perhaps it's preferable to show such content as text rather than as an input? (Seems like an instance of "yes, we have no bananas": yes this is an input, but no you can't.) Best regards, -- Andy Kirkwood | Creative Director Motive | web.design.integrity http://www.motive.co.nz ph: (04) 3 800 800 fx: (04) 970 9693 mob: 021 369 693 93 Rintoul St, Newtown PO Box 7150, Wellington South, New Zealand ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
