Planet-Accessibility

From Space Daily, Tokyo (AFP), 26 August 2009 Robotics and medical experts in Japan on Wednesday unveiled the prototype of a new hi-tech electric wheelchair that resembles a scooter and promises greater mobility. Users ride astride the four-wheeled Rodem—rather than sitting in it, as in a conventional wheelchair—steer it with a joystick and hold onto motorbike-style handles [...]

It can be a tough job to check out that your system is fully compatible with a new operating system before you install it. To help out assistive technology users, I’m compiling compatibility information for assistive technology and AT-related software.

I’ll be updating this post as new information is available, so come back and look again. If you have information that isn’t here, leave a comment or contact me and I’ll add it to the post.

General Assistive Technology Software

MacSpeech Dictate - Not functional with Snow Leopard. There are no known workarounds at this time, and no information about when an update will be available and if it will be free or paid.

KeyStrokes - Current version has been tested and is fully compatible with Snow Leopard.

SwitchXS - Current version has been tested and is fully compatible with Snow Leopard.

TouchStrokes - Current version has been tested and is fully compatible with Snow Leopard.

Layout Kitchen - Current version has been tested and is fully compatible with Snow Leopard.

VisioVoice - Version 1.2 has been tested and is fully compatible with Snow Leopard.

Proloquo - Current version has been tested and is fully compatible with Snow Leopard.

SmartNav - No information is available at this time. I have requested compatibility information from the company and will update as soon as there is news.

CrossScanner - No information is available at this time. I have requested compatibility information from the company and will update as soon as there is news.

SmartClick - No information is available at this time. I have requested compatibility information from the company and will update as soon as there is news.

MagicCursor OS X - No information is available at this time. I have requested compatibility information from the company and will update as soon as there is news.

Discover Envoy - No information is available at this time. I have requested compatibility information from the company and will update as soon as there is news.

Envoy Create - No information is available at this time. I have requested compatibility information from the company and will update as soon as there is news.

VirtualKeyboard No information is available at this time. I have requested compatibility information from the company and will update as soon as there is news.

Third Party System Voices

Note: Due to changes in the depths of Snow Leopard, it is highly unlikely that any third party voices will function without upgrades.

InfoVox iVox voices - Current version does not work with Snow Leopard. Version 2.0 will soon be released to public beta and will fully compatible with Snow Leopard although without the older “HD” quality voices. Version 2.0 will be a free upgrade for existing users.

Cepstral voices - Official word from the company is “The Cepstral voices have not yet been certified with Snow Leopard. We are working through some porting issues at this time. An update will be announced soon, but it’s not available for Beta yet.” It appears that “not yet certified” is a code phrase meaning “does not work”.

Text Expansion Software

TextExpander - The current version, 2.7 has been tested and is fully compatible with Snow Leopard.

TypeIt4Me - Version 4.1.2 and above have been tested and are fully compatible with Snow Leopard.

Typinator - The current version has been tested and is fully compatible with Snow Leopard.

OCR Software

Abbyy FineReader - [Added 29 August, 1:50am] Abbyy have advised me “our testing shows that ABBYY FineReader Express Edition for Mac can work under this OS correctly except for some non-critical issues which are going to fixed in future releases of the program.” I have requested clarification of these “non-critital issues” and whether releases to fix them will be free upgrades.

ReadIris Pro - The current version is ReadIris Pro 11 which has not been tested with Snow Leopard. ReadIris Pro 12, to be released in September, will be fully Snow Leopard compatible but a paid upgrade with prices probably comparable to current prices, which are US$129 for USA buyers and significantly higher for the rest of the world.

Other

Other software that’s commonly used in assistive/adaptive technology contexts.

KeyCue - Version 4.5 above have been tested and are fully compatible with Snow Leopard.

1Password - Current version of 1Password is 2.*, version 3.* will be needed for Snow Leopard (further technical information about 1Password and Snow Leopard). Version 3 is currently in beta testing, with the test version available for all Snow Leopard users. 1Password version 3 will be a paid upgrade unless you bought version 2 during 2009, the price is not yet decided.

EyeTV - The current version 3.1.2 is expected to be fully compatible with Snow Leopard, but this is not final information. See the EyeTV Forums for full details.

PhoneValet Home - A free upgrade will be required for Snow Leopard compatibility. Parliant advised us this should be available “within a few days” of Snow Leopard’s release.

PhoneValet Message Center - The current version 6.0.2 works with Snow Leopard on all machines except XServes. A free update for XServes will be issued shortly - if you don’t know what this means then you don’t have an XServe.

Growl - Several things in the current version of Growl don’t work under Snow Leopard. The Growl development team are hard at work to finish the version 1.2 update which will be fully Snow Leopard compatible, and hope to have it available by Friday (further details about Growl upgrade).

Other Information Sources

The two places with great compilations of information at the moment are:

• Wikidot Snow Leopard Compatibility List
• MacWorld Snow Leopard Compatibility List

Both of these documents are Wiki based so they can be edited by any user with new information. If you test something and it’s not on the lists, add the information so others can look it up!

Which of your essential programs have I missed, and do you know if they’re compatible with Snow Leopard? I’ll be updating this post as new information is available, so come back and look again.

- Ricky Buchanan

Share this

Do you know somebody else who would find this interesting or useful? Please forward it to them. Did somebody forward this post to you? Visit http://atmac.org/ and subscribe to receive posts for free.

Snow Leopard Assistive Technology Compatibility List

           

Related posts:

• Snow Leopard is Coming, Are You Ready Or Not?
• Accessibility for Snow Leopard
• Snow Leopard, Above and Beyond

Guest post by Alex Jurgensen.

Apple once said that you could “Live the digital life in stylish simplicity.” They were talking about the Mac Mini, but this statement could easily encompass all of Apple’s products. Apple is known for making products that are powerful and customer friendly, but what kind of accessibility can be expected from a modern mainstream technology company? What does all this talk about fancy Apple products mean for the average end user? Moreover, what does this mean for the end user with a visual impairment?

Apple has always had products with innovations that most assistive technologies traditionally seem to have found hard to support. Trends in assistive technology would tend to indicate that no support can be expected for such advanced technologies, but Apple is not a company which often follows trends set by others.

In June of this year Apple unveiled some of their plans for iPhone and iPod Touch operating system 3.0 and the new iPhone 3GS. The blind community had been bracing for the worst; version 2.0 of the iPhone operating system had offered some limited accessibility for those with low vision but no screen reader. To everybody’s amazement, Apple announced that iPhone OS 3.0 running on the new hardware, iPhone 3GS, would include support for a built-in screen reader. Prior to this announcement, it was “common sense” that any touch screen device was inaccessible to blind users and nobody expected this to change.

The screen reader, called VoiceOver allows blind and visually impaired individuals to use the touch-screen interface of iPhone like any sighted person would. When a finger is placed on-screen, the item below the finger is read. VoiceOver also supports Flick Navigation, which allows users to find icons even if they don’t know where they are on-screen. Probably the nicest feature of VoiceOver on iPhone is the Rotor. This gesture, which resembles turning a dial on a radio, allows people to select the mode in which to navigate. When on web pages, this allows users to jump quickly through headings, links and other elements.

