Accessibility
Get flash to fully experience Pearltrees
The different methods of indicating a link’s purpose are often misunderstood and incorrectly implemented. The Web Content Accessibility Guidelines (WCAG) explicitly require that link text accurately reflects the target and purpose of the link. While current Section 508 standards do not explicitly state this — many Federal Agencies in the US require similar practices under Section 1194.31 Functional Performance Criteria. The harmonization of Section 508 as indicated in the US Access Board’s last Advanced Notice of Proposed Rulemaking (ANRPM) also indicates that link purpose will be explicitly required when Section 508 is refreshed. A number of techniques exist that can be used by developers to meet the WCAG success criteria.
Methods of Indicating the Purpose of a Link | SSB BART Group
Now this would all be fine and dandy if developers were able to clearly identify which web content technologies, when used appropriately, are sufficiently supported by assistive (adaptive) technologies to be considered “accessibility supported” within the meaning of WCAG 2.0. However, when WCAG 2.0 was released in December 2008, the WCAG Working Group and the W3C effectively side-stepped this question, and more than three years later they continue to do so. “The Working Group, therefore, limited itself to defining what constituted support and defers the judgment of how much, how many, or which AT must support a technology to the community and to entities closer to each situation that set requirements for an organization, purchase, community, etc.” Understanding Accessibility Support
Is PDF accessible in Australia?
storytelling with data: tables that make sense
While catching up on some online reading this morning, I came across an article in the Washington Post titled " College Majors and Their Income Potential ". I was curious how my brother, a recent grad with degrees in Italian and Political Science, would stack up. Here is the table that was included with the article: I started to read the table. It looks nice: visually clean, no unnecessary clutter. When I first dove into the detail, I thought it might be ordered by increasing Unemployment Rate: 7.0...7.7...8.2...5.4?
Accessibility tools, web developer tools, wizards and markup generators | Accessify
Accessibility Tools Updated Accessible Table Builder - Create an accessible table using scope , header and id attributes using a wizard to guide you through the process. Quick Page Accessibility Test .“I want to do the right thing and make my blog accessible to people with disabilities, but I have so much to do. I just don’t have the time.” After uploading the image, delete the file name from the Title field (that is utterly useless!) and type a succinct description into the Alternative Text field.
Take the Accessibility Challenge: Make Your Next Blog Post Accessible in 75 Seconds | Blog Accessibility
Programmatically Determined | Articles | Accessible Culture
The phrase "programmatically determined" features prominently in six of the 61 WCAG 2.0 Success Criteria. It's a bit of a mouthful, for sure, and perhaps a little daunting to those getting into accessibility and WCAG for the first time, but it's really not that complicated. In fact, you may already have a handle on it, even if you're not familiar with the phrase itself. Whatever the case, I think "programmatically determined" is a very useful concept for explaining, particularly to web developers, something about WCAG, what web accessibility means and why the proper use of HTML is so important. It's in the HTML Behind all your typical web page content is, of course, the HTML markup.
image credit: Mattox from stock.xchng images Getting information up on the web can sometimes be a rushed and last minute job. We’ve all done it. You’re under pressure and have lots of competing demands. Then you get an email that says they need something online by the end of the day. Attached is a long word document full of content, so you PDF it to get it online and meet the deadline.
Why PDF Documents Shouldn’t Be Used For Web Content | Shortie Designs
It’s the time of year when web accessibility advocates tend to produce accessibility myths blogs … As nothing stays still on the web, and many of these blogs are rather old (other than Ian Pouncey’s great blog earlier this year), it’s important that our understanding of accessibility myths moves on too… So, for Christmas 2011, and to hook-in with the user-research blogs in my series on implementing BS8878 , here’s Part One of some accessibility myths I’d like to expose to clear out the cobwebs before 2012, based mostly on my experience and user-research from my time at the BBC .
Web accessibility myths 2011 – a call for accessibility advocates to be more business-minded
Posted: January 23rd, 2010 | Filed under: Accessibility , Web Development | Tags: accessibility , web development | There is a lot of good advice for the discerning web developer to find on the web on how to make a website accessible, unfortunately there is also plenty of bad or outdated advice out there as well. Here are a few of the myths of accessibility that you may hear. Validation equals accessibility Good markup is the foundation of a usable, accessible and robust website.
Ian Pouncey » Blog Archive » Web accessibility myths
Start with the link, not the sentence. Often, all you need is a nice clear link. No summary text. The link should be the first thing you think about. You should only add surrounding text if absolutely necessary. Write links like you would write a heading.
Tips for writing great links
In December 2010, WebAIM conducted a survey of preferences of screen reader users. This was a follow-up survey to the original WebAIM Screen Reader User Survey of January 2009 and the follow-up survey from October 2009 . We received 1245 valid responses to this survey (1049 English, 101 Spanish, 91 French, and 4 Portuguese responses).