We present to you a menu of tidbits collected in recent days that are too short for blog posts and sometimes too long for a tweet (when we want to add clarifying comments). Headings provide a light grouping to help you skim the offerings. Bon appétit!
Where to Discuss Accessibility?
The Accessify Forum [No longer active as of 15May16] is an excellent place for accessibility discussions – for developers, technical communicators. All are welcome! A recent topic showing the versatility and importance of this forum discusses who is responsible or accountable for accessibility issues. Stop by soon.
Where to Learn About Accessibility?
It depends. Next question. No, seriously, this is a big topic because it depends on what you mean by accessibility. Do you write code? Do you write policies and procedures? Your accessibility focus will depend on your actual work. However, a good foundation is good for everyone, so stopping by the WaSP InterAct Curriculum at webstandards.org will always be a good choice. Get your bearings on the About page. (By the way, it’ll be time to say Happy Birthday soon. WaSP InterAct was born at the South by Southwest Interactive conference in March 2009.)
Another good starting point is ScrunchUp, the web magazine for young designers and developers.
More resources can be found at The OneVoice for Accessible ICT. OneVoice aims to “assist organisations in embedding accessible information and communication technologies (ICT) as a fundamental part of their diversity and inclusion values and culture.” It is a new, still developing site, so come back frequently to find resources for best practice, tools, and guidelines for web designers and developers, HR and IT departments, and other parts of the organization involved in building accessible ICT.
Alt and title attributes are parts of the web content that aren’t immediately visible, yet they are important to know and understand.
Get help from Ian Pouncey’s articles: Alt attributes and Title attributes. Steve Faulkner, The Paciello Group, has been diligently updating the draft for HTML5: techniques for the provision of text alternatives – another resource to monitor. Finally, Vlad Alexander asks how web browsers should render alt text.
Definitely an area for technical communicators to monitor!
Short and Sweet – Abbreviations
Make a note of “a11y” and “tsaccess” for future reference.
“a11y” stands for “accessibility”. A is the first letter, y is the last letter, and 11 is the number of all the other letters in between the a and the y! Some might recognize this model from “l10n” (localization) and “i18n” (internationalization). In the world of Twitter, saving letters counts! Purists will cringe, and others will argue that these terms are not clear, but they are here to stay.
“tsaccess” is a new term that stands for “touch screen accessibility”. Touch screens are getting a lot of attention with iPhones, the iPad, and other devices with touch-sensitive screens. Where is the accessibility in that? Jennison Asuncion coined “tsaccess” as a hash tag that can be used to discuss this topic on Twitter, in conferences, or wherever hash tags are used.
Connect the Dots
Braille for Everyone is an interesting new initiative that could lead the way to less expensive braille devices, which could promote a wider use of Braille. Why Braille? You may recall a recent article in the New York Times about Braille and literacy that went around Twitter. Audio books and videos are convenient to use when we are on the go, and videos seem to be touted as the way for technical communicators to make documentation in the futures. The literacy issue that has been raised in connection with the decline in Braille sounds quite alarming. One blogger even asks can Braille become obsolete. Technical communicators preparing single-sourced material to be delivered in multiple ways should be very concerned about literacy issues for that material. It is a topic worth monitoring.
The U.S. Department of Labor, Office of Disability Employment Policy has an article about when to consider revealing a disability to a prospective employer. Your mileage may vary depending on your local laws and situation, but the article has some useful insights.
Employers should read People with Disabilities: The Talent You're Missing. No explanation is necessary with that title.
Doing it My Way
The beta version of the accessibility pages for the BBC website is quite impressive. It’s called My web my way and definitely worth a visit, especially for some good old inspiration. The page has links to other great accessibility offerings from the BBC, so grab a cuppa and poke around the site for a while.
An Awesome Newsletter
The University of Minnesota at Duluth has been sending out the Web Design Update newsletter since 2002. Any time news or information is posted to the Web Design Reference site, a newsletter is sent out to subscribers. Get your copy of the newsletter today by following the WDU newsletter subscription information. You can also read past issues on that site. I remember hearing about that site on the STC Lone Writer SIG discussion list years ago. Awesome is the general term used to describe the resources at the Web Design Reference site.
SharePoint and the Technical Communicator
SharePoint is rather notorious among technical communicators – some love to hate it. Offices toss it out on the web because they have it in some package deal. Most could use better training and education, but that requires knowledge about its accessibility. Bruce Lawson wrote about SharePoint accessibility in 2008 and Alastair Campbell wrote about SharePoint 2010 late last year. These two posts should get you talking about accessibility and SharePoint in your workplace.
The Last Word
@gezlemon posted a tweet that was too good to pass up. He writes that it is a true story from Radio 4 (in the UK).
“Right-click on your desktop.”
“What do you see?”
“What did you do?”
“Wrote click on my desktop.”
This post was glued together with links or inspiration from many people. They are listed with their Twitter names.