And as if the new and shiny iPhone with VoiceOver wasn’t enough, Apple releases Snow Leopard today. The operating system that Apple calls “the world’s most advanced operating system, finely tuned,” has redefined Universal Access. Before we look at some of the new features, let’s look at some history at how Apple came to where it is now.

In the late 1980s, back in the days of the “Classic Mac”, Berkley Systems had developed a screen reader for the Mac called outSPOKEN. This screen reader was excellent for its time but was third party software, not integrated with MacOS itself. When OS X was introduced, outSPOKEN became obsolete as the operating system itself had changed too much. It was never made functional on OS X, and no other screen readers were developed to fit the space.

In 2004, Apple debuted an OS X application called Spoken Interface that allowed blind and visually impaired individuals to hear descriptions of what was on the screen. This step is now almost forgotten, but it marked a critical turning point in Apple’s attitude toward the visually impaired community.

In April of 2005, Apple truly began its journey to become one of the best known universal access names in the mainstream market place. Their operating system Mac OS X 10.4, commonly known as Tiger, shipped with a built-in screen reader called VoiceOver, a large text screen magnifier called Zoom and numerous other accessibility features for hearing impaired and physically disabled users.

Though Tiger’s screen reader was not deemed appropriate for production environments by many of those who worked in the business of technology consulting for the visually impaired, it still was a topic that gave hope to those in the blind community. It stirred up much controversy as to which direction Apple was heading in regards to its commitment to accessibility. While some members of the visually impaired community argued that Apple was attempting to be all inclusive and break down barriers between the visually impaired and sighted communities, there were those who claimed that Apple only sought to meet the American 508 legislation and would go no further than the minimum requirements of the law. Despite these mixed feelings, Tiger adoption by members of the blind community increased at a slow but steady rate.

In October of 2007, Apple released a major update to their desktop and server operating systems. This release, Mac OS X 10.5, known as Leopard, held even more surprises in store for the visually impaired community. VoiceOver, had received a major update and was now ready for production use, putting it on equal footing with screen readers such as JAWS. VoiceOver was now shipped localized in eight languages and included support for about twenty refreshable USB Braille displays, and the visually impaired community saw a large jump in the number of Mac users.

Apple’s accessibility team dove head first into the iPod market with an unusual angle. At Apple’s “Let’s Rock” Event, on September 09, 2008, Apple revealed an iPod like none before. The iPod Nano G4 included spoken menus that could easily be accessed by all users. This was followed by the porting of the VoiceOver technology to the iPod Shuffle 3G in January of 2009. In both instances Apple advertised VoiceOver as a feature that had a benefit to all, not merely those who are visually impaired or blind. Sighted runners could now check album and artist data while on the run, drivers could operate their iPods safely while driving. This placed a big shift on how people viewed text to speech and Universal Access in general on OS X.

And tomorrow Apple releases Snow Leopard, an operating system that, as far as blind and visually impaired community is concerned, is more than “finely tuned.” Apple has yet again surprised the market with something unexpected, but this time it is something most people never dreamed possible. Through VoiceOver, the mouse has been marginally usable for those with visual impairments since Tiger, but totally blind people often found the feature to be more of a hinderance than a help.

Snow Leopard strove to change all that and the brilliant minds at Apple’s accessibility team have pulled it off yet again. The same technology used for VoiceOver on the iPhone 3GS, is now used in MacBooks with multi-touch trackpads to provide a “feelable” view of what is on-screen. Using gestures nearly identical to those on iPhone, blind and visually impaired users can access on-screen elements easily and effectively.

It seems that Apple has now removed all limits the blind and visually impaired face when using graphical environment. This lays to rest a fear that stretches back to the introduction of the graphical user interface and brings new possibilities to what the visually impaired community can achieve on their Macs.

Apple’s road is long, but it is one they have chosen and they strive to meet to the 110% mark. It is an accessibility model that the visually impaired community has come to embrace, and one that has removed boundaries in more ways than one.

Personally, I applaud Apple for their efforts and will be picking up a Snow Leopard family pack as soon as it becomes available here in Canada. Snow Leopard is now available for order through the Apple online stores and other authorised Apple retailers. It retails at an upgrade price of US$29 for a single license and US$49 for a five user family license.

I’ll be going into the Apple store with high hopes for this new operating system. What is your feeling toward this historic release? What issues that were present in Leopard do you most wish to see addressed?

- Alex Jurgensen

Share this

Do you know somebody else who would find this interesting or useful? Please forward it to them. Did somebody forward this post to you? Visit http://atmac.org/ and subscribe to receive posts for free.

Snow Leopard, Above and Beyond

           

Related posts:

• Accessibility for Snow Leopard
• Snow Leopard is Coming, Are You Ready Or Not?
• MacWorld Podcast Features VoiceOver and Accessibility

I’m happy to say that this project is finally coming together.  My latest version is my August 19 WCAG 2.0 chart, which is viewable in Word 2007 or the Word Viewer.

Why do I say it’s finally coming together?  Because it’s shaping up to be the stepping stones for a flowchart or decision tree that can make it easy for developers who have to just pick up WCAG 2.0 and implement it.  Of course, it’s no where near that stage yet, but it’s getting there.

Interesting to see accessibility APIs becoming available for mobile phones. If you are a developer for either of the major platforms you now have the ability to include accessibility information for your user interface.

iPhone Accessibility API

Blackberry Accessibility API

Only yesterday, we were saying that we didn’t know when the call for proposals would be out for STC’s Technical Communication Summit 2010 set in Dallas, Texas, 2–5 May 2010 (at the Hyatt Regency Dallas at Reunion.) Today, we are pleased to announce that the STC 2010 Summit Call for Proposals is now open. Go ahead and [...]

No matter what your political affiliation, we all owe Senator Edward Kennedy a lot.  A few minutes ago, a news flash came across my computer that Ted Kennedy had just passed away.  My wife (Laura Ruby) and I were shocked… Ted has been such an icon in the work we’ve both been doing for the last 20 years.  It seems so sad and ironic that just tomorrow, the Disability Rights Education and Defense Fund (DREDF)— the first outside group I met when I joined the Justice Department— was going to be having a gala to celebrate his accomplishments.

When I joined the Justice Department back in 1992 (when the ADA first came into effect), Senators Kennedy and Harkins stood out as the two demigods who made the ADA possible.  It wasn’t until years later that I understood how important Senator Kennedy’s lifelong fight for civil rights was for creating the legal infrastructure that ultimately created the disability rights framework that we all rely on every day.  Without that framework of basic disability rights laws, IT accessibility would be just a distant pipedream.

As we all go through our day today, let’s all keep thoughts of praise in our hearts for a bold pioneer.  Senator Kennedy was not the first person many of us might think about for technology accessibility but, without him, our world would be a far worse place.

