Mihael Zadravec wrote:
but we all know that for the best screen reader users expirience, it is still better that headeings contain text only...
But we are not designing sites solely to cater for screen reader users. Using an image in markup, with correct alt, is perfectly fine and still usable for all audiences, sighted or not.
Why would one want to use an image, rather than CSS trickery? Many reasons...one would be to avoid potential css on/images off issues (as previously discussed on the list), if one cares about that particular configuration; another would be a restrictive CMS; or, which is the situation I usually face, when there are multiple authors with varying skill levels editing pages and requiring them to set up specific image replacements for all their particular graphical needs is simply not a realistic option, and it's far easier for them to put an image in as long as they provide the right alternative text behind it.
P -- Patrick H. Lauke __________________________________________________________ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com __________________________________________________________ Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __________________________________________________________ ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
