-
Archives
- May 2013
- March 2013
- February 2013
- January 2013
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- February 2011
- January 2011
- November 2010
- October 2010
- September 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- October 2009
- September 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
-
Meta
Category Archives: WCAG 2.0
Examples of ‘skip links’ on some bank sites
While discussing long descriptions on the HTML working group mailing list I took a look at how some sites provide skip links as an example of contingent visible display of content as a more palatable design concept for some accessibility … Continue reading
Posted in accessibility testing, WCAG 2.0, Web Accessibility
3 Comments
Notes on accessible CSS image sprites
The issue of CSS image sprites has been raised again on the Web Accessibility Initiative Interest Group mailing list. Here is the advice we provide on the issue:
Pro HTML5 Accessibility – review
A new book Pro HTML5 Accessibility by Joshue O’connor.
Posted in Assistive Technology, HTML, HTML5, WAI-ARIA, WCAG 2.0, Web Accessibility
Tagged review
4 Comments
What’s ‘large text’ in WCAG 2.0 parlance?
I put together an example page, mainly for my own use, providing some examples of what in WCAG 2.0 terms is considered large and small text. WCAG 2.0 provides the font measurements in terms of points, so I initially used … Continue reading
Posted in accessibility testing, contrast analyser, CSS, HTML, HTML5, iPhone, mobile, WCAG 2.0, Web Accessibility
5 Comments
how to remove CSS outlines in an accessible manner?
Anybody with any real world accessibility experience knows that using CSS :focus {outline:none} as recommended in the WHATWG HTML living standard is not a solution to any problem, it only replaces one accessibility issue with another. This why I worked … Continue reading