• Resolved NathanCampbell

    (@nathancampbell)


    Hi,

    I know there’s a plugin out there that tells IE6 users to update. But most of them don’t.

    I’m sick of IE6 users. They’re idiots. I think they should be treated as such.

    Is it possible to use CSS to mangle text for IE6 users?

    I’m thinking to get it to detect the browser and then replace words with common misspellings. So replacing its with it’s, their with there, you’re with your…

    It’s slightly more subtle than the existing plug ins.

    I guess you could also use it to autocorrect mistakes or to automatically censor swearing so it’s not completely devoid of purpose…

    Can CSS change words in the body of a page?

Viewing 11 replies - 1 through 11 (of 11 total)
  • a lot of 3rd world and other folks are stuck using IE6 – so pile on them

    I don’t know of a plugin that would change the words in the body-text – I can only tell you, that CSS can’t do it.

    Actually it could, but the CSS would be ignored by IE6 because it does not support the selectors required to do it…

    I’m talking about using..
    :before
    and
    :after

    Which IE6 will of course ignore, because it doesn’t know what they are..

    Paste this chunk of code in a .txt, change the strings to fit your needs, name the file “foo2bar.php” place it in your plugins directory and have fun!

    <?php
    /*
    Plugin Name: foo 2 bar
    Plugin URI:
    Description: Search a string in the content and replaces it by another
    Author: MAC (adapted a long time ago from someone I don't recall)
    Version: 1
    Author URL: [email protected]
    */
    function foo2bar($text){
     	$text = str_replace('findThisWord', 'ReplaceItWithThis', $text);
     	return $text;
    }
    add_filter('the_content', 'foo2bar');
    add_filter('the_title', 'foo2bar');
    ?>

    MAC ??

    All the above does is replace matched text in a string, there’s lots of ways you could do it, i’m confused how that’s going to help in regard to IE6 specifically.

    @t31os_ > perhaps you didn’t pay atention to the above posts:

    “(…) I don’t know of a plugin that would change the words in the body-text (…)”

    MAC ??

    I’m sick of IE6 users. They’re idiots. I think they should be treated as such.

    What is your problem? There are many reason why some people still use IE6. Most of them are valid reasons and have nothing to do with IQ levels.

    Is it possible to use CSS to mangle text for IE6 users?

    If IE6 bothers you so much, just ignore and/or don’t support it. Deliberately trashing pages in a given browser is a different thing altogether and smacks of toddler tantrums to me. Personally, I have far better ways to spend my time. Plus, I’d rather not fall foul of any anti-discrimination laws…

    @esmi (and general comment) – I don’t think you’d be legally liable for anything when dealing with a web browser, it’s a piece of software, not a person…

    That would kind of be like saying Games are discriminating against Linux because they only work under Windows and Mac (for the most part)..

    That said, i d agree, it’s a little odd to want to make their browsing experience poorer by purposely changing text and such… but all the same it is kinda funny to… i’ve felt like doing it at times..

    @mac – Point taken (sorry), i retract my previous reply… (i can’t edit it now)…

    @nathan – You can use IE specific code to target IE6 and below… it’s generally used for including additional stylesheets, but i don’t see any reason you couldn’t place an element in there, so only IE users see it…

    See here.
    https://www.quirksmode.org/css/condcom.html

    @esmi (and general comment) – I don’t think you’d be legally liable for anything when dealing with a web browser, it’s a piece of software, not a person…

    DDA covers web sites as well as physical structures. So, if you deliberately make site content inaccessible to certain user agents and it turns out that some disabled people rely on said user agents, you (the site owner) could be liable under DDA. Going out of your way to garble content isn’t exactly making “reasonable adjustments”.

    Seriously i’d love to see someone try to pull that one..

    If it’s your webspace, you’re free to do with as you choose as long as you’re within the terms of service with your webhost, for example no adult content, or racism, etc…

    I can’t see how anyone could seriously mount a case against a developer for giving people with a particular browser a lesser experience on the site then with another..

    If i decide to block all user agents matching IE, would i also be liable?…

    I’d love to see an example of where someone has enforced this, i can’t imagine how anyone could honestly expect to hold up such an argument.

    I’m curious…

    Seriously i’d love to see someone try to pull that one..

    It’s been done. At least 3 cases in the UK (all settled out of court with non-disclosure agreements – more’s the pity). 1 famous case in Australia against the Olympic web site some years ago. 3 successful cases in the US (Ramada, Priceline and Target) under ADA

    If it’s your webspace, you’re free to do with as you choose as long as you’re within the terms of service with your webhost, for example no adult content, or racism, etc…

    …and provided you don’t discriminate against anyone due to lack of “reasonable adjustments”. That means not just providing wheelchair access where there are stairs in buildings but equal access to electronic information.

    I can’t see how anyone could seriously mount a case against a developer

    The case would be against the site owner but you can bet your bottom dollar that the owner would come after the developer(s) if at all possible.

    for giving people with a particular browser a lesser experience on the site then with another

    The issue isn’t the quality of experience, per se. It’s equal access. If someone chooses to use an old browser, then fair enough. But if you design a site that you know will only work on IE and somebody relies on Opera for their AT (assistive technology) and, therefore, cannot use the site, they could potentially claim that they had been discriminated against because of their disability.

    The landmark Australian case revolved around the fact that a blind user couldn’t access the cricket scores using a screen (or braille) reader on the Sydney Olympic site when his sighted neighbours could. He won and the Olympic committee responsible was hauled over the coals for not providing reasonable equal access.

    It’s been the law in the UK since 1999. ??

    If i decide to block all user agents matching IE, would i also be liable?…

    If you were the site owner, yes. Primarily because the two most common screen readers (JAWS and WindowEyes) are only officially supported with IE.

    I’d love to see an example of where someone has enforced this

    https://blackwidows.co.uk/blog/2009/02/23/law-school-site-sued-over-web-access-issues/
    https://blackwidows.co.uk/blog/2008/09/30/accessible-itunes/
    https://blackwidows.co.uk/blog/2007/10/03/target-lawsuit-goes-ahead/
    https://blackwidows.co.uk/blog/2007/02/12/us-organisations-liable-under-uk-law/

    I’m curious…

    https://www.gawds.org is a good place to start

    https://accessites.org because it shows that accessible design can also mean cool design.

    Then there’s https://codex.www.ads-software.com/Accessibility which you must have missed. ??

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Treating IE6 users as they deserve’ is closed to new replies.