Accessibility and Security Roundup
For those of you planning new web projects in the new year, here are some pointers for accessibility resources to keep in mind. Accessibility is not a marginal issue—by enabling web site users to interact with your web application without hindrance increases trust, improves the accuracy of information submitted and reduces errors. These are all aspects of software quality.
Accessibility sometimes get lumped in solely with talk of disability. But lack of special aids or adaptions haven't been a significant barrier to internet usage by disabled people. Like everyone else it's cost, lack of skills and confidence. So what should we be doing for all users?
BSI British Standards is now inviting comments on a new Draft for Public Comment (DPC) BS 8878:2009, the draft standard on accessible websites (registration required). Based on the Publicly Available Specification (PAS) PAS 78:2006 Guide to Good Practice in Commissioning Accessible Websites which will ultimately be withdrawn, the final date for submissions is the end of January 2009 with an aim for the standard to be published in summer 2009. Thankfully, BSI have now published the complete documents in PDF and Word format (no registration required), since the mechanism for reading and providing feedback is an excellent example of an unusable application! The draft standard is summarised by the document's statement:
The goal of any web project should be to create web experiences that are accessible, usable and enjoyable.
I'd add "safe" to the list.
Last week saw the Web Content Accessibility Guidelines 2.0 (WCAG) becoming a full W3C Recommendation. Key reference WCAG 2.0 Documents are:
- WCAG 2.0 at a Glance
- How to Meet WCAG 2.0: A Customizable Quick Reference
- Understanding WCAG 2.0
- Techniques for WCAG 2.0
- How to Update Your Web Site to WCAG 2.0
- Essential Components of Web Accessibility
These aspects are increasingly being highlighted in web project contracts and specifications - and system architects, designers, developers and testers need to know how to build compliant applications. It is important to understand that users won't just be using popular modern web browsers; all sorts of devices will be utilised. The information security shouldn't be less for anyone—regardless of their access method.
One aspect of WCAG 2.0 is maximising compatibility with current and future user agents, including assistive technologies. A related project from the Accessibility Interoperability Alliance (AIA) worth monitoring is concerning Common Keyboard Shortcuts for Accessible Technology (AT) Products Used with Web Browsers along with the Open Web Application Security Project (OWASP) Intrinsic Security Working Group's efforts on introducing more useful security into all web browsers.
Posted on: 16 December 2008 at 12:18 hrs

Comments are filtered automatically and should appear shortly after they been checked.