Contribute to Twitter Presentation at CSUN10

Twitter And Assistive Tech

Dennis Lembree (@dennisl) and Joseph O’Connor (@blacktelephone) are presenting “Accessibility of Twitter for Mobile, Desktop and Web” at the 25th Annual International Technology and Persons With Disabilities Conference in San Diego, California. The conference dates are from March 22 to 27. The presentation is scheduled at 8:00 a.m., Thursday, March 25.

You Can Help!

We are asking you to tweet about using Twitter with assistive tech on two topics:

  • How do you deal with the interfaces?
  • How has Twitter changed things for you?

Optional: audio record the written Tweets at or whatever you want to use. If you do record, please be sure to record what you have written in each Tweet you write. Write a Tweet, record that Tweet. You don’t have to record your Tweets to participate.

Accessible Twitter

This might be a good time to try Dennis Lembree’s Twitter site, and to Tweet about the experience.

How We’ll Use Your Tweets

We will use the Tweets/audio in our #csun10 presentation. We’ll present the Tweets on screen and hear the words – something for everyone. We’ll be looking for patterns such as the use of desktop applications with ZoomText, or mobile text with Talks, or mobile app with VoiceOver. These patterns will be touch-points for our presentation.


The hashtag for these Tweets will be #csun10s with the s representing story.

When Do I Start?

The days/dates we’ll be collecting Tweets and audio are Friday, February 26 – Saturday, February 27 in the northern hemisphere; Saturday, February 27 – Sunday, February 28 in the southern hemisphere.

Be Creative!

Feel free to be creative, to have fun, to be serious, to be furious, to be whoever you are. You know you want to do it!


Dennis Lembree @dennisl
Joseph Karr O’Connor @blacktelephone

For same info also see Webaxe blog.

Against Common Sense

Go, John, Go!


John, you are making great progress, keep up the good work!

I’m providing leadership for a large university Web effort. I just can’t imagine putting HTML5 before our people and stating that alt is optional and summary is obsolete (no one will even see conformant; they’ll stop at obsolete).

It goes against common sense, and our people are blessed with an abundance of that. These are very smart people we’re talking about. They pay close attention to details, and they want to do things the right way.

Real World Challenges

Just today we had a faculty member call us to tell us that the LIFT text transcoder wasn’t working properly. She had ALL-TEXT PAGES. It took a great effort to convince her that LIFT wasn’t needed for all-text pages, they pass already. She was trying to conform to the letter of the law and provide a text alternative for every page. These are the people to whom we CANNOT give a spec in which alt is optional and summary is obsolete. End of story.

I know that we should provide training. We do and two people show up. I know that we should have Web resources. We do but no one has time to read. We should have more hours in the day, but due to the state budget crisis, we’re on furlough 24 days this year. In weeks with furlough days in them we are restricted to 32 hours of work, period, the end. I’m not working now at 11:30 at night because this is my own personal blog, but I have work piled up like cord wood that isn’t getting done right now and that includes getting around to all 4,000 faculty, staff and administrators to see how they’re doing with our Web template system, XHTML 1.0 Transitional, and Section 508. Not going to happen, is it?

Common Sense

So when HTML5 is ready for primetime I hope that it follows WCAG 2.0 and common sense, or we won’t be able to use it.

For Fun And For Free

I am writing this on behalf of Accessible Twitter and Dennis Lembree.

In The Beginning

I was consulting at Cornell University in 1991 when I saw the first Web pages on a NeXT computer. The first pages were rather accessible but there wasn’t any assistive technology on the NeXT computer at that time. JAWS for DOS was originally released in 1989 by Ted Henter but as far as I know it never existed for NeXT.

Though Tim Berners-Lee is supposed to have said that he never intended for pictures to be displayed on the Web, in 1992 he apparently went out of his way to load this first Web picture.

Uploading that picture brought on the beginning of inaccessible Web design. People merrily went about “designing” pages filled with pictures with no alternative text. Pages with black backgrounds, yellow slanty text, and the tiled rings of Saturn. It was mostly academics, scientists, military people who had accounts. The Web grew out of their sensibilities.

A very common sensibility on the early Internet that carried over to the early Web was that it was for fun and for free. The people who regularly used the Internet back then might not have described their modality as for fun and for free but they sure lived it. I remember incendiary flame wars over the very mention of a commercial product in a Usenet newsgroup discussion. Contrast that with Blackboard claiming they own a patent to deliver courses over the Web. Sheesh.

Tim Berners-Lee himself did not patent the Web. While CERN was certainly a very serious enterprise, you could easily say that he gave the world the Web for fun and for free. Think about that for a second or two. This enormous economic development engine that is the Web was given to us for fun and for free. Wow!

Big AOL Bang

Now I come to the Big AOL Bang. When all those AOL pukes were set loose on the raw wild Internet in 1995 they destroyed it. They went right to GeoCities, also vintage 1995, and made pages that look like this.

