SeroTalk Podcast 191: XP Pocolypse

Listen to SeroTalk Podcast 191: XP Pocolypse

Join Jamie, Ricky and Joe as they discuss the top news stories of the week. After the news, Jamie and Buddy sit down to talk about the release of iOS 7.1. Stories disccussed in this week’s podcast include:

A T Talk

29th Annual CSUN Conference on Disability news and info

Blind Bargains: The Updated Blind Bargains Guide to Attending #csun14 on a Budget

Blind Bargains: Meet the Visually Impaired Athletes of the 2014 Winter Paralympics

Blind Bargains: Solo DX Announces That They’re Closing Their Doors

Blind Bargains: Google Updates Text-to-Speech App with New Voices

Screen Magnification Survey

My Initial Thoughts On NBC’s Growing Up Fisher

Mainstream Matters

Weeks before expiration date, Windows XP still has 29% OS market share

Microsoft’s Attempt To Convert Users From Windows XP Backfires

Microsoft Security Essentials to nag Windows XP users

Target tech chief resigns as it overhauls security

Twitter error blamed for mass user password reset

Verizon has most reliable cellular network in test, AT&T has the fastest

Opinion: Does CarPlay go far enough, or should car manufacturers let Apple do more?

Apple Could Soon Make Siri Much Smarter, More Like ‘Her’

Mailbag

From Mike Arrigo:

Hi there. First, a slight correction. For the mac, Leopard which was 10.5 was actually the last version of the operating system to work on power pc computers. Starting with snow leopard 10.6, it was Intel only. It’s not too surprising that Apple dropped support for Snow Leopard, it came out in August of 2009, so it’s over 4 years old. Regarding the question of screen reader detection, ideally this should not be needed. Rather, the issues should be addressed at the heart of the matter. All major screen readers support features such as navigating by headings, reading tables, etc. What needs to happen is that the web sites need to use best practices such as putting headings in the right place, labeling their links, etc. Similarly, the screen readers need to keep up with an support the web standards as they evolve. If these things are done, there should be no need for a site to have to detect whether someone is using a screen reader. I’m also not a fan of the separate but equal approach. More often than not, what we get is not equal, it’s not as good. And again, if best practices are followed, there is no need for that in the first place.

From Eugene:

Hi Team,

I’ve been thinking about the topic of screen reader detection, as I’ve read both the survey and Marco’s article on the subject. My comments follow, but I’m quite opposed to the idea, and here’s why.

First, there’s the matter of employment. If a job-hunting organization like DICE can put screen reader detection into their websites, the info that somebody is using a screen reader may be sent to possible employers, and your chances of nabbing a job may be shrunk to near zero. Certainly, a screener in a company may not even bother passing the resume on if they see the addendum about screen reader detection on it. This alone should stop any consideration of this kind of detection, but there is a much more sinister reason.

A screen reader is inherently viral. It must have access to all the processes of the computer in order to grab the information requested by the user. It is also a key logger since this is crucial to its function. A web author can use screen reader detection to not only gain access to the screen reader, but may also (and, I suspect, rather easily) gain access to its functions and turn the computer into a constant source of reportage for the author. He could, with relatively little trouble, plant a bomb in the computer that may do something when a series of keystrokes is pressed by the user. When it comes to the Internet, I am paranoid, and although I know nobody is out to get me personally, they are out to get me impersonally, so this would be a very good way to gain control of a computer system.

The best way for accessibility on the Web to happen is for Web authors to follow the rules which are being sent out. If they do so, and use the Java accessibility protocols and tools, accessibility can almost be built into any application that is written. (The only glaring weakness to this argument is the QT model, which is notoriously inaccessible.)

The tools are out there. They’re easy to use. I know. I’ve done a bit of programming, and it’s very easy for a program to be accessible if you follow the rules. It’s the same way for web pages. Now, it’s time for the developers to wake up, hear the piper and follow his song.

Thanks for the podcasts, and keep the good info coming.

Yours, Eugene A. Hetzer Jr.

From shuiyee

Hi,

I am totally blind and listen to every of your podcast. I am from Malaysia. Sometimes when I listen to all the benefits you guys have in America I wish it would be the same here in Malaysia. We don’t have guide dogs here. I love dogs but because of my country being a multiracial and one is Muslim which they are very afraid of dogs. So its taking a very long time to even implement a guide dog here. It won’t be useful if we train our own dogs because it won’t be allowed in the shops or public transport. I am an adult blind facing chance of losing my job because I was training as a pharmacist when I lost my sight gradually through side effects of chemotherapy. I love reading books too and how I wish we have BARD app to read books. Even kindle app is not available here. Some ebooks that you guys can download for free we are not allowed to download here. I am just commenting that Americans are very lucky to be in America. However, I don’t complain much because I know there are countries that are far worse than Malaysia such as China or India, where there are many cases whereby the eye condition can be treated but due to poverty or lack of medical staff they can’t get it. I’m not even sure if I got the email address correct. So bye for now. Thank you for reading my email.

regards: shuiyee

Sent from my iPod

Another email from shuiyee

hi,

Since I’ve got the correct email I just want to ad my comments about the TapTapSee. I was sad when they started charging too. For us 1 us dollar is about 3.8 ringgit malaysia. So if you guys are paying ten dollars it would be about 40 ringgit for us. So I’ve decided not to use the app then. I wish to use audible too but everything is so expensive as we have to multiply US dollars by 3.8. Also I love your podcast, keep up the good work and hopefully there are many many episodes to come!

shuiyee

Roundabout

Bad brains: some people are physically incapable of enjoying music

What Happens in the Brain When Blind People Learn to See With Sound

Kids attempt to use rotary phone, confusion ensues

Podcast: Play in new window | Download

Subscribe: iTunes | RSS