- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 17 Jul 2008 12:58:55 -0500
- To: <w3c-wai-ua@w3.org>
---------- Forwarded message ---------- From: Markku Hakkinen <mhakkinen@acm.org> Date: Thu, Jul 17, 2008 at 1:57 PM Subject: Rationale First Pass (1.1, 3.1, 4.1) To: w3c-wai-ua@w3.org Using ATAG as starting point, here are an initial set of short rationale statments. 2.1 and 5.1 are proving a bit more challenging. Guideline 1.1 Observe operating environment conventions [Techniques] Rationale: Following platform accessibility conventions lessens the need for assistive technologies to make special-purpose accommodations. Also, people who are familiar with the accessibility conventions employed by a specific platform will find applications that adhere to those conventions easier to use. Guideline 2.1 Programmatic access to HTML/XML infoset [Techniques] Rationale: @@tbd@@ Guideline 3.1 Provide text alternatives for non-text components [Techniques] Rationale: Providing text alternatives for non-text components allow for presentation in other forms people need, such as large print, braille, speech, symbols or simpler language. Guideline 4.1 Ensure full keyboard access [Techniques] Rationale: Full keyboard accessibility provides access for people with limited mobility and people with visual disabilities, who cannot rely on hand-eye coordination for navigating the user interface. Guideline 5.1 Help users avoid unnecessary messages [Techniques] Rationale: @@tbd@@
Received on Thursday, 17 July 2008 18:04:03 UTC