Sorry Ms. Hagen. I do really love your music though. I even have your vinyl! Vinyl? Well, records used to be relea… Records? Well records were…

Alright, so that page isn’t on GeoCities… but it should be. And what’s up with 1995 anyway? OMG!

From the beginning of the Web I was called on to “make a Web page” for places I worked, or lived, or friends, or politicians, or artists. I made Web pages. I tried to make plain pages with logical navigation. I was admonished. The client wanted black backgrounds with yellow slanty text, animated gif sparkle ponies, and a picture of their cat. And that was for a course syllabus. Of course.

Section 508 Saves The Day

In the USA in August 1998, Section 508 of the Rehabilitation Act was signed into law tasking the General Services Administration with providing technical assistance concerning the requirements of the law. Accessibility was now mandated by law, and it was good. And order was imposed on the Web. NOT!

As recently as this past week, on July 29th, 2009, the NFB – National Federation of the Blind – gave the online retailer some recognition. “The NFB’s Gold Level Certification is awarded in recognition of commitment and innovation to help ensure equal Web access to the visually impaired individuals.” The ironic thing is that I read the press release on a page without a skipnav or headings, with endless navigation and inline CSS; in short a rather inaccessible page.

Let’s review: 508 goes into effect 10 years ago. 10 years later, the NFB finds it necessary to note that an online retailer is doing something about accessibility. Boy oh boy.

I haven’t done extensive accessibility testing of, but here’s the first text (hidden) at the top of the mainpage: “If you are visually impaired and are having difficulty navigating this site, please call our Customer Support line.” Hmmm… I’m confused, if I can’t see the invisible text I should raise my hand? Of course!

What they are doing of course is putting that text there for those with screen readers, a vital but small portion of those with disabilities. They’re trying, but probably doesn’t get the whole picture.

They should read this article titled Don’t Just Tick Boxes.

Accessible Twitter

Now, after a lengthy digression in which I partly laid out the history of the inaccessible Web, added in the Big AOL Bang, took a potshot at Nina Hagen, and poked in the eye (Doh!) I come to Dennis Lembree and his remarkable construction of Accessible Twitter.

I believe that there are others involved in creating and maintaining and upgrading and generally futzing with Accessible Twitter. Dennis is to be lauded, as is anyone else who is contributing including:

Dennis has poured what looks to be his every waking moment into Accessible Twitter. And it is truly accessible. I can even navigate with the keyboard. I get an audio cue when I’ve reached milestones in my character count. It is semantic, and there are proper headings.

Oh, about that audio cue. Erm… do NOT leave your speakers turned up most of the way when using Accessible Twitter. Makes me jump every time I hear “30 characters” loudly proclaimed. You’ll want to wear headphones if anyone else is trying to sleep.

Dennis Lembree is a pioneer, a magician, a dedicated soul who is the heart of the real Internet, the Internet I have come to love so much. The Internet that helped me for free when my daughter was born with severe disabilities in 1992. The Internet that freely helped me heal a RAID array on Christmas Eve 1997 so our thesis students could resume their work. The Internet of thoughtful individuals giving their time for fun and for free so that others may benefit, thoughtful individuals like Tim Berners-Lee. That’s who Dennis is. And that’s why he deserves our support, because he’s giving it away, for fun and for free, expressing love one Tweet at a time.

You might also want to read Accessible Twitter: how it should have been done to start with.


XHTML vs. HTML 5 vs. Accessibility

From the W3C news archive for 2 July 2009:

XHTML 2 Working Group Expected to Stop Work End of 2009, W3C to Increase Resources on HTML 5
2009-07-02: Today the Director announces that when the XHTML 2 Working Group charter expires as scheduled at the end of 2009, the charter will not be renewed. By doing so, and by increasing resources in the Working Group, W3C hopes to accelerate the progress of HTML 5 and clarify W3C’s position regarding the future of HTML. A FAQ answers questions about the future of deliverables of the XHTML 2 Working Group, and the status of various discussions related to HTML. Learn more about the HTML Activity. (Permalink)

In terms of accessiblity, I believe that HTML 5 will do damage to our goals. However, HTML 5 won’t be widely adopted at first. Since there are some things about HTML 5 that baffle me this is a good thing. Since most Websites must be as compatible as possible we will continue using XHTML, probably for years to come. This will give us a chance to see if HTML 5 goes anywhere. It all comes back to supporting the functionality that we require to convey our messages in as accessible and usable a way as possible. At work at a large university we have a guideline we try to follow: current version minus 1. This keeps us from leaping on technologies before they are proven. When a reasonable percentage of Web materials are HTML 5 and we want the functions that HTML 5 provides, then we’ll think about moving to it. For now, XHTML provides us with a stable platform on which we can provide functional accessibility and usability for all.