<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Web Research Blog - Web Access, Automation, Customization, and Media</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/" />
    <link rel="self" type="application/atom+xml" href="http://www.jeffreybigham.com/accessibility/atom.xml" />
    <id>tag:www.jeffreybigham.com,2009-01-28:/accessibility//1</id>
    <updated>2010-01-26T20:52:44Z</updated>
    <subtitle>News and insights into access technology, web automation and customization, web-based media, and the social web from a researcher&apos;s perspective</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.32-en</generator>

<entry>
    <title>Legitimately Pushing Google Voice Text Messages on iPhone</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2010/01/legitimately-pushing-google-voice-text-messages-on-iphone.html" />
    <id>tag:www.jeffreybigham.com,2010:/accessibility//1.34</id>

    <published>2010-01-24T22:55:49Z</published>
    <updated>2010-01-26T20:52:44Z</updated>

    <summary>I really like Google Voice, but Apple refuses to accept it in the iPhone&apos;s App Store. Google provides a web-based Google Voice - the version just released today (1/26) looks pretty much like the Google Voice iPhone application that was...</summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="apple" label="Apple" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="appstore" label="AppStore" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="att" label="AT&amp;T" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="google" label="Google" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="googleappengine" label="Google App Engine" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="googlevoice" label="GoogleVoice" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="iphone" label="IPhone" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="twitter" label="Twitter" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[<a href="http://www.jeffreybigham.com/accessibility/system-diagram.png"><img alt="System Diagram that connects Google App Engine, to Twitter, to EchoFon on iPhones" src="http://www.jeffreybigham.com/accessibility/assets_c/2010/01/system-diagram-thumb-550x243-7.png" class="mt-image-none" height="216" width="490" /></a><div><br /><font face="-editor-proxy">I really like <a class="zem_slink" href="http://www.google.com/googlevoice/about.html" title="Google Voice" rel="homepage">Google Voice</a>, but Apple refuses to accept it in the <a class="zem_slink" href="http://www.apple.com/iphone" title="iPhone" rel="homepage">iPhone</a>'s <a class="zem_slink" href="http://www.apple.com/iphone/appstore/" title="App Store" rel="homepage">App Store</a>. Google provides a web-based </font><a href="http://voice.google.com/">Google Voice</a> - the version just released today (1/26) looks pretty much like the Google Voice iPhone application that was rejected from the store.&nbsp; The problem is that the web page is <i>pull</i>-only - and without <i>push</i> you don't get notified of new text messages or voicemails - you have to actually visit the site.&nbsp; I set out to try to fix this, and came up with a solution that works really well and is completely legitimate -- no Apple approval required!<br /><br />The summary is this - my <a class="zem_slink" href="http://code.google.com/appengine/" title="Google App Engine" rel="homepage">Google App Engine</a> application polls Google Voice every 15-20 seconds looking for new text messages. If a new text message is found, then the application sends a direct message containing the sender of the text message and the message itself to my <a class="zem_slink" href="http://twitter.com/" title="Twitter" rel="homepage">Twitter</a> account from a Twitter account that I set up for this purpose. I have EchoFon running on my phone, which does Push notifications (I needed the $4.99 Pro version of EchoFon to do this), so that when a new DM arrives my phone vibrates and rings.<br /><br />The end effect is that when I get texts on my Google Voice account, my phone acts almost exactly like it would if I had received a text message from <a class="zem_slink" href="http://www.att.com/" title="AT&amp;T" rel="homepage">AT&amp;T</a>.&nbsp; I've timed the round trip and it's less than 90 seconds on average. I can respond to the message using the web-based version of Google Voice by clicking a link included with the message.<br /><br />Because this uses Twitter, there's nothing Apple or AT&amp;T can deny from the App Store unless they agree to deny all Push applications (instead of Twitter, these could be Facebook messages, emails, fake point-of-interest near your location) - so, you don't need approval to run it!<br /><br />I'll update this post with details of this solution in a few days so you can get free Google Voice push on your phone too!<br /></div>

<div style="margin-top: 10px; height: 15px;" class="zemanta-pixie"><a class="zemanta-pixie-a" href="http://reblog.zemanta.com/zemified/1433b5b9-3e43-4d36-8a5a-dae185f082b1/" title="Reblog this post [with Zemanta]"><img style="border: medium none ; float: right;" class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=1433b5b9-3e43-4d36-8a5a-dae185f082b1" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script type="text/javascript" src="http://static.zemanta.com/readside/loader.js" defer="defer"></script></span></div><div><br /></div>]]>
        
    </content>
</entry>

<entry>
    <title>What if Science were like Banking?</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2010/01/what-if-science-were-like-banking.html" />
    <id>tag:www.jeffreybigham.com,2010:/accessibility//1.33</id>

    <published>2010-01-16T18:00:38Z</published>
    <updated>2010-01-16T20:15:51Z</updated>

    <summary><![CDATA[Science Editor: &nbsp;Hey boss, we just got an incredible submission! &nbsp;It's titled "Merry-Go-Round Warp Drive" and it explains how to exceed the speed of light! &nbsp;See, all you gotta do is get the merry-go-round going up to like 99.9% of...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="bankingsciencemedicalresearchgradstudent" label="banking science medical research grad student" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[<b><br />Science Editor:</b> &nbsp;Hey boss, we just got an incredible submission! &nbsp;It's titled "Merry-Go-Round Warp Drive" and it explains how to exceed the speed of light! &nbsp;See, all you gotta do is get the merry-go-round going up to like 99.9% of the speed of light and then make it really big. &nbsp;The outside part will then be going way faster than the speed of light.<div><br /></div><div><b>Science Senior Editor:</b> Who is this guy? &nbsp;What lab's he at?</div><div><br /></div><div><b>Science Editor:</b> &nbsp;That's the thing - this is a 12-year-old genius savant. &nbsp;He turned it in for his sixth-grade science homework.</div><div><br /></div><div><b>Science Senior Editor:</b> Buy the rights. In fact, buy the rights to the whole damn class' homework assignments - we'll bundle 'em all up into a special issue, maybe sell it to Nature!</div><div><br /></div><div>Better yet, let's bundle 'em, then auction them off paragraph by paragraph!</div><div><br /></div><div><b>Grad Student:</b>&nbsp;But the articles won't make any sense then.</div><div><br /></div><div><b>Dr. Bigwig, Ph.D.:</b>&nbsp;&nbsp;Exactly! &nbsp;They'll be difficult to understand, causing everyone to believe they must be incredibly ground-breaking, driving up prices (and our reputations).</div><div><br /></div><div><br /></div><div><br /></div><div>...a few months later in a lab near you</div><div><br /></div><div><br /></div><div><br /></div><div><b>Grad Student:</b> &nbsp;I've got this great idea for how to cure cancer. &nbsp;If we can get people moving up to the speed of light then they'll become super-conductors and we can zap them and all the free radicals in their bodies without hurting them. It could stave off or even cure existing cancers!</div><div><br /></div><div><b>Dr. Bigwig, Ph.D.:</b> &nbsp;I'm a bit skeptical - how would you get them up to the speed of light, isn't that impossible?</div><div><br /></div><div><div class="zemanta-img mt-image-right zemanta-action-dragged" style="margin-top: 1em; margin-right: 1em; margin-bottom: 1em; margin-left: 1em; display: block; float: right; width: 310px; "><a href="http://commons.wikipedia.org/wiki/Image:Interferometer.JPG"><img src="http://upload.wikimedia.org/wikipedia/commons/thumb/b/b8/Interferometer.JPG/300px-Interferometer.JPG" alt="Interference of split light beams" width="300" height="293" /></a><p class="zemanta-img-attribution" style="font-size:0.8em">Image via <a href="http://commons.wikipedia.org/wiki/Image:Interferometer.JPG">Wikipedia</a></p></div><p class="zemanta-img-attribution" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0.75em; margin-left: 0px; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; font-size: 0.8em; font-weight: normal; ">Image via&nbsp;<a href="http://commons.wikipedia.org/wiki/Image:Interferometer.JPG" style="text-decoration: underline; ">Wikipedia</a></p></div><div><br /></div><div><b>Grad Student:</b> &nbsp;No! &nbsp;There's this new result out of McKinley Middle School that shows how to exceed the speed of light - we'd just have to spin them really, really fast and then zap them.</div><div><br /></div><div><b>Dr. Bigwig, Ph.D.:</b> You know, I've heard that there's a new result showing how if you spin something fast enough it can be made to move faster than the speed of light. &nbsp;We could do that...and <i>then</i>&nbsp;zap them.</div><div><br /></div><div><b>Grad Student:</b> Right that's what I ...</div><div><br /></div><div><b>Dr. Bigwig, Ph.D.:</b> Ok, then we're all set! &nbsp;What a great idea I had! &nbsp;I'm going to be famous!</div><div><br /></div><div><b>Grad Student:</b> But can we get IRB approve it?</div><div><br /></div><div><b>Dr. Bigwig, Ph.D.:</b> Ha! &nbsp;IRB's are a worry of the past - the past few administrations have realized that the IRB was stifling creativity - they still exist, but their responsibilities have been reduced to getting coffee for one another and hassling HCI students wanting to do surveys. They've realized that we wouldn't dare do something dangerous - it would hurt our reputations, so subject protection is self-moderating.</div><div><br /></div><div><b>Grad Student:</b> &nbsp;Great! &nbsp;So I'll schedule the first couple of participants and see how they react.</div><div><br /></div><div><b>Dr. Bigwig, Ph.D.:</b> That's so slow, I need pay-off now. &nbsp;Bring in 100 people, do it all at once, you'll save time and money.</div><div><br /></div><div><b>Grad Student:</b> &nbsp;You're so smart Dr. Bigwig, Ph.D. &nbsp;I'll schedule them all as soon as I can attach this platform to this blender motor and rig up this wire for them to hold to an electrical outlet.</div><div><br /></div><div><br /></div><div><br /></div><div>...a few days later at a hospital near you</div><div><br /></div><div><br /></div><div><br /></div><div><b>Resident:</b> Doctor! &nbsp;We have just received 100 patients all with electric shocks, burns, and dizziness. I've quickly surveyed them and it appears the patient John Q. is in the worst shape - we should get him to surgery stat!</div><div><br /></div><div><b>Doctor:</b> Damn residents! Get this jerk out of here, bring in C. E. Oppenheimer, and tell that jackass to keep up with the latest medical research before gambling with people's lives.</div><div><br /></div><div>Now C., I'm glad I was able to intervene and see you first - your chart indicates your high levels of cash - is there anything I can get you? &nbsp;Coffee, juice?</div><div><br /></div><div><br /></div><div><br /></div><div>...at a conference on a small island paradise off&nbsp;Morocco</div><div><br /></div><div><br /></div><div><br /></div><div><b>Dr. Bigwig, Ph.D.:</b> &nbsp;"...and so after 2 years, of the 100 subjects in the experimental condition, all of whom were previously diagnosed with stage 4 cancer, NONE had died <i>from cancer.</i>"</div><div>&nbsp;</div><div><br /></div><div><br /></div><div>... later that evening</div><div><br /></div><div><br /></div><div><br /></div><div><b>Dr. Bigwig, Ph.D. (on phone with dean): </b>"The university has onlly awarded me 20 x current tuition for my annual bonus - this is simply unacceptable. My contract clearly states that I am to be awarded 30 x annual undergrad tuition. You know the Ivies have been calling me - if you want to remain keep the top talent, you need to reward me for my stellar performance."</div><div><br /></div><div><b>Dean:</b>&nbsp;"But Dr. Bigwig, you killed 100 people...I know you're worth 30 x annual undergraduate tuition, but you know the parents and alumni - they just don't understand. How about I give you 10 full undergraduate tuition tickets that you could sell to future undergraduates in a year after these crazy politics have died down?"</div><div><br /></div><div><br /></div><div>Stay tuned for next week's article --- &nbsp;what if banking were like science?</div>

<div class="zemanta-pixie" style="margin-top:10px;height:15px"><a class="zemanta-pixie-a" href="http://reblog.zemanta.com/zemified/725890b2-6f14-4071-a8cc-027fd980b399/" title="Reblog this post [with Zemanta]"><img class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=725890b2-6f14-4071-a8cc-027fd980b399" alt="Reblog this post [with Zemanta]" style="border:none;float:right" /></a><span class="zem-script more-related pretty-attribution"><script type="text/javascript" src="http://static.zemanta.com/readside/loader.js" defer="defer"></script></span></div>]]>
        
    </content>
</entry>

<entry>
    <title>WebAnywhere Gets A New Voice</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2010/01/webanywhere-gets-a-new-voice.html" />
    <id>tag:www.jeffreybigham.com,2010:/accessibility//1.32</id>

    <published>2010-01-10T16:18:29Z</published>
    <updated>2010-01-10T16:22:34Z</updated>

    <summary><![CDATA[Check out the new voice on&nbsp;WebAnywhere. The voice currently being used is "Jennifer" from&nbsp;Ivona. The inclusion of this voice was made possible by a very generous donation from Ivona. It's incredibly pleasant, a real treat to listen to! &nbsp;If you'd...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="webanywherevoiceivonascreenreader" label="webanywhere voice ivona screen reader" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[Check out the new voice on&nbsp;<a href="http://webanywhere.cs.washington.edu/beta/">WebAnywhere</a>. The voice currently being used is "Jennifer" from&nbsp;<a href="http://www.ivona.com">Ivona</a>. The inclusion of this voice was made possible by a very generous donation from Ivona. It's incredibly pleasant, a real treat to listen to! &nbsp;If you'd like to use it for other things, Ivona sells a SAPI compliant version.<div><br /></div><div>Look for great things in the future for WebAnywhere's voice. Ivona's donated a few other languages that are just as high quality, so we'll be rolling those out as quickly as possible. Also, we're still looking for a free, high-quality voice that we can use that can be sped up.</div>]]>
        
    </content>
</entry>

<entry>
    <title>Apple Tablet Could Be A Kindle Killer</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2010/01/apple-tablet-could-be-a-kindle-killer.html" />
    <id>tag:www.jeffreybigham.com,2010:/accessibility//1.31</id>

    <published>2010-01-06T18:13:47Z</published>
    <updated>2010-01-06T18:25:13Z</updated>

    <summary><![CDATA[A lot of people have been talking about the rumoured Apple Tablet - a new large-screen, multi-touch device that Apple will introduce priced in between its iPhone 3GS and Mac Books.&nbsp; What I haven't heard is about how this might...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[A lot of people have been talking about the rumoured Apple Tablet - a new large-screen, multi-touch device that Apple will introduce priced in between its iPhone 3GS and Mac Books.&nbsp; What I haven't heard is about how this might just be the perfect reading device, and one that can more than compete with the Kindle (whether or not it includes the fancy digital paper.)&nbsp; And the reason is accessibility.<br /><br />Apple designs great products, and actually includes good access technology on them *for free.* Because the iPhone includes VoiceOver it's quickly becoming the most sought-after phone for blind people.&nbsp; OS X includes a version of VoiceOver that's a fully-functioning screen reader, as opposed to Window's Narrator which true to its name kind of just tells you the high-level of what's going on without letting you actually get much of anything done.<br /><br /><br />Wisconsin <a href="http://www.wkowtv.com/Global/story.asp?S=11637477">already dropped the Kindle</a> due to its inaccessibility, and despite some rather vague claims of how they're going to hack in some basic accessibility features, Amazon has already shown that accessibility will take a back seat.&nbsp; Schools (secondary and post-secondary) don't want to deal with inaccessible products unless there's a clear advantage - I think this is one case where if you can read books on Apple's tablet they win.&nbsp; Granted there are cost considerations - but the Kindle's already pretty darn expensive for something that pretty much only reads books (most of which you have to buy for $10-20 a pop!).<br /><br />We in the accessibility field often say that accessibility can differentiate products - I'm really interested to see if this will turn out to be a clear example of that!<br />&nbsp;<br />]]>
        
    </content>
</entry>

<entry>
    <title>Why Comcast Should Have Held Firm Against Fox</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2010/01/why-comcast-should-have-held-firm-against-fox.html" />
    <id>tag:www.jeffreybigham.com,2010:/accessibility//1.29</id>

    <published>2010-01-02T17:21:22Z</published>
    <updated>2010-01-04T19:07:16Z</updated>

    <summary>Image via WikipediaIn the last few days, Fox was able to strong-arm a better deal with Comcast, likely upping the price paid to the broadcaster for each subscriber (likely in the middle of the $1 Fox demanded and the $0.30...</summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="broadcast" label="Broadcast" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="cabletelevision" label="Cable television" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="comcast" label="Comcast" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="fox" label="Fox" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="hulu" label="Hulu" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="television" label="Television" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="youtube" label="YouTube" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[<div class="zemanta-img mt-image-right" style="margin: 1em; display: block; float: right; width: 159px;"><a href="http://commons.wikipedia.org/wiki/Image:FOX_wordmark.svg"><img src="http://upload.wikimedia.org/wikipedia/commons/thumb/2/25/FOX_wordmark.svg/300px-FOX_wordmark.svg.png" alt="The current logo of Fox Television" height="64" width="149" /></a><p class="zemanta-img-attribution" style="font-size: 0.8em;">Image via <a href="http://commons.wikipedia.org/wiki/Image:FOX_wordmark.svg">Wikipedia</a></p></div>In the last few days, Fox was able to strong-arm a better deal with <a class="zem_slink" href="http://comcast.com/" title="Comcast" rel="homepage">Comcast</a>, likely upping the price paid to the broadcaster for each subscriber (likely in the middle of the $1 Fox demanded and the $0.30 Comcast offered). On the surface this seems ridiculous for a number of reasons - namely, (i) most subscribers should be able to get Fox for free over the air if they have the antenna and converter box and (ii) Fox somehow makes enough ad money to support local broadcasting stations all over the country, which can't be cheap. There's a good case to be made that by "standing firm" Fox is actually putting another nail in its coffin - or at least in the coffin of its current business model.<br /><br />(This posts gets a little away from the accessibility core of this blog, but I'll wrap up with little blurb connecting it in.)<br /><br />A building tsunami is set to wreck the current business models of the networks. Since the dawn of television, the networks have enjoyed a psuedo-monopoly on content delivery - it was just too darn expensive for small folks to deliver their own content. Cable has been ever-so-gradually chipping away at that advantage with the introduction of new channels, but they've locked us all in with packages that still only deliver less than 100 channels for a reasonable price. Those channels are also still burdened with having to deliver 24 hours of content every single day.&nbsp; What happens when there are millions of channels available, that may pop into or out of existence as they have content to deliver, for lower cost that the expensive packages we have now?<br /><br />Before addressing that question, lets first ask what exactly Fox (and the other networks) offer us? On the one hand, they're the only ones big enough to afford to buy the rights to broadcast big events - sports, the Olympics, etc, and to some extent they're the only ones who can develop high budget sitcoms and dramas. But because of how networks work, those shows need to target a really broad audience and still make a strong showing among certain age categories that really drive ad revenues). How can the junk on <a class="zem_slink" href="http://www.youtube.com/" title="YouTube" rel="homepage">YouTube</a> compete?&nbsp; But then, if people were free to watch whatever they wanted, and not limited by the networks - how long would it be before the NFL decides they'd rather take the bigger piece of the pie by broadcasting games online on their own?<br /><br />There will always be people, groups and organizations willing to support the creation of content - sports leagues of course, as well as someone to make the Bachelor and even (regretfully) the Real Housewives of Wherever Is Next.&nbsp; The biggest question remaining is whether the networks are needed in the middle. There's definitely a role for something like networks, but it's not clear you need the big dogs that the networks have become. You need someone to produce, market, and bankroll -- but you no longer need the final channel out to people.<br /><br />That channel is quickly becoming the Internet - with <a class="zem_slink" href="http://www.mythtv.org/" title="MythTV" rel="homepage">MythTV</a>, <a class="zem_slink" href="http://en.wikipedia.org/wiki/Apple_TV" title="Apple TV" rel="wikipedia">AppleTV</a>, <a class="zem_slink" href="http://beta.sling.com/" title="Slingbox" rel="homepage">SlingBox</a>, <a class="zem_slink" href="http://www.boxee.tv/" title="Boxee" rel="homepage">Boxee</a>, and Netflix it's not clear you need the networks or cable television. <a class="zem_slink" href="https://www.hulu.com/" title="hulu" rel="homepage">Hulu</a> is the network's attempt to remain in control, but it's simultaneously wets the appetite of more people for free, instantly available content and remains remarkably inadequate - too few shows and no live events. If the other networks follow suit, working out stronger deals with the cable companies, more people will disconnect their cable.<br /><br />While the networks will remain, their importance will diminish. What will replace them are thousands of smaller "networks" that will help people make the sense of all the new content that they now have access to - something the networks used to do and something that non-networks can and will eagerly do. Putting content up is one thing, but the main functionality still lacking is a "playlist," something to help folks who just want to turn on the tube find interesting shows and not have to get up every 30 minutes to find something else.&nbsp; That is, I hypothesize that channels won't go away just because the networks have.<br /><br />In summary, as the networks seek to capitalize on their own sense of self-importance, they are dooming themselves. Until a viable alternative to cable Internet comes along, the cable companies themselves have little to worry about - I have no doubt that they will find a way to offset declining revenues from the droves dropping cable television with new fees or services to help people watch Internet television. The networks will be the losers, and will be losers of their own creations.<br /><br />Of course, all of this is speculation.&nbsp; I'm hoping to begin investigating the hypotheses suggested in this article soon.<br /><br />Finally, I promised to connect this back to access. History has shown that large shifts in popular technology used to consume information often comes with access problems. The networks represented a small set of companies on which to focus complaints, and as powerful corporations public opinion could easily help bring legislation offering requirements. If millions of smaller entities replace the networks, it will be harder to regulate - who will provide captions? This is already a problem on YouTube and other video sharing sites.<br /><br />But, the earlier we think about such issues, the better chance we have of heading them off before they become too big of problems to readily address.<br />

<div style="margin-top: 10px; height: 15px;" class="zemanta-pixie"><a class="zemanta-pixie-a" href="http://reblog.zemanta.com/zemified/49e6e071-34b5-45c6-9729-cba1dae19191/" title="Reblog this post [with Zemanta]"><img style="border: medium none ; float: right;" class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=49e6e071-34b5-45c6-9729-cba1dae19191" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script type="text/javascript" src="http://static.zemanta.com/readside/loader.js" defer="defer"></script></span></div>]]>
        
    </content>
</entry>

<entry>
    <title>ASSETS 2009 Round-Up</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/11/assets-2009-round-up.html" />
    <id>tag:www.jeffreybigham.com,2010:/accessibility//1.30</id>

    <published>2009-11-02T21:16:23Z</published>
    <updated>2010-01-02T21:26:13Z</updated>

    <summary>ASSETS 2009 happened just a few days ago, and it was once again a great showing of the exciting research happening at the intersection of computer science, human computer interaction, and access technology.Some highlights (from my perspective, of course), were...</summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[<a href="http://www.sigaccess.org/assets09/">ASSETS 2009</a> happened just a few days ago, and it was once again a great showing of the exciting research happening at the intersection of computer science, human computer interaction, and access technology.<br /><br />Some highlights (from my perspective, of course), were the best paper awards, who went to two really great papers.&nbsp; The best student paper (that I must admit I was a co-author on) was entitled "<a href="http://portal.acm.org/citation.cfm?id=1639642.1639656&amp;coll=portal&amp;dl=ACM&amp;type=series&amp;idx=SERIES368&amp;part=series&amp;WantType=Proceedings&amp;title=ASSETS&amp;CFID=59263020&amp;CFTOKEN=22667894">ClassInFocus: Enabling Improved Visual Attention Strategies for Deaf and Hard of Hearing Students</a>" and was written by Anna Cavender, Jeffrey P. Bigham, and Richard E. Ladner. It introduces a really great system for enabling deaf and hard of hearing students to combine multiple sources of information all on a single screen in the classroom, and some novel notification strategies to help them know what to pay attention to when.<br /><br />The best paper award went to a great paper entitled <a href="http://portal.acm.org/citation.cfm?id=1639642.1639677&amp;coll=portal&amp;dl=ACM&amp;type=series&amp;idx=SERIES368&amp;part=series&amp;WantType=Proceedings&amp;title=ASSETS&amp;CFID=59263020&amp;CFTOKEN=22667894">"Collaborative Web Accessibility Improvement: Challenges and Possibilities</a>", that came out of the <a class="zem_slink" href="http://en.wikipedia.org/wiki/IBM_Tokyo_Research_Laboratory" title="IBM Tokyo Research Laboratory" rel="wikipedia">IBM Tokyo Research Lab</a> and was written by&nbsp; Hironobu Takagi, Shinya Kawanaka, Masatomo Kobayashi, Daisuke Sato, and Chieko Asakawa. This paper highlights some introducing qualities of the Social Accessibility Framework that they've been developing and overviews their initial challenges and successes.<br /><a href="http://portal.acm.org/citation.cfm?id=1639642.1639677&amp;coll=portal&amp;dl=ACM&amp;type=series&amp;idx=SERIES368&amp;part=series&amp;WantType=Proceedings&amp;title=ASSETS&amp;CFID=59263020&amp;CFTOKEN=22667894"></a><div><br /></div>

<div style="margin-top: 10px; height: 15px;" class="zemanta-pixie"><a class="zemanta-pixie-a" href="http://reblog.zemanta.com/zemified/c767e84f-ba33-4243-b4be-295474f8fefc/" title="Reblog this post [with Zemanta]"><img style="border: medium none ; float: right;" class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=c767e84f-ba33-4243-b4be-295474f8fefc" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script type="text/javascript" src="http://static.zemanta.com/readside/loader.js" defer="defer"></script></span></div>]]>
        
    </content>
</entry>

<entry>
    <title>Response Time over 24 Hours</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/08/response-time-over-24-hours.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.28</id>

    <published>2009-08-12T13:56:36Z</published>
    <updated>2009-08-12T13:59:52Z</updated>

    <summary><![CDATA[In my continuing effort to leverage Mechanical Turk to help with accessibility tasks, I've done another experiment on Mechanical Turk.&nbsp; The full results of the experiment are posted on MIT's Deneme blog.The main results are that turkers seem to be...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="mechanicalturk" label="mechanical turk" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[In my continuing effort to leverage Mechanical Turk to help with accessibility tasks, I've done another experiment on Mechanical Turk.&nbsp; The <a href="http://groups.csail.mit.edu/uid/deneme/?p=157">full results of the experiment</a> are posted on MIT's Deneme blog.<br /><br />The main results are that turkers seem to be around 24 hours a day and are relatively quick - took less than 100 seconds on average to get an answer back.&nbsp; Now, we'll have to see if we can play some tricks to make this even faster.<br /><br />In related news, I heard a rumor from a reliable source that WebVisum might be responsible for at least some of those CAPTCHAs that you see posted on Mechanical Turk.&nbsp; This is somewhat surprising to me, since I would have expected them to use a free volunteer-based model.&nbsp; In any case, it's still not clear to me how it works.<br /> ]]>
        
    </content>
</entry>

<entry>
    <title>Harnessing Human Computation in the Real World</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/07/harnessing-human-computation-in-the-real-world.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.27</id>

    <published>2009-07-15T22:30:14Z</published>
    <updated>2009-07-15T22:37:50Z</updated>

    <summary>I&apos;ve had the great pleasure of spending some time with the UID Group at MIT CSAIL.They&apos;re thinking a lot about harnessing Mechanical Turk to complete a variety of tasks, and how MT might be integrated seamlessly into software - what...</summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[I've had the great pleasure of spending some time with the UID Group at MIT CSAIL.<div><br /></div><div>They're thinking a lot about harnessing Mechanical Turk to complete a variety of tasks, and how MT might be integrated seamlessly into software - what if calling on a turker was a simple as calling a function? &nbsp;What would that look like and what could you do with it?</div><div><br /></div><div>For a while, I've been toying with the idea of using MT to help blind people not with improving web accessibility, but with everyday, real-world tasks. One simple application might, for instance, help blind people find objects that they've lost.</div><div><br /></div><div>A big question is how quickly we could get Turkers to answer a question like that. &nbsp;As a first step, I ran a small experiment in which I asked turkers to click on some duct tape in a picture.</div><div><br /></div><div><a href="http://groups.csail.mit.edu/uid/turkit-blog/?p=82">The Results</a>&nbsp;are posted here. &nbsp;In summary, we got 10 turkers to click on the duct tape in the picture correctly for just 1 cent each. &nbsp;We got the first answer after 90 seconds, and had all 10 in a little over 3 minutes. &nbsp;Very encouraging results for realtime human computation being practical and affordable!</div><div><br /></div>]]>
        
    </content>
</entry>

<entry>
    <title>Dissertation Done!</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/06/dissertation-done.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.26</id>

    <published>2009-06-22T18:31:41Z</published>
    <updated>2009-06-22T18:38:40Z</updated>

    <summary><![CDATA[Last week, I finished and submitted my dissertation entitled Intelligent Interfaces "Enabling Blind Web Users to Build Accessibility Into the Web."&nbsp; This work is a great summary of the work that I've been doing in accessibility over the past few...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="dissertation" label="dissertation" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="trailblazer" label="trailblazer" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="webanywere" label="webanywere" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[Last week, I finished and submitted my dissertation entitled Intelligent Interfaces "Enabling Blind <a href="http://webinsight.cs.washington.edu/papers/dissertation/dissertation.pdf">Web Users to Build Accessibility Into the Web</a>."&nbsp; This work is a great summary of the work that I've been doing in accessibility over the past few years, and a good guide to where I think access technology and the web will be going in the future.<br /><br />The more we understand about how people interact with web content, the more we can help automatically and *unobtrusively* adapt content to better suit the needs of users.&nbsp; I think disabled users themselves can (and maybe must) play an integral role in this process to make it happen more quickly.<br /><br />The thesis of my dissertation is:<br /><i>With intelligent interfaces supporting them, blind end users can collaboratively and effectively improve the accessibility, usability, and availability of their own web access.<br /></i> ]]>
        
    </content>
</entry>

<entry>
    <title>Global Reach of WebAnywhere</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/06/global-reach-of-webanywhere.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.25</id>

    <published>2009-06-21T19:58:02Z</published>
    <updated>2009-06-21T20:51:38Z</updated>

    <summary><![CDATA[Although we didn't originally design WebAnywhere thinking of reaching a global audience, one of the important advantages of it is anyone across the globe can get immediate access to the latest version just by visiting the WebAnywhere Website.&nbsp; The graph...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="webanywhere" label="WebAnywhere" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[Although we didn't originally design WebAnywhere thinking of reaching a global audience, one of the important advantages of it is anyone across the globe can get immediate access to the latest version just by visiting the <a href="http://wa.cs.washington.edu/">WebAnywhere Website</a>.&nbsp; The graph below, along with the associated numbers, demonstrate the very real global reach we've achieved in such a short itme.<br />.<br /><br /><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.jeffreybigham.com/accessibility/pics/countries.png"><img alt="Comma-separated list of country/number of visitors pairs -- UNITED STATES: 6815, UNITED KINGDOM: 2307, CANADA: 675, ITALY: 611, INDIA: 455, AUSTRALIA: 409, SPAIN: 351, TAIWAN: 341, URUGUAY: 335, BRAZIL: 321, GERMANY: 315, SINGAPORE: 273, FRANCE: 265, CHINA: 207, HONG KONG: 147, THAILAND: 137, NEW ZEALAND: 127, JAPAN: 97, NETHERLANDS: 95, MEXICO: 67, SWITZERLAND: 59, AUSTRIA: 57, DENMARK: 51, POLAND: 51, IRELAND: 49, BELGIUM: 47, PORTUGAL: 43, SWEDEN: 43, MALAYSIA: 37, SOUTH AFRICA: 37, ARGENTINA: 35, IRAN: 33, UNITED ARAB EMIRATES: 33, FINLAND: 29, OMAN:29, NORWAY: 27, CHILE: 25, SLOVAKIA: 21, ISRAEL: 19, TURKEY: 19" src="http://www.jeffreybigham.com/accessibility/assets_c/2009/06/countries-thumb-600x304-5.png" class="mt-image-center" style="margin: 0pt auto 20px; text-align: center; display: block;" width="600" height="304" /></a></span>]]>
        
    </content>
</entry>

<entry>
    <title>Alt Text - Still A Problem, This Time on the NYTimes</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/04/alt-text---still-a-problem-this-time-on-the-nytimes.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.24</id>

    <published>2009-04-25T17:57:05Z</published>
    <updated>2009-04-27T14:04:53Z</updated>

    <summary><![CDATA[I was reading the NYTimes today, and ran across the following editorial. &nbsp;The point of the article is to show some of the statistics involving intolerance and child suicide. &nbsp;Unfortunately, all of the interesting data tables were presented as graphics...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="accessibility" label="accessibility" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="alttext" label="alt text" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="images" label="images" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="standards" label="standards" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="webinsight" label="webinsight" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[I was reading the NYTimes today, and ran across the <a href="http://blow.blogs.nytimes.com/2009/04/24/two-little-boys/">following editorial</a>. &nbsp;The point of the article is to show some of the statistics involving intolerance and child suicide. &nbsp;Unfortunately, all of the interesting data tables were presented as graphics and none had alternative text provided.<div><br /></div><div>One table containing multiple columns, rows, and descriptive text, had the following HTML code:</div><div><br />

&lt;img src="http://graphics8.nytimes.com/images/blogs/blow/aug/bully3.jpg" alt="INSERT DESCRIPTION"&gt;

</div><div><br /></div><div>Whatever tool the author was using was smart enough to that alt text needed to be included for this image, but the author may have remained unaware.</div><div><br /></div><div>For 15 years, the lack of alt text has been a problem for web accessibility, and we haven't figured out a solution. &nbsp;The original <a href="http://webinsight.cs.washington.edu/projects/webinsight/">WebInSight</a> project could offer a solution by OCR'ing this text, but a lot of the structure would be lost.</div><div><br /></div><div>What needs to be done to prevent another decade from passing in which we still haven't solved the most basic and easiest to understand accessibility issue?</div>]]>
        
    </content>
</entry>

<entry>
    <title>Reactions of a Man on Crutches</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/04/reactions-of-a-man-on-crutches.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.23</id>

    <published>2009-04-03T17:22:50Z</published>
    <updated>2009-04-03T17:33:28Z</updated>

    <summary><![CDATA[The NYTimes had an article today describing the attention that a guy crutches has gotten by publishing photos of subway riders who did not offer him their seats. &nbsp;It's interesting - he discusses issues that disabled people might share. &nbsp;I...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[The NYTimes had an article today describing the attention that a guy crutches has gotten by publishing photos of subway riders who did not offer him their seats. &nbsp;It's interesting - he discusses issues that disabled people might share. &nbsp;I wonder if he would have gotten so much attention if he hadn't been someone who was temporarily disabled. &nbsp;I also wonder if it matters.<div><br /></div><div><a href="http://cityroom.blogs.nytimes.com/2009/04/03/man-on-crutches-in-train-with-camer/?hp">http://cityroom.blogs.nytimes.com/2009/04/03/man-on-crutches-in-train-with-camer/?hp</a></div>]]>
        
    </content>
</entry>

<entry>
    <title>Introduction to Screen Readers by Victor Tsaran, Yahoo</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/04/introduction-to-screen-readers-by-victor-tsaran-yahoo.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.22</id>

    <published>2009-04-03T16:42:45Z</published>
    <updated>2009-04-03T16:45:47Z</updated>

    <summary><![CDATA[I found this video to be a great introduction and confirmation of web accessibility issues for screen reader users. &nbsp;Victor is an incredible guy - I urge anyone interested in the area to watch his video. Victor Tsaran: &quot;An Introduction...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="screenreader" label="screen reader" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="users" label="users" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="video" label="video" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[I found this video to be a great introduction and confirmation of web accessibility issues for screen reader users. &nbsp;Victor is an incredible guy - I urge anyone interested in the area to watch his video.<div><br /></div><div><br /></div>

<div><object width="512" height="322"><param name="movie" value="http://d.yimg.com/static.video.yahoo.com/yep/YV_YEP.swf?ver=2.2.40" /><param name="allowFullScreen" value="true" /><param name="AllowScriptAccess" VALUE="always" /><param name="bgcolor" value="#000000" /><param name="flashVars" value="id=2686894&vid=514676&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/sch/cn/v/v1/w483/514676_320_224.jpeg&embed=1" /><embed src="http://d.yimg.com/static.video.yahoo.com/yep/YV_YEP.swf?ver=2.2.40" type="application/x-shockwave-flash" width="512" height="322" allowFullScreen="true" AllowScriptAccess="always" bgcolor="#000000" flashVars="id=2686894&vid=514676&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/sch/cn/v/v1/w483/514676_320_224.jpeg&embed=1" ></embed></object><br /><a href="http://video.yahoo.com/watch/514676/2686894">Victor Tsaran: &quot;An Introduction to Screen Readers&quot;</a> @ <a href="http://video.yahoo.com" >Yahoo! Video</a></div>]]>
        
    </content>
</entry>

<entry>
    <title>Base Level of Access More Important with Newspaper Closings</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/03/base-leve-of-access-more-important-with-newspaper-closings.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.21</id>

    <published>2009-03-23T13:21:38Z</published>
    <updated>2009-03-23T13:29:52Z</updated>

    <summary><![CDATA[During the past few weeks, large newspapers have stopped printing (most recently the&nbsp;Ann Arbor News). &nbsp;Most often, these print newspapers have said they still plan to provide news on their web sites. &nbsp;As this trend continues, as more of the...]]></summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="raisingthefloor" label="raisingthefloor" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="webanywhere" label="webanywhere" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[During the past few weeks, large newspapers have stopped printing (most recently the&nbsp;<a href="http://www.nytimes.com/aponline/2009/03/23/business/AP-Michigan-Newspapers.html">Ann Arbor News</a>). &nbsp;Most often, these print newspapers have said they still plan to provide news on their web sites. &nbsp;As this trend continues, as more of the information that used to be available in print or other forms becomes available only on the web, it becomes even &nbsp;more important that people have access to the tools they need to access computers wherever they have access to a computer.<div><br /></div><div><div>Our <a href="http://wa.cs.washington.edu">WebAnywhere</a>&nbsp;project is a start on this - providing free non-visual access to the web, but many of the people affected by events like newspapers stopping their print editions are those who could benefit from other interfaces. &nbsp;As just two examples, simpler interfaces could benefit all sorts of people who find current computers and browsers too complex, and magnification could benefit low-vision users. &nbsp;WebAnywhere is transitioning to a platform that can handle these diverse preferences and let anyone provide new interfaces that someone might find helpful.</div><div><br /></div><div>Toward this end, WebAnywhere is associated with the <a href="http://raisingthefloor.net/">RaisingtheFloor</a> initiative, which is a broad coalition of folks who have the goal of raising the base level &nbsp;of access for everyone, regardless of disability.</div></div>]]>
        
    </content>
</entry>

<entry>
    <title>WebAnywhere at CSUN</title>
    <link rel="alternate" type="text/html" href="http://www.jeffreybigham.com/accessibility/2009/03/webanywhere-at-csun.html" />
    <id>tag:www.jeffreybigham.com,2009:/accessibility//1.20</id>

    <published>2009-03-16T13:50:55Z</published>
    <updated>2009-03-16T13:56:18Z</updated>

    <summary>WebAnywhere will be visiting CSUN, so if you&apos;ll be there too and are interested in chatting, please find either me (Jeff Bigham) or Wendy Chisholm.Wendy will be speaking about AccessComputing on Wednesday at 9:20am in EMP-2006, and I will be...</summary>
    <author>
        <name>Jeff</name>
        
    </author>
    
    <category term="csun" label="CSUN" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="webanywhere" label="WebAnywhere" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-US" xml:base="http://www.jeffreybigham.com/accessibility/">
        <![CDATA[WebAnywhere will be visiting CSUN, so if you'll be there too and are interested in chatting, please find either me (Jeff Bigham) or Wendy Chisholm.<div><br /></div><div>Wendy will be speaking about AccessComputing on Wednesday at 9:20am in EMP-2006, and I will be speaking with Annuska Perkins as part of the Microsoft Imagine Cup presentation Saturday at 10:40am in BLV-1046.</div><div><br /></div><div>I'll also be checking email regularly, so if you'd like to meet to find out more about how you can become involved in the project, please email me at jbigham@cs.washington.edu.  I also plan to live blog the conference, so you'll be able to keep up with what I'm seeing in nearly real time. </div>]]>
        
    </content>
</entry>

</feed>
