Follow Up to Tesco Contact Form!.
So they got back in touch, of the 3 issues mentioned, they only talked about one. the fact I couldn’t read their email properly. Being asked if I have adobe reader to read their email is perhaps one of the most surreal things I have been asked in some time. Trying to explain to someone how to fix it who hasn’t got a clue was a waste of time, though I do hope I’m wrong.
No Tesco you do not need to use that to read you emails, you need to send out a text alternative to the HTML crap that you sent out. It was malformed HTML and I couldn’t read the email unless I read it in HTML mode. I guess their concerns about web accessibility has gone down recently then.
Before the BS standard for web accessibility was released, I was part of the team from GAWDS (Guild of Accessible Web Designers) that was involved with PAS78. So yeah it’s nice to check up on some of the big companies that have supposedly good web accessibility every now and then. Tesco, you failed with this one, the email, and the customer service. Satisfaction: 0.
This is a follow up to Tesco Spam.
I had cause to use this contact form today. I had just ordered something from them and the email that came through was useless for reading without HTML, no text alternative and HTML tags make it very difficult to read.
So navigating to their site and finding the link to the form I had my first issue, the security certificate was invalid, for whatever reason. But then after filling in the forum I hit the mobile number required. Now I don’t use one, and I don’t really want one. So I tried to put in n/a, didn’t accept it. I then tried 999… but they didn’t accept that either. Thankfully they had given an example number, and that did work.
So one complaint turned into 3. Thanks Tesco.
Followup: Tesco Support, bad, really really bad, and accessibility failure.
A few weeks ago I ordered from Tesco online. I then received one of their follow up emails suggesting I complete a survey, and then another and another … hourly.
I wrote to Tesco:
thank you for spamming my inbox on the hour every hour for the last 6
hours, I assume this will continue until the time has run out.
May I do the same in return and spam you, no? well please don’t do it
next day I get a response:
Thank you for your email and please accept my apologies for the delay in my
I’d also like to apologise that you’ve been inundated with messages from us, as
I too would feel equally unimpressed. Please rest assured that I’ve now
unsubscribed your email address to prevent this from happening in future. Please
kindly allow up to 14 days for this to take affect.
To which I replied:
thank you for you reply, I do hope you were being sarcastic when you said it could take up to 14 days for this to take effect.
That response does not instil me with confidence, and to be honest sounds like you are extracting the urine.
Follow up: Tesco Contact form!
No not the Gerry Anderson one, sadly. But the pile of crap that Mozilla has released as the update to Thunderbird 3. No I’m not sure what happened to 4 either.
- Inbox keeps crashing, no idea why.
- Basic plugins don’t work – why the hell can’t you navigate from one read email to another?
- Can’t compose emails properly, seriously, unable to add subject to recipient is kinda needed for an email client
- Looks pretty horrible as well, no color at all for the button icons makes them hard to distinguish
So anyone know of a decent alternative?
Within a year of releasing eShop I managed to get it onto the WordPress plugin repository. It certainly increased the number of downloads, and even brought in a little money – not that that was ever the intent. But I have become more and more frustrated ever since the Compatibility section was added to the plugins page. Why? because of the number of times that someone has marked it as Not Working – well sort of.
A case of strange but true tale of woe.
A few versions back I added in some functionality to my plugin, eShop, for users to view their orders. I called the file user.php. A lot of my other files have a preface of eshop_ in them. Now at the time I thought nothing of doing this, thinking the naming was suitable. Turns out it was, but caused major grief for IIS users.