I also think (wish) that screenreaders would not ignore display:none... But there isn't much we could do about that. Well, we could attack software that produces company, with an army of requests,... (not a bad idea, actually) And yes, using negative margin, makes me to feeling kind of dirty...
However, ...there you mentioned "comments", so the next question would be; Do the screeanreaders also ignore <!-- comments --> or not? Because, if they do not ignore it, it could be usefull (sometimes) to put some information in it, that could give an extra info about the content to people who are using screenreaders... Anyway, that does not help us with "additional website navigation" in case that the main navigotion used on site is built with Flash... Mihael On 1/9/07, Barney Carroll <[EMAIL PROTECTED]> wrote:
Mihael Zadravec wrote: > So, the best thing to use if we want not to display something, but still > want it to visible to the screenreader, would be use of negative > margins? Those effect something? > > Mihael That seems to be the case. Generally when people want something to be invisible but present, they give it absolute or fixed positioning and take it miles off the screen. I find this very annoying - tools are made available to us to hide things from view, yet we have to make them visible and render them off-screen instead... It feels incredibly ugly and protracted. 'display', by my definition, should affect display; even less ambiguously, 'visibility' should affect visibility - exclusively. The fact that screen readers remove these things from rendering is not a good thing in my eyes (hahaha). A better term for their currently implemented behaviour would be 'render:none;' - although actually, if something is not wanted in the user-available content at all, we are no longer talking about style and should be talking about whether or not it is in the HTML markup. Depending on circumstance, PHP and javascript can remove content that may not be desirable. If we are to hide the HTML from visual, tactile and audio rendering, then surely it is only available through source navigation, in which case we already have the standard of comments. Surely completely depriving the user of markup isn't CSS' job in the first place? Regards, Barney ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
-- Računalniške storitve Toasted Web Mihael Zadravec s.p. ----------------------------------------------- tel: 00386 51 808136 email in msn: [EMAIL PROTECTED] Skype kontakt: mihael_zadravec ----------------------------------------------- Toasted Web http://www.toastedweb.com ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
