Frederik Van Zande's Library tagged accessibility →  View Popular

"In October 2009, WebAIM conducted a survey of preferences of screen reader users. This was a follow-up survey to a previous survey. We received 665 valid responses to the screen reader user survey. More in-depth analysis and documentation on the free-form responses will be available in the future.

A few disclaimers and notices:

* Totals may not equal 100% due to rounding.
* Total responses (n) for each question may not equal 665 due to respondents not answering that particular question.
* The sample was not controlled and may not represent all screen reader users.
* Care should be taken in interpreting these results. Responses are based upon user experiences with web content that is generally inaccessible. We cannot help but wonder if responses may have been different if screen reader interactions with web content were typically very positive.
* Data was analyzed using JMP Statistical Discovery Software version 8
* We hope to conduct a survey of this nature again in the future. If you have recommendations or questions you would like asked, please let us know. Additional analysis of this data and details on the responses to open-ended questions will be available in the future."

webaim.org/...screenreadersurvey2 - Preview

usability accessibility survey browser

"When using HTML tables to mark up tabular data, remember to use th elements for cells that provide header information for rows or columns."

www.456bereastreet.com/..._column_headers_in_data_tables - Preview

table html accessibility header scope

www.personal.psu.edu/...ColorBrewer.html - Preview

accessibility color color blind color palette tool

In December 2008 through January 2009, WebAIM conducted a survey of preferences of screen reader users. We received 1121 valid responses to the screen reader survey, which was conducted Dec. 2008 - Jan. 2009. The response was amazing. Below are the initial quantitative results and a few observations on the survey results. More in-depth analysis and documentation on the free-form responses will be available in the future.

webaim.org/...screenreadersurvey - Preview

accessibility screen reader webdesign screenReaders research best practice

Back in Crimes Against Hypertext, I identified several common examples of poor hyperlinking. It generated an interesting discussion so I thought I’d write a follow-up, adding a few more examples and some solutions.

www.sitepoint.com/...more-crimes-against-hypertext - Preview

link copywriting click through best practice accessibility

This failure describes a common condition where links such as "click here" or "more" are used as anchor elements where you need to have the surrounding text to understand their purpose and where there isn't any mechanism to make the destination clear by itself, such as a button to expand the link text.

www.w3.org/...F84 - Preview

accessibility click through link copywriting

When people talk about both usability and accessibility, it is often to point out how they differ. Accessibility often gets pigeon-holed as simply making sure there are no barriers to access for screen readers or other assistive technology, without regard to usability, while usability usually targets everyone who uses a site or product, without considering people who have disabilities. In fact, the concept of usability often seems to exclude people with disabilities, as though just access is all they are entitled to. What about creating a good user experience for people with disabilities—going beyond making a Web site merely accessible to make it truly usable for them?

www.uxmatters.com/...r-people-with-disabilities.php - Preview

accessibility best practice forms

I recently gave an internal presentation at Headscape about WCAG 2. A number of people expressed an interest in seeing it so I made a point to record it.

boagworld.com/...video_introduction_to_wcag_2 - Preview

accessibility wcag best practice video audio

The old Accessibility Evaluation and Repair Tools (AERT) suggested algorithm for determining colour contrast now directs here. The AERT algorithm was never a recommendation, and WCAG 2.0's luminosity contrast algorithm is recommended instead.

juicystudio.com/...luminositycontrastratio.php - Preview

contrast tool text copy headers usability visual impairment accessibility luminosity design

AnySurfer is een kwaliteitslabel voor websites die voor iedereen toegankelijk zijn — ook voor mensen met een functiebeperking.

Slechtzienden, blinden en ouderen ervaren online het vaakst problemen, maar AnySurfer bewaakt ook de toegankelijkheid voor internetgebruikers met motorische en auditieve beperkingen.

anysurfer.be/nl - Preview

belgie accessibility guidelines label quality label tests

Basic web accessibility is a known commodity now. Web applications can almost be made accessible; eventually web application accessibility will also be a known commodity, too. Those are clear wins.

