Victorian
Government
Contact Centre
1300 366 356
Government
Contact Centre
1300 366 356
Main Menu
Resize Text
Categories, RSS and More
RSS News Feeds
Rate this Site
Members Forum
Accessibility Guidelines - Topics A-Z
Topics A-Z listing of resources detailing how to make your websites accessible.
4
Site Articles
- Accessibility Guidelines: Articles - Archive
- Articles and resources about accessibility guidelines, and in particular government and W3C guidelines.
Added: 16 December 2005
Page views: 3,080
Rating: 0.0
Votes: 0
- Accessibility Guidelines: Resources - Archive
- Resources about egovernment accessibility guidelines.
Added: 20 December 2005
Page views: 2,868
Rating: 0.0
Votes: 0
- Australian Human Rights Commission position on WCAG 2.0
- The Australian Human Rights Commission is engaging in a process of broad-based consultation, and at this stage they have not finalised a view on any specific aspect of WCAG2.0.
Added: 1 April 2009
Page views: 3,114
Rating: 5
Votes: 2
- Guideline: Accessibility: Understanding the WCAG - text alternatives
- All Victorian Government websites must conform to the Web Content Accessibility Guidelines (WCAG) by 2012/14. This Victorian Government guideline explains the intent and practical implementation of Guideline 1.1: text alternatives for non-text content.
Added: 4 July 2012
Page views: 24,736
Rating: 0
Votes: 0
75
External Links
- Information technology - W3C Web Content Accessibility Guidelines (WCAG) 2.0
- International Organization for Standardization - ISO/IEC 40500:2012 - 12 October 2012. "ISO/IEC 40500:2012 [Web Content Accessibility Guidelines (WCAG) 2.0] covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photo-sensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general..."
Added: 16 October 2012;
Page views: 389
Rating: 0
Votes: 0
- Creating Accessible PDFs
- HowTo.gov, Page Reviewed/Updated: September 25, 2011. "... Making your PDF documents accessible is important so that all users are able to access your agency's information—no matter its format. Not only is making your content accessible a best practice, agencies are also required by OMB to maintain accessibility and follow standards from Section 508 of the Rehabilitation Act as amended in 1998..."
Added: 26 March 2012;
Page views: 769
Rating: 0
Votes: 0
- PDF Techniques for WCAG 2.0
- W3C Working Group Note, 2012. "This Web page lists PDF Techniques from Techniques for WCAG 2.0: Techniques and Failures for Web Content Accessibility Guidelines 2.0. Technology-specific techniques do not supplant the general techniques: content developers should consider both general techniques and technology-specific techniques as they work toward conformance..."
Added: 3 February 2012;
Page views: 849
Rating: 0
Votes: 0
- Silverlight Techniques for WCAG 2.0
- W3C, 21 June 2011. "... Silverlight support for assistive technologies is based on implementing Silverlight for Microsoft UI Automation (often abbreviated as UIA). In the UIA accessibility framework, Silverlight is implemented as a UI Automation server. This means that Silverlight provides information about the application itself and its current content through the framework. Any subscriber to the operating system's automation can consume that information as a UI Automation client. One such client role is typically implemented by assistive technologies, most notably by screen readers. By acting as a UI Automation client, an assistive technology can programmatically determine many aspects of Silverlight content and content structure. In addition, UIA has APIs that can change the content in a predictable way that maintains security boundaries between applications. Reading information from Silverlight through the UIA accessibility framework requires no extra work on the part of a given assistive technology, presuming that the assistive technology has already implemented UIA. All information that Silverlight reports to UIA comes through the common property set, and a fixed set of possible user interactions is programmatically accessible through a discoverable set of automation patterns and techniques..."
Added: 14 July 2011;
Page views: 583
Rating: 0
Votes: 0
- For Review: Updated WCAG 2.0 Techniques
- W3C - Web Accessibility Initiative, 21 June 2011. "WAI announces a Call for Review of draft updates to supporting documents for WCAG 2.0: Techniques for WCAG 2.0 (Editors' Draft) and Understanding WCAG 2.0 (Editors' Draft). (This is not an update to WCAG 2.0, which is a stable document.) To learn more about the updates, see Call for Review: WCAG 2.0 Techniques Draft Updates e-mail. Please submit comments by 26 August 2011..."
Added: 23 June 2011;
Page views: 586
Rating: 0
Votes: 0
- Yes I'm recommending WCAG2 now
- Gian Wild - Practical accessibility, April 1, 2011. "I had a client ring me yesterday, wanting to know if they should be trying to comply with WCAG1 or WCAG2. They had read my article: Why I'm sticking with WCAG1… for now, and wanted to check if my opinion still held. I wrote that post a little over a year ago, and although much has stayed the same (there are still few free accessibility testing tools that test against WCAG2 for example), much has changed. For example, the Australian Government Information Management Office (AGIMO) has released the Web Accessibility National Transition Strategy, the Australian Human Rights Commission (AHRC) have updated their Web Advisory Notes and most states in Australia now have formalised compliance to WCAG2 or are following the federal strategy. There is still a lot of confusion regarding WCAG2. It is still a very complex series of documents that require specialist interpretation..."
Added: 1 April 2011;
Page views: 653
Rating: 0
Votes: 0
- World Wide Web Access: Disability Discrimination Act Advisory Notes
- Version 4.0 - Australian Human Rights Commission, October 2010. "... The purpose of these Advisory Notes is to provide background information about accessibility and legal issues, as well as advice about how web designers and website owners can minimise the possibility of disability discrimination without sacrificing the richness and variety of communication offered by the web and web-based technologies. This new version (version 4.0) includes specific advice about a transition to WCAG 2.0..."
Added: 29 November 2010;
Page views: 914
Rating: 0
Votes: 0
- Understanding WCAG 2.0
- A guide to understanding and implementing Web Content Accessibility Guidelines 2.0. W3C Working Group Note, 14 October 2010. "Abstract - This document, "Understanding WCAG 2.0," is an essential guide to understanding and using Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. It is part of a series of documents that support WCAG 2.0. Please note that the contents of this document are informative (they provide guidance), and not normative (they do not set requirements for conforming to WCAG 2.0). See Web Content Accessibility Guidelines (WCAG) Overview for an introduction to WCAG, supporting technical documents, and educational material. WCAG 2.0 establishes a set of Success Criteria to define conformance to the WCAG 2.0 Guidelines. A Success Criterion is a testable statement that will be either true or false when applied to specific Web content. "Understanding WCAG 2.0" provides detailed information about each Success Criterion, including its intent, the key terms that are used in the Success Criterion, and how the Success Criteria in WCAG 2.0 help people with different types of disabilities. This document also provides examples of Web content that meet the success criterion using various Web technologies (for instance, HTML, CSS, XML), and common examples of Web content that does not meet the success criterion. This document indicates specific techniques to meet each Success Criterion. Details for how to implement each technique are available in Techniques for WCAG 2.0, but "Understanding WCAG 2.0" provides the information about the relationship of each technique to the Success Criteria. Techniques are categorized by the level of support they provide for the Success Criteria. "Sufficient techniques" are sufficient to meet a particular Success Criterion (either by themselves or in combination with other techniques), while other techniques are advisory and therefore optional. None of the techniques are required to meet WCAG 2.0, although some may be the only known method if a particular technology is used. "Advisory techniques" are not sufficient to meet the Success Criteria on their own (because they are not testable or provide incomplete support) but it is encouraged that authors follow them when possible to provide enhanced accessibility. Another support category is "Common Failures", which describe authoring practices known to cause Web content not to conform to WCAG 2.0. Although failures provide advisory information about certain authoring practices, authors must avoid those practices in order to meet the WCAG 2.0 Success Criteria..."
Added: 21 October 2010;
Page views: 870
Rating: 0
Votes: 0
- Techniques for WCAG 2.0
- Techniques and Failures for Web Content Accessibility Guidelines 2.0. W3C Working Group Note, 14 October 2010. "Abstract - "Techniques for WCAG 2.0" provides information to Web content developers who wish to satisfy the success criteria of Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. Techniques are specific authoring practices that may be used in support of the WCAG 2.0 success criteria. This document provides "General Techniques" that describe basic practices that are applicable to any technology, and technology-specific techniques that provide information applicable to specific technologies. Use of the techniques provided in this document makes it easier for Web content to demonstrate conformance to WCAG 2.0 success criteria than if these techniques are not used. Besides the techniques provided in this document, there may be other techniques that can be used to implement conformance to WCAG 2.0. The WCAG WG encourages submission of such techniques so they can be considered for inclusion in this document, in order to make the set of techniques maintained by the WCAG WG as comprehensive as possible..."
Added: 21 October 2010;
Page views: 576
Rating: 0
Votes: 0
- New and Improved WCAG 2.0 Techniques
- by Shawn Henry. W3C Blog, October 14, 2010. "Today W3C WAI published updated Techniques for WCAG 2.0 and Understanding WCAG 2.0, following a public review and comment period... etailed guidance, including technology-specific guidance, on meeting WCAG 2.0 is provided in the following supporting documents: Techniques for WCAG 2.0 - guidance for developers with general and technology-specific examples, including for HTML/XHTML, CSS, scripting, multimedia, Flash, and WAI-ARIA; Understanding WCAG 2.0 - includes the intent of the guideline or success criterion; how it helps people with different disabilities, browser and assistive technology support notes, examples, and resources..."
Added: 21 October 2010;
Page views: 892
Rating: 0
Votes: 0
- Call for Review: WCAG 2.0 Techniques Draft Updates
- by Shawn Lawton Henry. W3C, 8 July 2010. "The W3C WAI announces a Call for Review of updates to two supporting documents for Web Content Accessibility Guideline (WCAG) 2.0. This is not an update to WCAG 2.0, which is a stable document. The supporting documents (W3C Notes) are updated periodically to reflect current practices and technologies. The existing Techniques and Understanding documents remain in place as W3C Notes while the separate draft updates are under review and the WCAG Working Group addresses comments. The following draft updates are available for review as Editors' Drafts: Techniques for WCAG 2.0 Editors' Draft; Understanding WCAG 2.0 Editors' Draft.."
Added: 9 July 2010;
Page views: 677
Rating: 0
Votes: 0
- User Agent Accessibility Guidelines (UAAG) 2.0: Updated Working Draft
- W3C, 23 July 2009. "The User Agent Accessibility Guidelines Working Group has published an updated Working Draft of the User Agent Accessibility Guidelines (UAAG) 2.0. UAAG defines how browsers, media players, and other "user agents" should support accessibility for people with disabilities and work with assistive technologies..."
Added: 30 July 2009;
Page views: 1,189
Rating: 0
Votes: 0
- Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG): Overview
- W3C Working Group Note, 9 July 2009. "Abstract - This technical report describes the similarities and differences between the requirements in Web Content Accessibility Guidelines (WCAG) and Mobile Web Best Practices 1.0 (MWBP). Introductory information and links to related documents are in Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices..."
Added: 13 July 2009;
Page views: 1,488
Rating: 0
Votes: 0
- New Accessibility Guidelines Part IV: Robustness
- by Joseph C. Dolson. Practical eCommerce, May 22, 2009. "This article addresses 'robustness', and is part four in a series discussing the impact of WCAG 2.0 on your website. The fourth principle of the Web Content Accessibility Guidelines requires new web documents to be 'robust'. Robustness, future-proofing, user-agent independence, accessibility-supported: All are terms that suggest the same basic idea that your documents should follow standard, supported models for web document types. In many ways, this is the simplest and most testable requirement of the WCAG, but the details can be quite complicated..."
Added: 28 May 2009;
Page views: 1,181
Rating: 0
Votes: 0
- New Accessibility Guidelines Part III: Understandability
- by Joseph C. Dolson. Practical eCommerce, April 22, 2009. "This article addresses 'understandability', and is part three in a series discussing the impact of WCAG 2.0 on your website. The understandability of text is crucial to web accessibility. At broad levels, this means specifying text languages, explaining the meanings of jargon or idioms, and expanding abbreviations to clarify text. It's not just text that can present a barrier to accessibility, however. A lack of organizational predictability or proper error management can greatly decrease the accessibility of any website..."
Added: 28 May 2009;
Page views: 1,117
Rating: 0
Votes: 0
This category last updated: 16 October 2012
Translate, Search, Login and Options
Search
Translate
Mailing List
Enter your email address to subscribe or unsubscribe from the eGov What's New mailing list.
Email a Friend
Please enter email address of the person you wish to send this page to.
