Archive for Accessibility/Section 508
Accessibility/Section 508Published July 9, 2009 at 5:14 am 3 Comments
Two weeks ago, the National Federation of the Blind (NFB) and the American Council of the Blind (ACB) filed suit against Arizona State University (ASU) for planning to use Amazon’s Kindle e-book reader as a means to distribute textbooks to students. While the latest version Kindle DX has text-to-speech capability for e-books, strangely the Kindle
read more..
Accessibility/Section 508Published May 1, 2009 at 11:34 am No Comments
WebAIM has conducted a screen reader survey from Dec 08 – Jan 09 with over 1000 responses mostly from users who use a screen reader on a day-to-day basis. It was interesting to see that JAWS is still the predominant screen reader (74% of respondents), while competitor WindowEyes comes in second (23%). This makes sense,
read more..
Accessibility/Section 508Published February 20, 2009 at 2:41 pm No Comments
A good way of staying on top of what’s happening with accessibility is to have a nice list of RSS feeds to give you the latest news at a glance. Here are the ones I like to review on a regular basis: Webstandards.org National Center on Disability and Access to Education Google News feed “accessibility
read more..
Accessibility/Section 508Published February 3, 2009 at 1:30 pm No Comments
If you just received a contract that states Section 508 compliance as a requirement and you haven’t worked on such a project before, here are some quick tips to help you get on the right track. This information is geared towards project managers, developers, and designers who want to tackle such a project. The road
read more..
Accessibility/Section 508Published December 23, 2008 at 1:33 pm No Comments
When you create a new website or application, you probably have some ideas about how to make your pages accessible. If not, there are plenty of resources out there (a good starting point is webaim.org). If you develop a portal-type site that contains a lot of content in proprietary formats, such as Microsoft Word, or
read more..
Accessibility/Section 508Published December 5, 2008 at 3:51 pm No Comments
This post comes somewhat late, but I didn’t have my blog up in August this year. But this is an important milestone for the legal aspect of Web Accessibility and will probably bring accessibility into the requirements process of more and more web sites, especially shopping sites. And in general, it should be on the
read more..
Accessibility/Section 508 Web DesignPublished December 2, 2008 at 2:30 pm No Comments
It is refreshing to see John Allsopp’s smart article about “The Dao of Web Design” re-surface on the December 2008 issue of “A List Apart” (as editor’s choice - hat off to the editor). Constantly shifting and evolving web paradigms (then pull – now push; first Web 1.0 - soon Web 3.0) make us frown when Google returns results as old as
read more..
Accessibility/Section 508 SharepointPublished December 1, 2008 at 2:03 pm No Comments
It is annoying that Microsoft published MOSS 2007 without updating their terrible WYSIWYG editor. The default rich-text editor produces nasty HTML, still including lots of font tags and other long-deprecated stuff. Some developers have replaced this feature with the free version of aTelerik product, called radEditor Lite, free MOSS edition. There seem to be some
read more..
Accessibility/Section 508 SharepointPublished November 29, 2008 at 2:37 pm No Comments
While MOSS 2007 and WSS 3 come with some built-in accessibility features, some companies might be looking into improving the accessibility options of specific SharePoint features, such as individual web parts. To get familiar with the built-in accessibility, namely “Accessible Mode On,” consult Microsoft’s help at Microsoft Office/SharePoint. Some other Microsoft-authored starting points are: Deliver
read more..