Evaluating web sites for accessibility with Firefox Patrick H. Lauke

1
Evaluating web sites for accessibility with
FirefoxPatrick H. Lauke
Manchester Digital Accessibility Working Group
(MDAWG) - 1/3/2006
2
Introduction

• What well cover
• no big secrets revealed
• short, pragmatic tips on WCAG 1.0 manual checks
• live version of short article originally
  published on Ariadne
• time permitting short look at TAW3 tool to
  record check results

3
Automated validators

• The infamous Bobby(now WebXact)
• Automated accessibility checkers are dumb.
• Bobby and co. are just a tool and do not
  replace human judgement and checks.
• False positives, false negatives.
• All my images have an ALTernate text of
  imageis that accessible?
• Some tools do aknowledge that manual testing is
  required

4
Firefox Web Developer Toolbar

• Mozilla Firefox combined with Web Developer
  Toolbar
• cheap (free) and easy way to assist in testing
• http//www.mozilla.com/firefox/
• http//chrispederick.com/work/webdeveloper/

5

• Checkpoint 1.1Provide a text equivalent for
  every non-text element
• Outline Images Without Alt Attribute
• Outline Images With Empty Alt Attribute
• Replace Images With Alt Attributes

6

• Checkpoint 3.2Create documents that validate to
  published formal grammars
• Validate CSS
• Validate HTML
• Validate Local CSS
• Validate Local HTML

7

• Checkpoint 3.3Use style sheets to control layout
  and presentation
• Disable Styles All Styles

8

• Checkpoint 3.5Use header elements to convey
  document structure and use them according to
  specification
• Checkpoint 3.6Mark up lists and list items
  properly
• Checkpoint 3.7Mark up quotations. Do not use
  quotation markup for formatting effects such as
  indentation
• Options Show element names when outlining
  elements
• Outline Block Level Elements

9

• Checkpoint 4.2Specify the expansion of each
  abbreviation or acronym in a document where it
  first occurs
• Outline Custom Elements ABBR and ACRONYM

10

• Checkpoint 5.3Do not use tables for layout
  unless the table makes sense when linearised
• Miscellaneous Linearise Page

11

• Checkpoint 6.1Organise documents so they may be
  read without style sheets. For example, when an
  HTML document is rendered without associated
  style sheets, it must still be possible to read
  the document
• Same as 3.3

12

• Checkpoint 6.3Ensure that pages are usable when
  scripts, applets, or other programmatic objects
  are turned off or not supported
• Disable Java
• Disable Javascript

13

• Checkpoint 6.4For scripts and applets, ensure
  that event handlers are input device-independent
• Checkpoint 9.3For scripts, specify logical event
  handlers rather than device-dependent event
  handlers
• Just use keyboard

14

• Checkpoint 9.4Create a logical tab order through
  links, form controls, and objects
• Linearise / disable styles / use keyboard

15

• Checkpoint 9.5Provide keyboard shortcuts to
  important links (including those in client-side
  image maps), form controls, and groups of form
  controls
• Information Display Accesskeys

16

• Checkpoint 11.2Avoid deprecated features of W3C
  technologies.
• Outline deprecated elements

17

• Checkpoint 12.4Associate labels explicitly with
  their controls
• Use mouse
• Forms View Form Information

18
Other useful tools

• Gez Lemons table inspector
• http//juicystudio.com/article/firefox-table-inspe
  ctor.php
• Gezs colour contrast analyser
• http//juicystudio.com/article/colour-contrast-ana
  lyser-firefox-extension.php
• TAW3 to record manual check findings
• http//www.ariadne.ac.uk/issue46/lauke/
• http//www.tawdis.net/taw3/cms/en

19
(No Transcript)