-
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: WAI-ARIA
aViewer 2013
Here at the paciello group we are very excited by the improvements being made to our aViewer accessibility API information inspection tool. We want to share the updated aViewer with you and in the process elicit your feedback on the … Continue reading
Using WAI-ARIA Landmarks – 2013
tl;dr Adding ARIA landmarks to your existing site, or to a site you are developing, provides useful global navigation features and aids understanding of content structure for users. Over time the necessity of explicitly assigning landmarks will lessen as browsers … Continue reading
Posted in Assistive Technology, HTML, HTML 5.1, HTML5, landmark roles, WAI-ARIA, Web Accessibility
22 Comments
Notes on accessibility of Microsoft.com’s new home page
Microsoft.com has a new home page. It uses HTML5 and ARIA. I have done a quick review of their usage. There are a few issues…
Posted in Assistive Technology, HTML5, microsoft, W3C Validator, WAI-ARIA, Web Accessibility
26 Comments
latest aViewer alpha 2012
Refer to: aViewer 2013
Visualising browser accessibility bugs
On revisiting what I believe to be a simple to fix bug, filed in January on Webkit’s ARIA implementation, unsurprisingly I found it not yet fixed. Part of the reason this occurs is because there is limited resources available and … Continue reading
Posted in Assistive Technology, Google Chrome, HTML, HTML5, Safari, WAI-ARIA, Web Accessibility, webkit
5 Comments