Blogging is often just text or a combination of text, images and links. Therefore it is easy to make a blog accessible. However a blog has all the same potential accessibility issues as a web site does. Consequently blogs should always be tested against the W3C Web Content Accessibility Guidelines, Version 1.0, Level AA.
Checkpoint 3.5 requires that header elements are used to convey document structure and that they are used according to specification.
Checkpoint 10.2 requires that all form controls with implicitly associated labels, that the label is properly positioned.
Checkpoint 12.4 requires that labels are explicitly associated with their controls.
Checkpoint 13.1 requires that the target of each link is clearly identified.
Headings
Make sure that the blog post is a heading, and that each blog post heading is at the same level. If you use headings within blog posts then make sure all headings are nested properly. The name of the blog should be an H1.
Field labels
Where users can add comments, ensure that each field has a descriptive field label that is immediately to the left or immediately above the relevant field.
Ensure that these fields and field labels are coded using the FOR ID and LABEL elements.
Links
Most blog posts contain links to the comments section. It is imperative that these links are unique. So, for example, if there are a number of comments on a particular blog post then the link should include the number of comments and the name of blog post. For example "34 comments on Writing accessible blog posts".
Source: Accessibility Toolkit Version 3, September 2009. Section 5 - Blogging and Accessibility.
Last updated: 14 October 2010(This document requires the use of Adobe Acrobat Reader). Department of Business and Innovation, Information Victoria, September 2009 - Version 3.1.1 - March 2011 (minor edits). "The Victorian Government’s Accessibility Standard requires that: All websites must be Level AA compliant (W3C Web Content Accessibility Guidelines, Version 1.0); Where audience needs are specific, websites should become Level AAA as appropriate. This toolkit shows departments and agencies how to conform to this policy and the W3C Web Content Accessibility Guidelines, Version 1.0. The toolkit is designed for Victorian Government business managers and web site owners to enable them to effectively present the business case for accessibility and manage the processes involved..."
An accessible HTML version of the toolkit is currently under development.
(This document requires the use of Microsoft Word Reader). Department of Business and Innovation, Information Victoria, September 2009 - Version 3.1.1 - March 2011 (minor edits). "The Victorian Government’s Accessibility Standard requires that: All websites must be Level AA compliant (W3C Web Content Accessibility Guidelines, Version 1.0); Where audience needs are specific, websites should become Level AAA as appropriate. This toolkit shows departments and agencies how to conform to this policy and the W3C Web Content Accessibility Guidelines, Version 1.0. The toolkit is designed for Victorian Government business managers and web site owners to enable them to effectively present the business case for accessibility and manage the processes involved..."
An accessible HTML version of the toolkit is currently under development.
Enter your email address to subscribe or unsubscribe from the eGov What's New mailing list.
Please enter email address of the person you wish to send this page to.