A few months back, Thomas reported on a cool flumotion experiment that he hacked together which allows jumping back in time on a live video stream.

Thomas used a URI scheme with a negative offset to do the jumping back on the http stream:
http://localhost:8800?offset=-120

John left a comment pointing to current work being done in the W3C on Media Fragment addressing, but had to notice that despite Annodex’s temporal URIs having a live stream addressing feature, the new W3C draft didn’t accommodate such a use case.

We got to work in the working group and I am very happy to announce that as of today there is now a draft specification for addressing time offsets by wall-clock time.

Say, you are watching Thomas’ live stream from above at http://localhost:8800 and you want to jump back by 2 min. Your player would grab the current streaming time, e.g. 2009-08-26T12:34:04Z and subtract the two minutes, giving 2009-08-26T12:32:04Z. Then the player would use this to tell your streaming server to jump back by two minutes using this URL:
http://localhost:8800#t=clock:2009-08-26T12:32:04Z.

Or another example would be: you had a stream running all day from a conference and you want to go back to a particular session. You know that it was between 10am and 11am German time (UTC+2 right now). Then your URL would be as follows:
http://conference:8800#t=clock:2009-08-26T10:00+02:00,2009-08-26T11:00+02:00

Now if only there was an implementation…

With all the open calls for papers for various conferences, it is easier to blog about them than to tweet about them. Why the call for papers? Conferences are excellent opportunities to exchange knowledge with your peers. It’s never too early or too late to share. Some even provide special student opportunities to encourage the new generation. Think [...]

Yesterday was the third Drupal 7 accessibility taskforce meeting, and the final meeting before code freeze. With September 1 just around the corner the Drupal accessibility community would like to reach out the the broader community for some additional help during this busy time to get as many accessibility improvements into Drupal 7 core as possible.

There are many ways to help and to get involved. If anyone is wondering what they can do or how their skills may be useful please e-mail Everett to find out where your skills can best be put to use.

There are five issues that we would like to request assistance with. They are listed below with links to their issue page.

1. Form element labeling is inconsistent, inflexible and bad for accessibility (558928)
2. Local tasks lack semantic markup to indicate an active task (521852)
3. Link to expand / collapse fieldsets has poorly accessible link text (541568)
4. Accessibility improvements for vertical tabs (467296)
5. Drag and Drop for table rows is not accessible to screen-reader users (448292)

Thank you so much to everyone who has contributed to Drupal accessibility thus far, and thanks in advance for those who can find the time to contribute over the next week.

Apple has announced that the upgraded Snow Leopard operating system (OS X 10.6) will be available from this Friday, 28 August 2009.

Upgrading to Snow Leopard might not make your computer look a lot different, but the hidden guts of the operating system have been extensively worked on. This has big implications for assistive technology users - you’ll need to carefully check that your assistive technology will work with Snow Leopard before you upgrade.

For those using assistive technology hardware, if it came with no drivers or programs needed then it should work under Snow Leopard with no problems. “Smaller” types of assistive technology such as ergonomic keyboards, large trackballs, etc., tend to be in this category. If your assistive technology program came with a driver, an application, a system preference pane, or anything else you had to install from a CD or download from the internet, you’ll need to check the software first.

For those using software-based assistive technology such as on-screen keyboards, upgraded voice software, etc., you should check with the software company before you upgrade to Snow Leopard. It’s quite possible that your software will stop working if it’s not compatible with Snow Leopard!

For companies who write this software, most were guessing that Snow Leopard would be released at the end of September. Like us, they only found out last week that Snow Leopard is to be released on Friday. This means that many companies whose software will need upgrading thought they probably had another 6 weeks to finish their programming, and suddenly found out they only had a week. As you can imagine, this has left many scrambling to catch up.

We already have an announcement from AssistiveWare that the current Infovox iVox voices, version 1.3, will not function with Snow Leopard. David Niemeijer, told ATMac today:

Infovox iVox 2.0 will be required [for Snow Leopard]. Infovox iVox 2.0 required a complete rewrite of the core engine to make it compatible with Snow Leopard. Despite the many months of development work Acapela Group put in to it, Infovox iVox 2.0 will be offered as a free update for Infovox iVox 1.x users to support those users who rely on Infovox iVox to use their computer.

Because of the amount of work involved we do not have a final release for Infovox iVox 2.0 ready yet. Instead, if our current tests are positive we will make Infovox iVox 2.0 available as a public beta by Friday, 28 August. If you rely on Infovox iVox do not upgrade to Snow Leopard until you have upgraded to Infovox iVox 2.0.

Kudos to David for stepping up and offering a public beta for those of us that like to upgrade things quickly.

There is an additional note for InfoVox iVox users who are using the older HD voices:

The change to support 64 bit technology made it impossible to retain the HD voices in Infovox iVox 2.0. For most languages HQ voices are available (several new ones are included in Infovox iVox 2.0). Only Icelandic had to be completely dropped in Infovox iVox 2.0 because there are no HQ voices for that language.

If you aren’t sure if the voice you are using is HQ or HD, open System Preferences and open the Speech pane, then the Text to Speech tab. This is the same tab you open to change the default system voice. Your current system voice is displayed in the drop-down right at the top of the pane, and if you’re using an Infovox iVox voice it will have “HQ” or “HD” at the end of the name. If you click on the box, you can see the other voices you have available and for all the iVox ones the “HD” or “HQ”.

David has told me that there are no known problems with any other AssistiveWare products and Snow Leopard, so users of KeyStrokes, TouchStrokes, LayoutKitchen, SwitchXS, and Proloquo should have no problems. VisioVoice should work fine with Snow Leopard, but an upgrade to VisioVoice 1.2 is expected in time for Snow Leopard too and will be needed for Infovox iVox 2.0 voices.

I don’t have information from any other assistive technology companies about the compatibility of their software yet. I’m trying to compile information on the Snow Leopard compatibility of other OS X based assistive software, and will publish it as soon as possible. If you know about any bits of software, or have a particular piece of assistive tech you’re curious about, please leave a comment or contact me with the information.

- Ricky Buchanan

Share this

Do you know somebody else who would find this interesting or useful? Please forward it to them. Did somebody forward this post to you? Visit http://atmac.org/ and subscribe to receive posts for free.

Snow Leopard is Coming, Are You Ready Or Not?

           

Related posts:

• Accessibility for Snow Leopard
• Leopard: 17 Universal Access Features or more
• Infovox iVox 1.2 adds new voices and a pronunciation editor

NVDA is a screen reader offered by NV Access, an Australian non-profit organization. NVDA is open-source and free for users to download and use.

All users encounter Flash-based content and PDF documents regularly, and Adobe wants NVDA users to have a positive experience. Therefore, Adobe is funding NVAccess to help address the goals to "Improve support for Adobe Reader" and "Add support for Adobe Flash embedded in Browsers. This work will benefit not only Flash and PDF, but also help users access content and applications developed with Adobe Flex and interactive forms developed with Adobe LiveCycle.

