PUBLIC MARKS with tags [en] & accessibilité

A practical resource for content authors that shows you how to comply with WCAG 2.0. Each topic explains what you need to do, why you need to do it and how to do it in easy-to-understand language.

Make no mistake: Sectioning elements help you improve document structure, and they’re in the spec’ to stay. Once and for all, I will be exploring the problems these elements solve, the opportunities they offer and their important but misunderstood contribution to the semantic Web.

My biggest overall takeaway from this experience was how inaccessible many sites are, and how frustrating it must be to a person with certain disabilities to regularly have poor web experiences. As developers, it’s our job to keep this in mind when creating any site, whether it “needs to be accessible” or not. You can bet that these lessons are being baked back into our work. Hopefully some of these will make it into your next projects as well.

The reality is that accessibility is simply a key part of UX. A truly outstanding digital experience is a fusion of accessibility, usability, creativity and technology. The trick is to weave those things together, and to do that successfully there needs to be a cross pollination of skills and expertise.

The good news is that accessibility is usability under a magnifying glass. If you’re thinking about great usability, the chances are that you’re already thinking about great accessibility too.

It's no exaggeration to say that the recently released NVDA upgrade is a huge step forward for PDF accessibility. With respect to tables, NVDA now matches JAWS in almost every way that matters, and in some respects it is significantly better. NVDA is now a realistic alternative to JAWS.

This one is for testers who use NVDA, a free screenreader, to test online content for any access issues.

In my experience, the range of parameters devised is fairly large and it is easy to get lost in selecting configurations or even anticipating how well they will fit user needs. Still, these tactics seem important for practitioners to apply when appropriate. The challenges strike me as fundamental, given the range of needs and potential interface designs.

What does the outline property do?

It provides visual feedback for links that have "focus" when navigating a web document using the TAB key (or equivalent). This is especially useful for folks who can't use a mouse or have a visual impairment. If you remove the outline you are making your site inaccessible for these people.

Browser support is IE10 and modern versions of Firefox, Safari, Chrome, Opera. Basic support for IE9. No responsive version yet, sorry (but you can always send pull requests!)

For years now, we've used a number of techniques for hiding content offscreen for accessibility purposes. We do this because the content is still accessible to screenreaders while being removed from the interface for sighted users.

Part polemic, part instruction manual, The Truth About HTML5 has ignited an interesting debate. Here we present an exclusive excerpt on the problems around structuring in HTML5

Compatibility tables for support of HTML5, CSS3, SVG and more in desktop and mobile browsers.

Why I created this resource

This list should not be taken as a stab against tools and tool vendors. I’ve said numerous times that we should do automatic testing first. When done properly, automatic testing offers a degree of efficiency that cannot be matched by other methods. However, that doesn’t mean that we should leave our compliance up to automated testing. As the tables above show, there are 9 WCAG Success Criterion (in Level A and AA) that cannot be tested for in any meaningful manner using a tool. There are another 13 that can be tested for automatically but require a human to verify. Full compliance and risk mitigation always requires the involvement of a skilled professional reviewer, even when you have a tool as well.

This mantra is as true for the mobile Web as it is for the desktop Web.

It’s important to note that PDF/UA is neither a spec to measure PDF content, like the Web Content Accessibility Guidelines (WCAG), nor an everyday authoring guide. It focuses on giving developers of PDF authoring tools and viewers, as well as vendors of assistive technologies that support PDF, critical information on how to build and present PDF content more accessibly. The goal is to make accessible PDFs easy to author and use, however they are produced.

The new caption editor function, developed by a Google intern and his mentor, allows users to correct automatic captions within the YouTube website.

This article is based on the WCAG 2.0 (Web Content Accessibility Guidelines), a worth reading set of recommendations for making Web content more accessible, that is, more friendly for people with disabilities.

IBM Research-Tokyo recently partnered with NCAM to research ways to deliver online audio descriptions via text-to-speech (TTS) methods, rather than using human recordings. IBM and NCAM explored two approaches which exploit new HTML5 media elements as well as Javascript and TTML

If you are about to redesign your website, now is a good time to focus on getting a website that can be used by as many people as possible. Here are some tips on when and how to make requirements and focus on accessibility throughout the process.