Categories
podcast

Podcast 61: Accessibility Statements

Download Web Axe Episode 61 (Accessibility Statements)

News

Listener’s Comments

Main Segment Topics

  • What is an accessibility statement?
  • Should an accessibility statement be on my web site?
  • Where should I provide links to the accessibility statement?
  • What should be included in the accessibility statement?
    • A brief description of the policy.
    • How to report failures on the site.
    • Details of the functions built-in to the site.
    • Information on browser options.
    • The standards used in the building of the site.
    • The verification processes used.
    • Links to further information.

Related Links

Categories
law screenreader

JAWS and Target

JAWS

The trial version of JAWS has always been a hassle to use for testing with its 40 minute sessions and required reboots. In the WebAIM blog, Jared Smith points out that the license infers that you cannot use the demo version of JAWS for web development purposes. Someone in the comments of the post suggests using Window-Eyes.

Target vs. NFB

Early this month, it was reported that Target lost an appeal of the class action status of the lawsuit by the National Federation of the Blind.

Categories
administrative

Donate to Web Axe

You can now donate to Web Axe. Help keep the podcast blog going.

Categories
podcast

Podcast 60: Web Axe 2007 Year in Review

Happy New Year! Dennis highlights and discusses numerous podcasts and news/blog events about web accessibility in the last year.

Download Web Axe Episode 60 (2007 Year in Review)

News

Categories
expert standards

Supporting Standards that Support Accessibility

In his article/post Supporting Standards that Support Accessibility, Joe Dolson examines the (non) relationship between web standards and web accessibility. He makes the excellent point that following web standards is not the same as providing web accessibility, although generally standards are beneficial. Joe discusses examples of where standards can actually make a negative impact on the accessibility of a web page, and where rarely used code can be beneficial.