NVDA developers have already done some work to enhance access to PDF in the current release. We're looking forward to additional improvements progress that will surely be made in the coming months!

We are pleased and grateful to announce that  Adobe have provided a grant to  NV Access to support NVDA development. This grant will enable us to improve support for Adobe Reader and add support for Adobe flash embedded in browsers. This is great news for NVDA users given the increasing regularity of PDF documents and Flash content. This will also help users access content and applications developed with Adobe Flex and interactive forms developed with Adobe LiveCycle.

We've already done much of the work to improve support for Adobe Reader. You can try it out for yourself in NVDA development snapshots.

For a long time, I’ve been an advocate of using whenever possible and generally shunning the use of title attributes whenever I could use a label.  I felt this way especially about forms buried in HTML tables.  In fact, back in 2001 when Doug Wakefield and I were running through the testing that developed in the Access Board’s Guidance on HTML Forms, we told developers to always use explicit labels when putting forms into tables.

This week, I worked on a project that changed my mind.  It’s no secret that I’m under contract to create a simple online tool that enables IT companies to quickly create and edit VPATs in XML format.  The form, however, needs to look like a tabular VPAT because, quite frankly, that’s what people are used to seeing and its the format we’ve used for almost 10 years now.  I knew that headers and ID were great for making tables accessible, but screen readers want something actually tied to the form element.  Problem is that location in a VPAT table is meaningful— it is much more than a layout table.

