Watch videos with subtitles in your language, upload your videos, create your own subtitles! Click here to learn more on "how to Dotsub"

Accessible Content Basics

0 (0 Likes / 0 Dislikes)
Hi, this is Kevin - maintainer of the Accessible Content module. and I'm going to show you how it easy it is to integrate accessibility checking into your drupal site. So I've got a Cat News site with news all about cats. It's a really nice site, except except amongst my great content, there's BLINK tags there's paragraphs which are BOLD which really should be headers and the dreaded images with no ALT attributes. So I have a great site, but it's not accessible and it's also not semantically correct. So in order to help me find out where my pain points are, I've downloaded the Accessible Content module. I've also followed the installation readme file, which also shows that you need to download the QUAIL library for accessibility checking. Pretty simple to do. So I'm just going to go to my module page. And enable Accessible Content module. There are some other modules that come with accessible content and we'll go over a few of those And I'm just going to save. So, um, Accessible Content installs over 200 nodes that are called accessibility tests, and a handful of accessibility guidelines that are collections of tests. So if I go to my content area, I can see that there were a number of guidelines that were installed. I have section 508. I have WCAG 1.0 A through AAA, and I have WCAG 2.0 A through AAA. And if I change my filter... I can see pages and pages of accessibility tests. So, for example, there's a test called "PRE elements should not be used for tabular data" it's triggered every time you see a PRE, and that just let's you know if this is tabular information you really should use a well-formed table. But enabling the module does not automatically enable accessibility checking. To give you the most flexibility, you can actually turn accessibility checking and the preferred guideline on and off per content type. So I'm just going to go to my content type for News Article. And you'll see there's a new section called "Accessibility Checking" There's a check box for just enabling checking for accessibility By default this is off - it's Ignore errors that involve document or header-related information there are some tests that QUAIL introduces inherently that are tests for things like the document's DOCTYPE is correct or the language for the document is set appropriately. Those are tests that content creators in Drupal don't really need to be concerned about So if you check this setting, that'll ignore any tests like that There are some use cases where people might find that useful, so we left those tests available. If you have very complex filter rules, if you want to run them before as input formats before QUAIL checks the content for accessibility this is where you can do that. Tests are broken into three different categories: there's SEVERE tests which are tests where we can know 100% if there is a problem so these are things like "an image is missing an ALT attribute" there is no question, there is a problem there if we find that. So if you have this check box turned on, that will prevent someone from saving a node until there are no severe errors. You can even disable tests entirely by severity level. So severe are those 100% certain there's a problem moderate are tests where there might be a problem, and suggestions are things that are more informational. Things like the document is written in a well-structured way, or language tags are applied correctly those are things that people might need to know about informationally, but there's very few ways that we can tests for that. I'm going to turn them all on for purposes of demonstration. We can then select a guideline that either came with QUAIL, or a guideline that we built ourselves. I'm going to select WCAG 2.0 (AAA). So that sets accessibility settings for all future news articles, but I already have a rich selection of cat-related News Articles. (A collection of... four, um) So what I'm going to do is check existing content on this site, especially if you have thousands of nodes, this is very nice. Under "Site Configuration," there's the "Accessible Content" area, These we'll go over a little bit later, There's a tab called "Check Existing Content" and it just checks all the existing content where you have set the accessibility settings. I'm going to select a News Article, it does a batch process. Now a site with a few thousand nodes might take faster than that, but, sorry, be much SLOWER than that, but still it's nice to have that feature. I'm also going to turn on a block that comes with the module called "Page Accessibility Overview." I've enabled that for my blocks. That will turn on automatically if you are viewing a page which has checking turned on for that content type. So I'm just going to go to my existing content... I can see there are two severe errors here, three moderate errors, and one suggestion. So already I can get just at a glance an overview of what is wrong on this page. On every page where accessibility is turned on for that content type, there is an "Accessibility" tab. An all this information can be controlled using user permissions, so under "accessible_content" in your permissions area, you can turn on or off "is allowed to view accessibility information," and "is allowed to override accessibility tests." Which might be useful if you are in an institution where you want to manually review things. I could, for example, say "OK, this is a suggestion that any words or phrases which are not the document's language be marked," and I can just manually say "hey, we've checked that, it's cool" and override it. And in the future that test will always be overridden. So I can see that there are also some moderate errors. For example, abbreviations must be marked with an ABBR tag, so there's an abbreviation here for CSUMB WCAG also asks for acronym elements around acronyms. And this is also another possible problem, that it thought there might be a quote in the text, and it's asking for me to use BLOCKQUOTE. Again, if you were a manual accessibility reviewer, you could override that. Then as long as the text in the page doesn't change, that error will never appear. And there's also severe errors. So I can see, that a BLINK tag should not be used. And also image elements should not have an alt attribute. Again, these are all regular nodes, these tests so if you are using WYSIWYG editors and people don't even know what an alt attribute is, You can just go ahead and edit that and say whatever you want. You can say "Images need a description" and here's how to do that using our editor. Also, if you are looking here, it's really hard to tell "well, where is that image?' So you can click "Highlight the Problem," it'll take you to a view of the node itself with a box around the specific problem, and a little icon in front of the problem. And under "Accessibility" there's a "Highlight Errors" sub-tab, Which will highlight all the errors on the page. And if you have Beautytips module installed, it will also give you these handy little beauty tips. Now, all of the classes for the dotted lines, the red boxes, the icons, can be changed to your liking under "Accessible Content." You can upload custom icons for severe errors, moderate errors, etc., and also change the classes to different classes to apply to your theme. Another thing you can do with this module is... I have a view there, it's views enabled. I've already built this view, but under the "fields" section in views, there will be another group called "Accessibility Overview." So if you want to make a report and say "hey, show me all the ones that have the highest severe errors, so I know which content on my site I need to check, and is the biggest pain points," you can go ahead and do that, and use all the power of views to create custom reporting on your content. So that's the general overview of how to install and enable the Accessible Content module on your site. Another thing you should know about know is, a lot of times people use WYSIWYG editors. So I'm going to turn the WYSIWYG API module on. There's an Accessible Content WYSIWYG integration module. And what that allows you to do is... right now this is only for TinyMCE, but we are looking at additional ones in the future, is if you have TinyMCE installed under "Buttons and Plugins," there will be a "Check Accessibility" button. So then while authors are writing content, I'm going to go ahead and edit this page... there's a new "Check Accessibility of Selected Content" button, so all I have to do is select everything and another window opens with an accessibility overview of my content before I've even saved it. So that's a nice feature to have, to let people just write some information and - if they're not sure it's accessible they can check it immediately without having to save the page. There's also a highlight accessibility and "Check Accessibility" links below there for any other text area or WYSIWYG editors that we dont' support. Another thing to point out is that you can check the accessibility of CCK text fields. So under my content type for News Article, I have a field called a Sidebar. So I'm going to configure that and under there, there's an "Enable Accessibility Checking" checkbox which will just make this CCK text field inherit the accessibility settings of it's parent node type. So we're going to a page with an image within a CCK field with no ALT attribute. So we can go ahead and... just change it. So now we can see the totals have changed and under the "Accessibility" tab, we can see for the Node Body there's a severe error, and also for Sidebar there's a severe error and if we highlight the errors, it also sees the problems with the sidebar itself. So you can turn on and off accessibility per field and it will just inherit the settings from their parent node type So that's a quick introduction to the Accessible Content module... and I hope it helped you out!

Video Details

Duration: 13 minutes and 33 seconds
Country: United States
Language: English
Producer: Kevin Miller
Views: 699
Posted by: kevee on Apr 26, 2010

An overview of the Accessible Content module for Drupal - an interactive accessibility checking tool.

Caption and Translate

    Sign In/Register for Dotsub to translate this video.