But nearly ten years after specifications first required it, online captioning still pretty much does not exist. That’s probably going to change, and the way it’s going to change is by government regulation.

Does that strike you as unthinkable? Do you view the web as a libertarian place where old-media laws barely apply, if at all? Well, prepare for a shock. Legislation is probably coming. And not only should you let it happen, you should get behind it—but only if it’s done using open standards.

www.alistapart.com/...thisishowthewebgetsregulated - Preview

accessibility video captioning subtitles regulations legal

The following is a guest post from Armando Roggio, a web developer, a marketer, the Contributing Editor of Practical eCommerce and a serial entrepreneur with many micro-businesses.

The leading web standards body, the World Wide Web Consortium (W3C) recently announced new content accessibility guidelines (WCAG 2.0) to help make the Internet easier for blind, deaf or otherwise disabled web-surfers to access and use. Such visitors require aids such as screen readers to follow content.

Not only is adhering to web accessibility standards ethically and morally the right thing to do, there are 2 other pragmatic reasons to abide by WCAG 2.0:

www.getelastic.com/eb-accessibility-for-ecommerce - Preview

accessibility e-commerce

Google Maps is a powerful, free tool for adding maps to a site. Unfortunately, out of the box, these maps are reliant on mouse interaction; therefore, they are completely inaccessible to those using only the keyboard for Web interaction. In this article, we'll examine the problem and, step by step, make our way toward a possible solution.

I'll assume that you're familiar with the basics of Google Maps, have obtained your API key , and implemented a map on your site. Now, let's say that you want to make your map a tad more accessible but without changing the look and feel of your existing map (maybe because your boss or designer insists on it)— a case of unobtrusive accessibility, if you will.

dev.opera.com/...eyboard-accessible-google-maps - Preview

accessibility google maps keyboard input

"Accessible Forms using WCAG 2.0" is the first of a series of documents to help web professionals use the Web Content Accessibility Guidelines Version 2.0 to develop accessible websites.

www.usability.com.au/...wcag2 - Preview

wcag accessibility form best practice

Using video and audio in a website increases the probability of an accessibility problem. Where text can be readily translated into a wide variety of alternative mediums for the disabled, the complex nature of video and audio make this kind of machine-generated comprehension nearly impossible. Add to that the fact that reading a transcript hardly conveys an experience equivalent to the excitement of an expertly-produced audio file, and it’s clear that marketers have a serious challenge when targeting the disabled using video and audio.

In this article, I’ll be looking specifically at ideas to help make video and audio promotions more accessible – and marketable – to the deaf/hard-of-hearing community.

www.practicalecommerce.com/...-and-Audio-Usable-For-The-Deaf - Preview

video audio accessibility deaf optimizing

In recent months, many web designers have been asking the question, “How can I make my dynamic site accessible?” Unfortunately, good answers have been slow in coming from the accessibility community. While some articles have touched on the problem, not many have gone into details. Here is our first attempt at rectifying this situation.

northtemple.com/...javascript-and-screen-readers - Preview

javascript screenreader accessibility best practice

uitest.com - Preview

usability accessibility validation uitest

Surprisingly many tools exist on the web that can help your site become more inviting and easier to use. By now, you are probably familiar with the free tools offered by Flickr, del.icio.us, or YouTube for embedding images, tags, and videos on webpages. I highly recommend experimenting with these. Here is a comprehensive list of some perhaps lesser-known but equally useful tools for your site. This list can also be found at http://del.icio.us/cpretlow. Screen Recording Software

www.redorbit.com/...s_to_create_userfriendly_sites - Preview

tools usability accessibility webdevelopment free

Your guide for developing usable and useful Web sites

www.usability.gov - Preview

webdesign design reference accessibility government web usability testing

Including articles, spreadsheets, links, and other resources related to usability metrics. We're adding to this site regularly, so please check back!

measuringuserexperience.com/index.htm - Preview

user experience best practice tools survey usability analysis tests card sorting accessibility