The solution, of course, was to use the title attribute even where I would have once people to use  only.  Even basic and tags got the title treatment to basically provide the same information that location within a VPAT table would provide to a visual user.  It was a humbling moment indeed.</p> <p>This isn’t a new suggestion, as <a href="http://accessibilitytips.com/2008/03/25/using-titles-on-form-fields/">others have made the same recommendation</a>.  It’s also part of the WCAG 2.0 techniques (<a href="http://www.w3.org/TR/WCAG20-TECHS/H65.html">H65: Using the title attribute to identify form controls when the label element cannot be used</a>).  But it does still irk me that my old HTML 4 book doesn’t say anything about these elements including the title attribute even though JAWS picks it up fine.</p> <p>BTW, about the VPAT XML online tool.  Details will be available once it’s officially posted, but the version I’ve brewed up works great right now.</p> <div class="comments"><a target="blank" href="http://www.accessibilitywatch.com/?p=175">Click here to comment on this article</a></div> </div> </div> <div class="single_post"> <div class="title_date"> <p class="days">21</p> <p class="month">Aug</p> </div> <div class="title"> <h4>Fallback</h4> <h4 id="blogname" name="All Sorts of Things">Source: <a href="http://allsortsofshrink.blogspot.com">All Sorts of Things</a> </h4> </div> <span class="footnote"> Written by: <a href="http://allsortsofshrink.blogspot.com/2009/08/fallback.html" target="_blank">$hRiNk</a> on Fri, 21 Aug 2009 14:26:00 -0500 </span> <div class="post_content">Rahul (<a href="http://mether.wordpress.com">mether</a>) Sundaram proposed this idea of a <a href="https://fedoraproject.org/wiki/Remixes_Web_Interface">web-application</a> to make Fedora <a href="https://fedoraproject.org/wiki/Remix">remixes</a>/spins.<br /><br />I had decided to implement it using Ruby on Rails (surprising?).<br /><br />I had already parsed the <a href="http://cvs.fedoraproject.org/viewvc/comps/comps-f11.xml.in?view=markup">comps</a> into a MySQL database schema. I then filed <a href="https://fedorahosted.org/design-team/ticket/67#preview">a ticket</a> to the Fedora Design Team for a mock-up UI. I am still waiting for a response on this.<br /><br />The name of the application is yet to be decided.<br /><br />The next hurdle is to parse/build <a href="http://fedoraproject.org/wiki/Anaconda/Kickstart">kickstart</a> files. There are two ways of doing that:<br /><br /><ol><li>Writing my own kickstart parser in Ruby.</li><li>Using the already existing and extensively used <a href="https://fedoraproject.org/wiki/PykickstartIntro">pykickstart</a> - a Python library for manipulating kickstart files.<br /></li></ol>While the fate of the project was already decided at this point, I decided to give it another shot by asking around in the <a href="https://www.redhat.com/archives/kickstart-list/2009-August/msg00044.html">kickstart-list</a>.<br /><br />Well now its final. The web application would be developed using Django.<br /><br />Hence I would not only be able to use pykickstart and thus avoid writing a parser from scratch, but I would also be able to integrate the application with <a href="https://fedorahosted.org/releases/p/y/python-fedora/doc/django.html#fedora-django-auth">FAS</a>.<br /><br />P.S. - This is the second time a missing or poorly written Ruby parser has let me down. While I am all for the far-more-superior framework of Ruby on Rails when building web-apps, I can't help but admire the advantage Django has when it comes to integration with existing and awesome Python libraries that do cool stuff.<div><img width="1" height="1" src="https://blogger.googleusercontent.com/tracker/974409201910540496-5158257479602443323?l=allsortsofshrink.blogspot.com" /></div> <div class="comments"><a target="blank" href="http://allsortsofshrink.blogspot.com/2009/08/fallback.html">Click here to comment on this article</a></div> </div> </div> <div class="single_post"> <div class="title_date"> <p class="days">21</p> <p class="month">Aug</p> </div> <div class="title"> <h4>Adobe Flex continues to drag feet, still not accessible by default</h4> <h4 id="blogname" name="AccessibilityWATCH">Source: <a href="http://www.accessibilitywatch.com/">AccessibilityWATCH</a> </h4> </div> <span class="footnote"> Written by: <a href="http://www.accessibilitywatch.com/?p=173" target="_blank">Thomas Logan</a> on Fri, 21 Aug 2009 09:35:26 -0500 </span> <div class="post_content"><p>Adobe has done good work to help automatically determine accessibility information and expose it to assistive technologies. Unfortunately, because the feature is not turned on by default many sites that would benefit are left completely inaccessible. </p> <p>I have been watching this <a href="http://bugs.adobe.com/jira/browse/SDK-20526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel">Flex accessibility issue</a> for quite some time now. Today I received a notification that the item has been “deferred” which means for the time being Adobe Flex will continue being inaccessible by default. I don’t know any other technology that has made this choice. </p> <p>For those of you reading that want to know how to turn accessibility on see this <a href="http://www.adobe.com/accessibility/products/flex/components.html">Flex documentation</a>.</p> <div class="comments"><a target="blank" href="http://www.accessibilitywatch.com/?p=173">Click here to comment on this article</a></div> </div> </div> <div class="single_post"> <div class="title_date"> <p class="days">21</p> <p class="month">Aug</p> </div> <div class="title"> <h4>ARIA – A Brief Introduction</h4> <h4 id="blogname" name="Silvia Pfeiffer">Source: <a href="http://blog.gingertech.net/category/video-accessibility/">Silvia Pfeiffer</a> </h4> </div> <span class="footnote"> Written by: <a href="http://blog.gingertech.net/2009/08/21/aria-a-brief-introduction/" target="_blank">silvia</a> on Fri, 21 Aug 2009 07:19:52 -0500 </span> <div class="post_content"><p>Since working on video accessibility, I have felt rather inadequate not knowing exactly how general Web accessibility works, in particular ARIA. I have been pointed at the W3C WAI-ARIA <a href="http://www.w3.org/TR/wai-aria-primer/">primer</a>, <a href="http://www.w3.org/TR/wai-aria-practices/">best practices</a>, and <a href="http://www.w3.org/TR/wai-aria/">WD specification</a>, but found them almost impossible to read.</p> <p>If you are looking for a document that gets right to the point, I can recommend <a href="http://dev.opera.com/articles/view/introduction-to-wai-aria/">Opera’s Introduction to WAI ARIA</a>. It tells you what attributes there are and how to use them. More in-depth information is available in the W3C <a href="http://www.w3.org/TR/wai-aria-practices/">WAI-ARIA best practices</a>. Here’s my little summary of what I learnt.</p> <p>Getting straight to the point: ARIA mostly cares about giving screen control to the keyboard (away from the mouse) and about exposing semantic information, such that vision-impaired people have a way to interact with Web content and screen readers can read out useful information.</p> <p><strong>Basic keys</strong><br /> The basic keys in use for accessibility are the tab/shift+tab, arrow, enter, space and escape keys.</p> <p><strong>Keyboard Focus: tabbing</strong><br /> Normal tabbing includes form controls and anchors. This can be overruled with the <em>tabindex</em> attribute.</p> <p>Adding a tabindex=0 to an element adds the element to the tab order in which it appears in the document. Adding a tabindex out of [1;32767] you can place any element into a desired order – lowest numbers first.</p> <p>Adding a tabindex=-1 to an element removes it from tabbing order, but you can still get keyboard focus onto it through javascript, e.g. for the subelements of a menu. The aria-activedescendant attribute can tell which is active in a list of descendants.</p> <p><strong>Navigation Landmarks: roles</strong><br /> Screenreaders have a problem with expressing what the functionality of elements is – normally they can only read out the name of the element.</p> <p>This is where the <em>role</em> attribute comes in. It provides semantic meaning, e.g. “slider” instead of “input” element.</p> <p>ARIA has a large number of pre-defined roles. They are <a href="http://www.w3.org/TR/wai-aria/#roles">listed in the spec</a> – each role has additional attributes to provide more assistive information – mostly state information on the particular element.</p> <p><strong>Live updated content: aria-live</strong><br /> When data is updated somewhere on screen, often assistive technology doesn’t get to know about it.</p> <p>Regions that are marked with the aria-live attribute will be read out even if the user is focused on another part of the screen at that point.</p> <p><strong>Form input: aria-reqired</strong><br /> For screen readers it is not obvious if a form element’s entry is a required or optional entry. Add an aria-required attribute to the form entry element and your screen reader will tell you.</p> <p><strong>Labels and descriptions: aria-labelledby / aria-describedby</strong><br /> Most often the description or label for a page area sits already elsewhere on screen, but with no obivous relationship to an element other than visible neighbourship.</p> <p>A screenreader can be told about the relationship by using the aria-labelledby / aria-describedby attributes, which allow to link to such an area through that area’s id attribute.</p> <p><strong>Is that all?</strong><br /> Yes, I think that’s essentially all. It’s not particularly difficult, but it has a high impact on accessibility. I hope your take-away is as big as mine!</p> <p>BTW: WAI ARIA is written for good old HTML4, not HTML5. However, there are synchronisation activities under way and WAI ARIA attributes will still be relevant to HTML5. Some of the roles will become unnecessary with the new elements available in HTML5 – see a <a href="http://hsivonen.iki.fi/aria-html5/">draft mapping of HTML5 elements to ARIA implicit roles in Henry’s excellent document</a>, but it seems the tabbing order, live regions, and the role attribute are here to stay.</p> <div class="comments"><a target="blank" href="http://blog.gingertech.net/2009/08/21/aria-a-brief-introduction/">Click here to comment on this article</a></div> </div> </div> <div class="single_post"> <div class="title_date"> <p class="days">21</p> <p class="month">Aug</p> </div> <div class="title"> <h4>Tab Auto-Completion in Python Shell</h4> <h4 id="blogname" name="All Sorts of Things">Source: <a href="http://allsortsofshrink.blogspot.com">All Sorts of Things</a> </h4> </div> <span class="footnote"> Written by: <a href="http://allsortsofshrink.blogspot.com/2009/08/tab-auto-completion-in-python-shell.html" target="_blank">$hRiNk</a> on Fri, 21 Aug 2009 04:49:00 -0500 </span> <div class="post_content">Strangely enough, I discovered that I do not get bash-like auto-completion in my python interactive shell.<br /><br />Looking up helped.<br /><br />Just need to have a file called <span>.pythonrc</span> in your home directory containing the following:<br /><br /><pre><br />#!/usr/bin/python<br />import os<br />import sys<br /><br />try:<br /> import readline<br />except ImportError:<br /> print "Module readline not available."<br />else:<br /> import rlcompleter<br /> readline.parse_and_bind("tab: complete")<br /></pre><br /><br />Apparently, that was not enough. I also needed to add the following line to my .bashrc file (in my home directory again).<br /><br /><pre>export PYTHONSTARTUP=~/.pythonrc</pre><br /><br />That's all. Open a new shell and start the python shell.<br /><br />And enjoy auto-completion!<div><img width="1" height="1" src="https://blogger.googleusercontent.com/tracker/974409201910540496-957932714530995880?l=allsortsofshrink.blogspot.com" /></div> <div class="comments"><a target="blank" href="http://allsortsofshrink.blogspot.com/2009/08/tab-auto-completion-in-python-shell.html">Click here to comment on this article</a></div> </div> </div> <div class="single_post"> <div class="title_date"> <p class="days">21</p> <p class="month">Aug</p> </div> <div class="title"> <h4>Goodbye Miscellaneous Dependencies Package</h4> <h4 id="blogname" name="NVDA">Source: <a href="http://www.nvda-project.org/">NVDA</a> </h4> </div> <span class="footnote"> Written by: <a href="http://www.nvda-project.org/blog/GoodbyeMiscDeps" target="_blank">jteh</a> on Fri, 21 Aug 2009 01:00:31 -0500 </span> <div class="post_content"><p> NVDA has quite a few dependencies. Some of these have nice installers, but others are very small or aren't readily available in the form we need for some reason or another. Therefore, for people running from source, we previously bundled all of these dependencies into a single, convenient "miscellaneous dependencies" package. Unfortunately, this is rather tedious for us to maintain. Most of these dependencies rarely ever change, making updating the whole package for every change rather pointless. Therefore, the miscellaneous dependencies package is no more. Instead, dependencies.txt in the root of the code repository has been renamed to readme.txt and provides an in-depth description of all of the required dependencies, as well as instructions for preparing, running and building the source code. Pre-built versions of some of the dependencies are still provided where they are difficult to obtain or build, as described in the readme. Please let me know if I've missed anything! </p> <div class="comments"><a target="blank" href="http://www.nvda-project.org/blog/GoodbyeMiscDeps">Click here to comment on this article</a></div> </div> </div> <div class="single_post"> <div class="title_date"> <p class="days">20</p> <p class="month">Aug</p> </div> <div class="title"> <h4>Design for life part 1</h4> <h4 id="blogname" name="The 58 Sound">Source: <a href="http://58sound.com">The 58 Sound</a> </h4> </div> <span class="footnote"> Written by: <a href="http://58sound.com/2009/08/21/design-for-life-part-1/" target="_blank">David Sloan</a> on Thu, 20 Aug 2009 18:04:41 -0500 </span> <div class="post_content"><div><br /><p>One of the great things about my job as a researcher with a focus on accessibility and usability is that I can happily justify going all reflective on an everyday event, wondering why it happened, and what could be done to change it in the future – especially if it involves some user interface design quirk or flaw.</p> <p>That’s why earlier this year I found myself in the longest queue for the ticket machine outside the Prado gallery in Madrid, because I was curious to know why nobody seemed to be able to make it work (the answer was confusion caused by two user interfaces – one for selecting tickets, one for the credit card reader positioned below).</p> <p>Yesterday, I had to send someone a fax. I’d sent the same person a fax last week, and made the common mistake of sending the fax to a telephone number instead of using the fax number (there is a peculiar and specific embarrassment of hearing a disembodied voice try to answer the fax machine’s call while you can do nothing about it). I was so determined not to make the same mistake again…but I did.</p> <p>I can’t blame what I did on the fancy document-management machine we have in the office that supports printing, copying, scanning and faxing. So I looked at the document I was trying to send, on the second page of which was the fax number.</p> <p>This was the first problem – the destination fax number was on the document I wanted to send, and being too disorganised to write it down somewhere else, I had to quickly mentally note the number, type it into the machine, and put the document back in the slot ready for scanning.</p> <p>The second problem is the obvious one. Below the fax number was a phone number. Fax numbers are in an identical format to phone numbers (at least here in the UK), and most commonly will start with the same digits as a phone number: (0nnn) nnnnnn. Chances are the area code and first few digits will be identical for an organisation’s phone and fax number, which means without a distinguishing label it’s impossible to tell whether a number is a fax or phone number.</p> <p>So when the two are placed close to each other on a document – even when clearly labelled as ‘fax’ or ‘phone’, the chances of entering the wrong number are pretty high – and as I just proved, even when the consequences are known. Just like <a title="Derren Brown on Wikipedia" href="http://en.wikipedia.org/wiki/Derren_Brown">Derren Brown</a>’s TV ‘experiments’ where people  press a big red button despite (because of?) being told not to and being shown the consequences.</p> <p>OK, you’re probably wondering what my point is – we must have known about the problem of fax numbers for years, and aren’t faxes yesterday’s technology anyway? But in 2009, here I am, making the error – twice – so what could have stopped me?</p> <p><strong>The problem was the presence of two pieces of similar data</strong> – one important to the task, one irrelevant. The information design on the document was such that the two very similar numbers were physically close to each other. I didn’t need the phone number to send a fax, so it could have been somewhere else in the document, or not there at all (As it happens, there was also an email address beside the phone number, but I would bet very few people accidentally send faxes to an email address).</p> <p>It’s a simple information design lesson – think carefully about showing information that may hinder successful completion of a task. If it’s not essential, don’t show it, otherwise position it away from where the user’s focus will likely be.</p> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/58sound.wordpress.com/217/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/58sound.wordpress.com/217/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/58sound.wordpress.com/217/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/58sound.wordpress.com/217/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/58sound.wordpress.com/217/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/58sound.wordpress.com/217/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/58sound.wordpress.com/217/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/58sound.wordpress.com/217/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/58sound.wordpress.com/217/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/58sound.wordpress.com/217/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=58sound.com&blog=6581407&post=217&subd=58sound&ref=&feed=1" /></div> <div class="comments"><a target="blank" href="http://58sound.com/2009/08/21/design-for-life-part-1/">Click here to comment on this article</a></div> </div> </div> </div><div class="sidebar_left"> <div class="block"> <script src="http://www.planet-a11y.net/media/js/jquery/plugins/jquery.form.js" type="text/javascript"></script> <script src="http://www.planet-a11y.net/modules/search/js/liveSearch.js" type="text/javascript"></script> <form id="searchForm" class="liveSearchform" action='http://www.planet-a11y.net/' method='get'> <h5>Search:</h5> <input type="text" name="search" /> </form> <form action='http://www.planet-a11y.net/' method='get'> <div style="float:right;" id="buttonLink"> <a href='http://www.planet-a11y.net/?advanceSearch='>Advanced Search</a> </div> </form> </div> <div class="block"> <div class="title"><h2><span class="dark">Register Your Feed!</span></h2></div> <div class="text"> <form action='http://www.planet-a11y.net/?user=addRss' method='post'> Name:<br/><input type="text" name="phanetTitle" /> <br/><br/> Description:<br/><input type="text" name="phanetDesc" /> <br/><br/> Site Url:<br/><input type="text" name="phanetUrl" /> <br/><br/> Site Feed:<br/><input type="text" name="phanetRss" /> <br/><br/> Owner Nickname:<br /><input type="text" name="phanetNick" /> <br/><br/> Owner Fullname:<br/><input type="text" name="phanetFull" /> <br/><br/> Owner Email:<br/><input type="text" name="phanetEmail" /> <br/><br/> <input type="submit" name="phanetRssregister" value="Register" /> <br /> </form> </div> <div class="close"></div> </div> <script type="text/javascript" > $( document ).ready(function() { $("input:checkbox").click(function() { var check = $(this).attr("name") if ( !$(this).is(":checked") ) { $( "div#posts div.title" ).each(function(){ if ( $( "#blogname", this ).attr("name") == check ) { $( this.parentNode ).hide() } }) } else { $( "div#posts div.title" ).each(function(){ if ( $( "#blogname", this ).attr("name") == check ) { $( this.parentNode ).show() } }) } }); }); function enDisBlog( check ) { console.log( check.select ) //for ( a in check ) { //console.log( a ) //} $( "div#posts div.title" ).each(function(){ if ( $( "#blogname", this ).attr("name") == check.attr("name") ) { $( this.parentNode ).hide() } }) } </script> <div class="block"> <div class="title"><h2><span class="dark">Registered Blogs (47)</span></h2></div> <div class="text"> <ul id="blog"> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="" title=""></a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="" title=""></a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="" title=""></a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="5:55 AM" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://automorphic.blogspot.com" title="Sandy's a11y-tagged posts">5:55 AM</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Access Garage" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://accessgarage.wordpress.com/" title="">Access Garage</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Accessibility" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://blogs.adobe.com/accessibility/" title="Information and news about accessibility in Adobe products for people with disabilities, authors, and developers.">Accessibility</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Accessibility Tips" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.accessibilitytips.com/" title="Practical advice and guidance for building accessible websites">Accessibility Tips</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="AccessibilityWATCH" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.accessibilitywatch.com/" title="AccessibilityWatchâ„¢ is dedicated to providing the Web community with latest information on accessibility technology, news, solutions, tips and more. The AccessibilityWatch team has over 20 years of combined experience in Web accessibility. They are dedi">AccessibilityWATCH</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="All Sorts of Things" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://allsortsofshrink.blogspot.com" title="shrink's weblog">All Sorts of Things</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="ATMac" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://atmac.org/" title="Assistive Technology for Apple and Mac Users">ATMac</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Blog By Bryen (aka suseROCKs)" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.bryen.com" title="Rantings and Ravings">Blog By Bryen (aka suseROCKs)</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="decriptor" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.decriptor.com" title="Decriptor's Blog">decriptor</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="dotjay.co.uk" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://dotjay.co.uk/" title="web development and accessibility ramblings">dotjay.co.uk</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="FlaPer87" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.flaper87.org" title="import freedom; print everything">FlaPer87</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Gary Bishop" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://wwwx.cs.unc.edu/~gb/wp/blog/category/et/" title="Geeks making the world a bit better">Gary Bishop</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Hironobu Takagi" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://socialaccessibility.alphaworks.ibm.com/en/" title="Social Accessibility">Hironobu Takagi</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="iheni" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.iheni.com" title="iheni: making the web worldwide">iheni</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="isolani: web accessibility" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.isolani.co.uk/blog/access.html" title="Web accessibilility thoughts by Mike Davies">isolani: web accessibility</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Jantrid" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://blog.jantrid.net/" title="The musings and ramblings of Jamie Teh.">Jantrid</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Jim Thatcher" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://jimthatcher.com/news.htm" title="News @ Jimthatcher.com">Jim Thatcher</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="jpwhiting" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://jpwhiting.blogspot.com" title="my ramblings wrt accessibility especially in KDE">jpwhiting</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Juicy Studio" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://juicystudio.com" title="Best practice in web accessibility">Juicy Studio</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Marco Zehe" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.marcozehe.de/" title="Marco's accessibility blog">Marco Zehe</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Mario Carrion" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://blog.carrion.ws/" title="it’s gotta be smooth">Mario Carrion</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Mark Doffman" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://mark.doffman.com" title="Project maintainer - D-Bus Accessibility.">Mark Doffman</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="mindforks" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://mindforks.org/" title="Idle bandter about accessibility and other stuff">mindforks</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Monotonous.org" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://monotonous.org" title="Eitan's Pitch">Monotonous.org</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Nagappan's Weblog" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://nagappanal.blogspot.com" title="LDTP maintainer, a11y-tester through LDTP.">Nagappan's Weblog</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Neville's Blog" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://figod.blogspot.com/" title="Neville's Blog">Neville's Blog</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="NV Access news" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.nvaccess.org/" title="Information about NV Access Inc (a non-profit organisation created to support the NVDA screen reader)">NV Access news</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="NVDA" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.nvda-project.org/" title="News and thoughts from the developers of NVDA (Nonvisual Desktop Access, A free and open source screen reader for Microsoft Windows)">NVDA</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="OpenConcept Accessibility Threads" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://openconcept.ca/topic/accessibility" title="We're working to bring accessibility into Drupal Core">OpenConcept Accessibility Threads</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Peter Korn's Weblog" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://blogs.sun.com/korn" title="The collected occasional commentary by Peter Korn">Peter Korn's Weblog</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Peter Parente" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://mindtrove.info" title="mindtrove.info">Peter Parente</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="pixeldiva" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.pixeldiva.co.uk/tag/accessibility" title="On Accessibility">pixeldiva</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Planet-A11y" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.planet-a11y.net/announcements" title="Planet-A11y News and Updates">Planet-A11y</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Radical Accessibility" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://delysid.org/" title="The internet seen from the perspective of a blind guy">Radical Accessibility</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Silvia Pfeiffer" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://blog.gingertech.net/category/video-accessibility/" title="Open Digital Media Technology Blog">Silvia Pfeiffer</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="STC AccessAbility SIG Blog" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.stc-access.org/" title="An Accessibility and Technical Communication Blog">STC AccessAbility SIG Blog</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Steve's Technology Access Notes" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://fullmeasure.co.uk" title="Open Source a11y and open source in education">Steve's Technology Access Notes</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="The 58 Sound" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://58sound.com" title="thoughts on accessibility, usability and incluisve interaction design">The 58 Sound</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="The Paciello Group" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.paciellogroup.com/blog/" title="Accessibility blog">The Paciello Group</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="tim o'brien photos" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.timobrienphotos.com/" title="accessibility, photography, economics">tim o'brien photos</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Wanderings of an aimless vortex" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://lightvortex.livejournal.com" title="Record of my mono-a11y and atspi-dbus work [and occasional musings about politics, sustainability, and life in general">Wanderings of an aimless vortex</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="WebA11y" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://www.weba11y.com/blog/" title="Adventures in Web Accessibility">WebA11y</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="WebAIM" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://webaim.org/" title="Web Accessibility In Mind">WebAIM</a></li> <li><input style="margin-left:5px;" type="checkbox" id="showBlog" name="Willie Walker's Weblog" checked="checked"><a style="padding-left:5px;padding-right:5px;" href="http://blogs.sun.com/wwalker" title="Sparse mentioning of the doings of Willie Walker">Willie Walker's Weblog</a></li> </ul> </div> <div class="close"></div> </div> <div class="block"> <div id="notToggle" style="text-align: center; background: transparent !important;" class="text"> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=2nd vp" title="'2nd vp' returned a count of 32">2nd vp</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=a11y" title="'a11y' returned a count of 33">a11y</a> <a style="font-size: 30px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=accessibility" title="'accessibility' returned a count of 2202">accessibility</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=accessibility and usability" title="'accessibility and usability' returned a count of 13">accessibility and usability</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=accessibility testing" title="'accessibility testing' returned a count of 12">accessibility testing</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=ambiguity" title="'ambiguity' returned a count of 149">ambiguity</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=app" title="'app' returned a count of 27">app</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=apple" title="'apple' returned a count of 28">apple</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=aria" title="'aria' returned a count of 45">aria</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=article" title="'article' returned a count of 155">article</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=assignment" title="'assignment' returned a count of 30">assignment</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=assistive technology" title="'assistive technology' returned a count of 37">assistive technology</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=atlanta" title="'atlanta' returned a count of 12">atlanta</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=atlanta conference" title="'atlanta conference' returned a count of 13">atlanta conference</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=audio" title="'audio' returned a count of 15">audio</a> <a style="font-size: 14px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=audio recording" title="'audio recording' returned a count of 357">audio recording</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=blind" title="'blind' returned a count of 35">blind</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=blind photographers" title="'blind photographers' returned a count of 16">blind photographers</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=blog" title="'blog' returned a count of 203">blog</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=board positions" title="'board positions' returned a count of 12">board positions</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=body of knowledge" title="'body of knowledge' returned a count of 33">body of knowledge</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=caketalk" title="'caketalk' returned a count of 15">caketalk</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=cakewalk" title="'cakewalk' returned a count of 15">cakewalk</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=candidacy statement" title="'candidacy statement' returned a count of 38">candidacy statement</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=candidate" title="'candidate' returned a count of 40">candidate</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=chn" title="'chn' returned a count of 31">chn</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=code" title="'code' returned a count of 12">code</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=coding" title="'coding' returned a count of 15">coding</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=community" title="'community' returned a count of 18">community</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=conference" title="'conference' returned a count of 32">conference</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=conferences" title="'conferences' returned a count of 20">conferences</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=developer" title="'developer' returned a count of 16">developer</a> <a style="font-size: 25px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=development" title="'development' returned a count of 1705">development</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=digital media" title="'digital media' returned a count of 19">digital media</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=disabilities" title="'disabilities' returned a count of 153">disabilities</a> <a style="font-size: 14px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=drm" title="'drm' returned a count of 353">drm</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=education" title="'education' returned a count of 17">education</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=elections" title="'elections' returned a count of 40">elections</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=enabling technology" title="'enabling technology' returned a count of 18">enabling technology</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=features" title="'features' returned a count of 12">features</a> <a style="font-size: 26px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=firefox" title="'firefox' returned a count of 1762">firefox</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=flash" title="'flash' returned a count of 15">flash</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=general" title="'general' returned a count of 18">general</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=generalnews" title="'generalnews' returned a count of 43">generalnews</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=generalprogressupdate" title="'generalprogressupdate' returned a count of 14">generalprogressupdate</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=glenda watson" title="'glenda watson' returned a count of 149">glenda watson</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=gnome" title="'gnome' returned a count of 30">gnome</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=google" title="'google' returned a count of 20">google</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=hillary hart" title="'hillary hart' returned a count of 33">hillary hart</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=home recording studio" title="'home recording studio' returned a count of 15">home recording studio</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=html" title="'html' returned a count of 11">html</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=html5" title="'html5' returned a count of 15">html5</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=hyperlinks" title="'hyperlinks' returned a count of 149">hyperlinks</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=hypertext links" title="'hypertext links' returned a count of 149">hypertext links</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=ideas" title="'ideas' returned a count of 14">ideas</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=information" title="'information' returned a count of 28">information</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=iphone" title="'iphone' returned a count of 42">iphone</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=iphone app" title="'iphone app' returned a count of 24">iphone app</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=ipod" title="'ipod' returned a count of 15">ipod</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=ipod touch" title="'ipod touch' returned a count of 11">ipod touch</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=itunes" title="'itunes' returned a count of 11">itunes</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=javascript" title="'javascript' returned a count of 20">javascript</a> <a style="font-size: 15px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=jaws scripts" title="'jaws scripts' returned a count of 377">jaws scripts</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=knowledge portal" title="'knowledge portal' returned a count of 32">knowledge portal</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=landscape mode" title="'landscape mode' returned a count of 13">landscape mode</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=large print" title="'large print' returned a count of 215">large print</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=large print ideas" title="'large print ideas' returned a count of 19">large print ideas</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=law and policy" title="'law and policy' returned a count of 22">law and policy</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=linux" title="'linux' returned a count of 23">linux</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=mobile" title="'mobile' returned a count of 17">mobile</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=mono" title="'mono' returned a count of 11">mono</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=mozilla" title="'mozilla' returned a count of 79">mozilla</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=music production" title="'music production' returned a count of 19">music production</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=neurologically impaired" title="'neurologically impaired' returned a count of 13">neurologically impaired</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=new software" title="'new software' returned a count of 12">new software</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=news" title="'news' returned a count of 14">news</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=novell" title="'novell' returned a count of 16">novell</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=nvda" title="'nvda' returned a count of 14">nvda</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=open source" title="'open source' returned a count of 75">open source</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=opensuse" title="'opensuse' returned a count of 48">opensuse</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=opera" title="'opera' returned a count of 24">opera</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=os x" title="'os x' returned a count of 30">os x</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=pdf" title="'pdf' returned a count of 14">pdf</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=personal" title="'personal' returned a count of 13">personal</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=programming" title="'programming' returned a count of 32">programming</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=review" title="'review' returned a count of 17">review</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=screen reader users" title="'screen reader users' returned a count of 149">screen reader users</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=screen readers" title="'screen readers' returned a count of 168">screen readers</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=screenreaders" title="'screenreaders' returned a count of 21">screenreaders</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=sight impairments" title="'sight impairments' returned a count of 149">sight impairments</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=software" title="'software' returned a count of 11">software</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=software development" title="'software development' returned a count of 15">software development</a> <a style="font-size: 14px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=sound taxi" title="'sound taxi' returned a count of 352">sound taxi</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=sports" title="'sports' returned a count of 12">sports</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=standards" title="'standards' returned a count of 50">standards</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=standards groups" title="'standards groups' returned a count of 32">standards groups</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=stc" title="'stc' returned a count of 64">stc</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=stc elections" title="'stc elections' returned a count of 38">stc elections</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=strobist" title="'strobist' returned a count of 12">strobist</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=support" title="'support' returned a count of 16">support</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=supporters" title="'supporters' returned a count of 13">supporters</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=technology" title="'technology' returned a count of 23">technology</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=tim's photos" title="'tim's photos' returned a count of 39">tim's photos</a> <a style="font-size: 13px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=tip" title="'tip' returned a count of 157">tip</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=touch" title="'touch' returned a count of 15">touch</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=tweets" title="'tweets' returned a count of 14">tweets</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=twitter" title="'twitter' returned a count of 25">twitter</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=uncategorized" title="'uncategorized' returned a count of 116">uncategorized</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=users" title="'users' returned a count of 44">users</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=vice-president" title="'vice-president' returned a count of 32">vice-president</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=video" title="'video' returned a count of 17">video</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=video accessibility" title="'video accessibility' returned a count of 20">video accessibility</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=visual studio" title="'visual studio' returned a count of 15">visual studio</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=voiceover" title="'voiceover' returned a count of 15">voiceover</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=w3c" title="'w3c' returned a count of 29">w3c</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=wai-aria" title="'wai-aria' returned a count of 22">wai-aria</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=wcag 2.0" title="'wcag 2.0' returned a count of 13">wcag 2.0</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=web" title="'web' returned a count of 42">web</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=web 2.0" title="'web 2.0' returned a count of 33">web 2.0</a> <a style="font-size: 12px" class="tag_cloud" href="http://www.planet-a11y.net/?tag=web accessibility" title="'web accessibility' returned a count of 39">web accessibility</a> </div></div> </div><div id="site_bottom">Phanet does not generate contents each post belongs to the author.<br/> © 2008 - <a href="http://www.phanet.net" >Phanet</a> is under GPLv2</div> </div> </div> </body> </html>