- From: Michael Gower <michael.gower@ca.ibm.com>
- Date: Wed, 11 Apr 2018 13:56:30 +0000
- To: Shadi Abou-Zahra <shadi@w3.org>
- Cc: Andrew Kirkpatrick <akirkpat@adobe.com>, "Bailey, Bruce" <bailey@access-board.gov>, Kathy Wahlbin <kathy@interactiveaccessibility.com>, Katie Haritos-Shea <katie.haritos-shea@deque.com>, Katie Haritos-Shea <ryladog@gmail.com>, WCAG WG <w3c-wai-gl@w3.org>
- Message-Id: <OF61EF4394.D01C2F9C-ON8825826C.004B385C-8825826C.004C940D@notes.na.collabserv.c>
We took the Input Methods guideline from Kathy's F2F wording. We're aware
keyboard is an input, but Keyboard Accessible is a baseline guideline that
requires all functionality to be operable by keyboard. There are no other
means of input that have this requirement. So practically, we need a
separate category for addressing non-keyboard operation. Folks didn't like
the use of "non-keyboard" in the guideline name itself.
Perhaps this difference can be clarified through some changes to the short
description. A couple of suggestions:
Make it easier for users to operate functionality using non-keyboard
inputs
Make it easier for users to operate functionality through various inputs
in addition to keyboard
Michael Gower
IBM Accessibility
Research
1803 Douglas Street, Victoria, BC V8T 5C3
gowerm@ca.ibm.com
voice: (250) 220-1146 * cel: (250) 661-0098 * fax: (250) 220-8034
From: Shadi Abou-Zahra <shadi@w3.org>
To: Kathy Wahlbin <kathy@interactiveaccessibility.com>, Michael Gower
<michael.gower@ca.ibm.com>, Katie Haritos-Shea <ryladog@gmail.com>
Cc: "Bailey, Bruce" <bailey@access-board.gov>, Katie Haritos-Shea
<katie.haritos-shea@deque.com>, WCAG WG <w3c-wai-gl@w3.org>, Andrew
Kirkpatrick <akirkpat@adobe.com>
Date: 2018-04-11 05:21 AM
Subject: Re: WCAG 2.1 Guideline Suggested Changes
[moving this thread back to the list for others to follow]
On 11/04/2018 01:56, Kathy Wahlbin wrote:
> Hi –
>
> Thank you for pulling this together. Overall I think it is good but I
> don’t like “input methods”. The reason I don’t is because keyboard is
> also an input method. I like having the three SCs under pointer.
We have "input methods" in all three proposals summarized by Andrew:
-
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.w3.org_Archives_Public_w3c-2Dwai-2Dgl_2018AprJun_0230&d=DwID-g&c=jf_iaSHvJObTbx-siA1ZOg&r=o0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ&m=ranJttITMbcdRl9_7dVZqyIcWL-kdV_8j3Sm7YMcMUM&s=qNMn9dZ66sBOuEsYqtWII-BzraUhPFXJ7PGRbSLkW2o&e=
I agree with Alastair's concern about adding too many Guidelines, even
though I was tossing in Kathy's idea for our CSUN presentation (listed
as "Katie email").
I like both Andrew's and Mike's proposals equally. Would it make sense
to rename Guideline 2.5 "Input Methods" in either proposals to "Sensor
Accessible"? While keyboards are technically types of sensors, I think
that most people would not call them that. However, pointers and most
other input types are probably more commonly considered to be sensors.
The description for the proposed Guideline 2.5 "Sensor Accessible" can
remain as suggested by Andrew: "Make it easier for users to operate
functionality using different input types."
Best,
Shadi
> Kathy
>
> *From:* Michael Gower <michael.gower@ca.ibm.com>
> *Sent:* Tuesday, April 10, 2018 6:43 PM
> *To:* Katie Haritos-Shea <ryladog@gmail.com>
> *Cc:* Bailey, Bruce <bailey@access-board.gov>; Kathy Wahlbin
> <kathy@interactiveaccessibility.com>; Katie Haritos-Shea
> <katie.haritos-shea@deque.com>; Shadi Abou-Zahra <shadi@w3.org>
> *Subject:* Re: WCAG 2.1 Guideline Suggested Changes
>
> Sorry, meant Kathy not Kim!
>
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC V8T 5C3
> gowerm@ca.ibm.com <mailto:gowerm@ca.ibm.com>
> voice: (250) 220-1146 * cel: (250) 661-0098 * fax: (250) 220-8034
>
>
>
> From: Michael Gower/CanWest/IBM
> To: Katie Haritos-Shea <ryladog@gmail.com <mailto:ryladog@gmail.com>>
> Cc: "Bailey, Bruce" <bailey@access-board.gov
> <mailto:bailey@access-board.gov>>, Kathy Wahlbin
> <kathy@interactiveaccessibility.com
> <mailto:kathy@interactiveaccessibility.com>>, Katie Haritos-Shea
> <katie.haritos-shea@deque.com <mailto:katie.haritos-shea@deque.com>>,
> Shadi Abou-Zahra <shadi@w3.org <mailto:shadi@w3.org>>, WCAG
> <w3c-wai-gl@w3.org <mailto:w3c-wai-gl@w3.org>>
> Date: 2018-04-10 03:42 PM
> Subject: Re: WCAG 2.1 Guideline Suggested Changes
>
> ------------------------------------------------------------------------
>
>
>
> Katie and I went over what Kim, she and I had drummed up independently,
> and we think we've come up with a joint approach that is very tenable.
>
> Key points:
>
> * Retains almost entire existing guideline structure (one guideline
> renamed; one removed)
> * Only moving 4 SCs from current editor's draft
> *
>
>
> Changes from existing editor's draft:
>
> * rename the existing Pointer Accessible guideline to Input Methods
> o remove the word "pointer" from the existing short description of
> the guideline to now read: "Make it easier for users to operate
> functionality."
> * remove Additional Sensor Inputs (put Motion Actuation under Input
> Methods)
> * move Orientation to Adaptable -- where it fits well: "Create content
> that can be presented in different ways (for example simpler layout)
> without losing information or structure."
> * move Character Key Shortcuts to Keyboard Accessible. It is where it
> fits practically and linguistically; speech operability rides on top
> of the keyboard API.
> * move Label in Name to Compatible, where it fits well with the second
> Intention ("exposing information in the content in standard ways
> that assistive technologies can recognize and interact with.")
> *
> *
>
> In the below table, in the second column, 2.1 guidelines are in bold.
> Changes from the existing editor's draft are in blue and bold with the
> old number in parentheses)
> *WCAG 2.1 Guideline Suggested Changes*
>
> Current
>
>
>
> Suggested
>
> *1. Perceivable*
> *1.1 Text Alternatives*
>
> 1.1.1 Non-text Content
>
> 1.2 Time-based Media
>
> 1.2.1 Audio-only and Video-only (Prerecorded)
>
> 1.2.2 Captions (Prerecorded)
>
> 1.2.3 Audio Description or Media Alternative (Prerecorded)
>
> 1.2.4 Captions (Live)
>
> 1.2.5 Audio Description (Prerecorded)
>
> 1.2.6 Sign Language (Prerecorded)
>
> 1.2.7 Extended Audio Description (Prerecorded)
>
> 1.2.8 Media Alternative (Prerecorded)
>
> 1.2.9 Audio-only (Live)
>
>
> *1.3 Adaptable*
>
> 1.3.1 Info and Relationships
>
> 1.3.2 Meaningful Sequence
>
> 1.3.3 Sensory Characteristics
>
> 1.3.4 Identify Common Purpose
>
> 1.3.5 Identify Purpose
>
>
> *1.4 Distinguishable*
>
> 1.4.1 Use of Color
>
> 1.4.2 Audio Control
>
> 1.4.3 Contrast (Minimum)
>
> 1.4.4 Resize text
>
> 1.4.5 Images of Text
>
> 1.4.6 Contrast (Enhanced)
>
> 1.4.7 Low or No Background Audio
>
> 1.4.8 Visual Presentation
>
> 1.4.9 Images of Text (No Exception)
>
> 1.4.10 Reflow
>
> 1.4.11 Non-text Contrast
>
> 1.4.12 Text Spacing
>
> 1.4.13 Content on Hover or Focus
>
>
>
> *1. Perceivable*
> *1.1 Text Alternatives*
>
> 1.1.1 Non-text Content
>
> 1.2 Time-based Media
>
> 1.2.1 Audio-only and Video-only (Prerecorded)
>
> 1.2.2 Captions (Prerecorded)
>
> 1.2.3 Audio Description or Media Alternative (Prerecorded)
>
> 1.2.4 Captions (Live)
>
> 1.2.5 Audio Description (Prerecorded)
>
> 1.2.6 Sign Language (Prerecorded)
>
> 1.2.7 Extended Audio Description (Prerecorded)
>
> 1.2.8 Media Alternative (Prerecorded)
>
> 1.2.9 Audio-only (Live)
>
>
> *1.3 Adaptable*
>
> 1.3.1 Info and Relationships
>
> 1.3.2 Meaningful Sequence
>
> 1.3.3 Sensory Characteristics
>
> *1.3.4 Identify Input Purpose*
>
> *1.3.5 Identify Purpose*
>
> *1.3.6 Orientation (was 2.6.2)*
>
>
> *1.4 Distinguishable*
>
> 1.4.1 Use of Color
>
> 1.4.2 Audio Control
>
> 1.4.3 Contrast (Minimum)
>
> 1.4.4 Resize text
>
> 1.4.5 Images of Text
>
> 1.4.6 Contrast (Enhanced)
>
> 1.4.7 Low or No Background Audio
>
> 1.4.8 Visual Presentation
>
> 1.4.9 Images of Text (No Exception)
>
> *1.4.10 Reflow*
>
> *1.4.11 Non-text Contrast*
>
> *1.4.12 Text Spacing*
>
> *1.4.13 Content on Hover or Focus*
>
> *2. Operable*
> *2.1 Keyboard Accessible*
>
> 2.1.1 Keyboard
>
> 2.1.2 No Keyboard Trap
>
> 2.1.3 Keyboard (No Exception)
>
>
> *2.2 Enough Time*
>
> 2.2.1 Timing Adjustable
>
> 2.2.2 Pause, Stop, Hide
>
> 2.2.3 No Timing
>
> 2.2.4 Interruptions
>
> 2.2.5 Re-authenticating
>
> 2.2.6 Timeouts
>
> 2.2.7 Animation from Interactions
>
>
> *2.3 Seizures*
>
> 2.3.1 Three Flashes or Below Threshold
>
> 2.3.2 Three Flashes
>
>
> *2.4 Navigable*
>
> 2.4.1 Bypass Blocks
>
> 2.4.2 Page Titled
>
> 2.4.3 Focus Order
>
> 2.4.4 Link Purpose (In Context)
>
> 2.4.5 Multiple Ways
>
> 2.4.6 Headings and Labels
>
> 2.4.7 Focus Visible
>
> 2.4.8 Location
>
> 2.4.9 Link Purpose (Link Only)
>
> 2.4.10 Section Headings
>
> 2.4.11 Character Key Shortcuts
>
> 2.4.12 Label in Name
>
>
> *2.5 Pointer Accessible*
>
> 2.5.1 Pointer Gestures
>
> 2.5.2 Pointer Cancellation
>
> 2.5.3 Target Size
>
> 2.5.4 Concurrent Input Mechanisms
>
>
> *2.6 Additional sensor inputs*
>
> 2.6.1 Motion Actuation
>
> 2.6.2 Orientation
>
>
>
> *2. Operable*
> *2.1 Keyboard Accessible*
>
> 2.1.1 Keyboard
>
> 2.1.2 No Keyboard Trap
>
> 2.1.3 Keyboard (No Exception)
>
> *2.1.4 Character Key Shortcuts (was 2.4.11)*
>
>
> *2.2 Enough Time*
>
> 2.2.1 Timing Adjustable
>
> 2.2.2 Pause, Stop, Hide
>
> 2.2.3 No Timing
>
> 2.2.4 Interruptions
>
> 2.2.5 Re-authenticating
>
> *2.2.6 Timeouts*
>
>
> *2.3 Seizures **and Physical Reactions*
>
> 2.3.1 Three Flashes or Below Threshold
>
> 2.3.2 Three Flashes
>
> *2.3.3 Animation from Interactions (was 2.2.7)*
>
>
> *2.4 Navigable*
>
> 2.4.1 Bypass Blocks
>
> 2.4.2 Page Titled
>
> 2.4.3 Focus Order
>
> 2.4.4 Link Purpose (In Context)
>
> 2.4.5 Multiple Ways
>
> 2.4.6 Headings and Labels
>
> 2.4.7 Focus Visible
>
> 2.4.8 Location
>
> 2.4.9 Link Purpose (Link Only)
>
> 2.4.10 Section Headings
>
>
> *2.5 Input Methods*
>
> *2.5.1 Pointer Gestures*
>
> *2.5.2 Pointer Cancellation*
>
> *2.5.3 Target Size*
>
> *2.5.4 Concurrent Input Mechanisms*
>
> *2.5.5 Motion Actuation (was 2.6.1)*
>
> **
>
> *3. Understandable*
> *3.1 Readable*
>
> 3.1.1 Language of Page
>
> 3.1.2 Language of Parts
>
> 3.1.3 Unusual Words
>
> 3.1.4 Abbreviations
>
> 3.1.5 Reading Level
>
> 3.1.6 Pronunciation
>
>
> *3.2 Predictable*
>
> 3.2.1 On Focus
>
> 3.2.2 On Input
>
> 3.2.3 Consistent Navigation
>
> 3.2.4 Consistent Identification
>
> 3.2.5 Change on Request
>
> 3.2.6 Status Changes
>
>
> *3.3 Input Assistance*
>
> 3.3.1 Error Identification
>
> 3.3.2 Labels or Instructions
>
> 3.3.3 Error Suggestion
>
> 3.3.4 Error Prevention (Legal, Financial, Data)
>
> 3.3.5 Help
>
> 3.3.6 Error Prevention (All)
>
>
>
> *3. Understandable*
> *3.1 Readable*
>
> 3.1.1 Language of Page
>
> 3.1.2 Language of Parts
>
> 3.1.3 Unusual Words
>
> 3.1.4 Abbreviations
>
> 3.1.5 Reading Level
>
> 3.1.6 Pronunciation
>
>
> *3.2 Predictable*
>
> 3.2.1 On Focus
>
> 3.2.2 On Input
>
> 3.2.3 Consistent Navigation
>
> 3.2.4 Consistent Identification
>
> 3.2.5 Change on Request
>
>
> *3.3 Input Assistance*
>
> 3.3.1 Error Identification
>
> 3.3.2 Labels or Instructions
>
> 3.3.3 Error Suggestion
>
> 3.3.4 Error Prevention (Legal, Financial, Data)
>
> 3.3.5 Help
>
> 3.3.6 Error Prevention (All)
>
> *4. Robust*
> *4.1 Compatible*
>
> 4.1.1 Parsing
>
> 4.1.2 Name, Role, Value
>
>
>
> *4. Robust*
> *4.1 Compatible*
>
> 4.1.1 Parsing
>
> 4.1.2 Name, Role, Value
>
> *4.1.3 Status Changes*
>
> *4.1.4 Label in Name (was 2.4.12)*
>
> **
>
> I've made the changes in this document, and shown what was changed from
> the prior version.
>
> [attachment "WCAG 2.1 Guideline Suggested Changes_mike.docx" deleted by
> Michael Gower/CanWest/IBM]
>
>
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC V8T 5C3
> gowerm@ca.ibm.com <mailto:gowerm@ca.ibm.com>
> voice: (250) 220-1146 * cel: (250) 661-0098 * fax: (250) 220-8034
>
>
>
>
> From: Katie Haritos-Shea <ryladog@gmail.com <mailto:ryladog@gmail.com>>
> To: Michael Gower <michael.gower@ca.ibm.com
> <mailto:michael.gower@ca.ibm.com>>, "Bailey, Bruce"
> <bailey@access-board.gov <mailto:bailey@access-board.gov>>, Shadi
> Abou-Zahra <shadi@w3.org <mailto:shadi@w3.org>>, Katie Haritos-Shea
> <katie.haritos-shea@deque.com <mailto:katie.haritos-shea@deque.com>>,
> WCAG <w3c-wai-gl@w3.org <mailto:w3c-wai-gl@w3.org>>, Kathy Wahlbin
> <kathy@interactiveaccessibility.com
> <mailto:kathy@interactiveaccessibility.com>>
> Date: 2018-04-10 02:37 PM
> Subject: WCAG 2.1 Guideline Suggested Changes
>
> ------------------------------------------------------------------------
>
>
>
>
> Hello,
>
> I am sending this WORD document, but have also pasted below the idea
> mock-up of more specific Guidelines for 2.1 from Shadi and Kathy's CSUN
> talk. Also, let me know if I have missed anything. It incorporates CFCs
> for moving Status Changes and Animations from Interactions and the name
> change to SC 1.3.4 and GL 2.3.
>
> Please comments and suggest language text for the Guidelines themselves.
>
> *WCAG 2.1 Guideline Suggested Changes*
>
> Current
>
>
>
> Suggested
>
> *1. Perceivable*
> *1.1 Text Alternatives*
>
> 1.1.1 Non-text Content
>
> 1.2 Time-based Media
>
> 1.2.1 Audio-only and Video-only (Prerecorded)
>
> 1.2.2 Captions (Prerecorded)
>
> 1.2.3 Audio Description or Media Alternative (Prerecorded)
>
> 1.2.4 Captions (Live)
>
> 1.2.5 Audio Description (Prerecorded)
>
> 1.2.6 Sign Language (Prerecorded)
>
> 1.2.7 Extended Audio Description (Prerecorded)
>
> 1.2.8 Media Alternative (Prerecorded)
>
> 1.2.9 Audio-only (Live)
>
>
> *1.3 Adaptable*
>
> 1.3.1 Info and Relationships
>
> 1.3.2 Meaningful Sequence
>
> 1.3.3 Sensory Characteristics
>
> 1.3.4 Identify Common Purpose
>
> 1.3.5 Identify Purpose
>
>
> *1.4 Distinguishable*
>
> 1.4.1 Use of Color
>
> 1.4.2 Audio Control
>
> 1.4.3 Contrast (Minimum)
>
> 1.4.4 Resize text
>
> 1.4.5 Images of Text
>
> 1.4.6 Contrast (Enhanced)
>
> 1.4.7 Low or No Background Audio
>
> 1.4.8 Visual Presentation
>
> 1.4.9 Images of Text (No Exception)
>
> 1.4.10 Reflow
>
> 1.4.11 Non-text Contrast
>
> 1.4.12 Text Spacing
>
> 1.4.13 Content on Hover or Focus
>
>
>
> *1. Perceivable*
> *1.1 Text Alternatives*
>
> 1.1.1 Non-text Content
>
> 1.2 Time-based Media
>
> 1.2.1 Audio-only and Video-only (Prerecorded)
>
> 1.2.2 Captions (Prerecorded)
>
> 1.2.3 Audio Description or Media Alternative (Prerecorded)
>
> 1.2.4 Captions (Live)
>
> 1.2.5 Audio Description (Prerecorded)
>
> 1.2.6 Sign Language (Prerecorded)
>
> 1.2.7 Extended Audio Description (Prerecorded)
>
> 1.2.8 Media Alternative (Prerecorded)
>
> 1.2.9 Audio-only (Live)
>
>
> *1.3 Adaptable*
>
> 1.3.1 Info and Relationships
>
> 1.3.2 Meaningful Sequence
>
> 1.3.3 Sensory Characteristics
>
> *1.3.4 Identify Input Purpose*
>
> *1.3.5 Identify Purpose*
>
>
> *1.4 Distinguishable*
>
> 1.4.1 Use of Color
>
> 1.4.2 Audio Control
>
> 1.4.3 Contrast (Minimum)
>
> 1.4.4 Resize text
>
> 1.4.5 Images of Text
>
> 1.4.6 Contrast (Enhanced)
>
> 1.4.7 Low or No Background Audio
>
> 1.4.8 Visual Presentation
>
> 1.4.9 Images of Text (No Exception)
>
> *1.4.10 Reflow*
>
> *1.4.11 Non-text Contrast*
>
> *1.4.12 Text Spacing*
>
> *1.4.13 Content on Hover or Focus*
>
> *2. Operable*
> *2.1 Keyboard Accessible*
>
> 2.1.1 Keyboard
>
> 2.1.2 No Keyboard Trap
>
> 2.1.3 Keyboard (No Exception)
>
> 2.2 Enough Time
>
> 2.2.1 Timing Adjustable
>
> 2.2.2 Pause, Stop, Hide
>
> 2.2.3 No Timing
>
> 2.2.4 Interruptions
>
> 2.2.5 Re-authenticating
>
> 2.2.6 Timeouts
>
> 2.2.7 Animation from Interactions
>
>
> *2.3 Seizures*
>
> 2.3.1 Three Flashes or Below Threshold
>
> 2.3.2 Three Flashes
>
>
> *2.4 Navigable*
>
> 2.4.1 Bypass Blocks
>
> 2.4.2 Page Titled
>
> 2.4.3 Focus Order
>
> 2.4.4 Link Purpose (In Context)
>
> 2.4.5 Multiple Ways
>
> 2.4.6 Headings and Labels
>
> 2.4.7 Focus Visible
>
> 2.4.8 Location
>
> 2.4.9 Link Purpose (Link Only)
>
> 2.4.10 Section Headings
>
> 2.4.11 Character Key Shortcuts
>
> 2.4.12 Label in Name
>
>
> *2.5 Pointer Accessible*
>
> 2.5.1 Pointer Gestures
>
> 2.5.2 Pointer Cancellation
>
> 2.5.3 Target Size
>
> 2.5.4 Concurrent Input Mechanisms
>
>
> *2.6 Additional sensor inputs*
>
> 2.6.1 Motion Actuation
>
> 2.6.2 Orientation
>
>
>
> *2. Operable*
> *2.1 Keyboard Accessible*
>
> 2.1.1 Keyboard
>
> 2.1.2 No Keyboard Trap
>
> 2.1.3 Keyboard (No Exception)
>
> 2.2 Enough Time
>
> 2.2.1 Timing Adjustable
>
> 2.2.2 Pause, Stop, Hide
>
> 2.2.3 No Timing
>
> 2.2.4 Interruptions
>
> 2.2.5 Re-authenticating
>
> *2.2.6 Timeouts*
>
>
> *2.3 Seizures **and Physical Reactions*
>
> 2.3.1 Three Flashes or Below Threshold
>
> 2.3.2 Three Flashes
>
> *2.3.3 Animation from Interactions (was 2.2.7)*
>
>
> *2.4 Navigable*
>
> 2.4.1 Bypass Blocks
>
> 2.4.2 Page Titled
>
> 2.4.3 Focus Order
>
> 2.4.4 Link Purpose (In Context)
>
> 2.4.5 Multiple Ways
>
> 2.4.6 Headings and Labels
>
> 2.4.7 Focus Visible
>
> 2.4.8 Location
>
> 2.4.9 Link Purpose (Link Only)
>
> 2.4.10 Section Headings
>
>
> *2.5 Pointer Accessible*
>
> *2.5.1 Pointer Gestures*
>
> *2.5.2 Pointer Cancellation*
>
> *2.5.3 Target Size*
>
>
> *2.6 Speech Input*
>
> *2.6.1 Character Key Shortcuts (was 2.4.11)*
>
> *2.6.2 Label in Name (was 2.4.12)*
>
>
> *2.7 Input Methods*
>
> *2.7.1 Concurrent Input Mechanisms (was 2.5.4)*
>
> *2.7.2 Motion Actuation (was 2.6.1)*
>
>
> *2.8 Device Settings*
>
> *2.8.1 Orientation (was 2.6.2)*
>
> *3. Understandable*
> *3.1 Readable*
>
> 3.1.1 Language of Page
>
> 3.1.2 Language of Parts
>
> 3.1.3 Unusual Words
>
> 3.1.4 Abbreviations
>
> 3.1.5 Reading Level
>
> 3.1.6 Pronunciation
>
>
> *3.2 Predictable*
>
> 3.2.1 On Focus
>
> 3.2.2 On Input
>
> 3.2.3 Consistent Navigation
>
> 3.2.4 Consistent Identification
>
> 3.2.5 Change on Request
>
> 3.2.6 Status Changes
>
>
> *3.3 Input Assistance*
>
> 3.3.1 Error Identification
>
> 3.3.2 Labels or Instructions
>
> 3.3.3 Error Suggestion
>
> 3.3.4 Error Prevention (Legal, Financial, Data)
>
> 3.3.5 Help
>
> 3.3.6 Error Prevention (All)
>
>
>
> *3. Understandable*
> *3.1 Readable*
>
> 3.1.1 Language of Page
>
> 3.1.2 Language of Parts
>
> 3.1.3 Unusual Words
>
> 3.1.4 Abbreviations
>
> 3.1.5 Reading Level
>
> 3.1.6 Pronunciation
>
>
> *3.2 Predictable*
>
> 3.2.1 On Focus
>
> 3.2.2 On Input
>
> 3.2.3 Consistent Navigation
>
> 3.2.4 Consistent Identification
>
> 3.2.5 Change on Request
>
>
> *3.3 Input Assistance*
>
> 3.3.1 Error Identification
>
> 3.3.2 Labels or Instructions
>
> 3.3.3 Error Suggestion
>
> 3.3.4 Error Prevention (Legal, Financial, Data)
>
> 3.3.5 Help
>
> 3.3.6 Error Prevention (All)
>
> *4. Robust*
> *4.1 Compatible*
>
> 4.1.1 Parsing
>
> 4.1.2 Name, Role, Value
>
>
>
> *4. Robust*
> *4.1 Compatible*
>
> 4.1.1 Parsing
>
> 4.1.2 Name, Role, Value
>
> *4.1.3 Status Changes (was 3.2.6)*
>
>
>
> ** katie **
>
> *Katie Haritos-Shea **
> Principal ICT Accessibility Architect *
>
> *WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy, **IAAP CPACC+WAS
> = **CPWA*
> <
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.accessibilityassociation.org_cpwacertificants&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=o0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ&m=RsxfgsNOmN7DwCAu0-Q8P6RmrzvpyRhbh9d2uZyra1A&s=YCshzmjLhgvlzWF4HG7l97yWkdaudWsYKDeRBaRhu18&e=
>
>
> *Cell: **703-371-5545* <tel:703-371-5545>***|****ryladog@gmail.com*
> <mailto:ryladog@gmail.com>*|****Oakton, VA **|****LinkedIn Profile*
> <
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_katieharitosshea_&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=o0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ&m=RsxfgsNOmN7DwCAu0-Q8P6RmrzvpyRhbh9d2uZyra1A&s=wYbBFciBty7VQtrdoy_9f5T8X2y7Cixk7S4lre7WAJM&e=
>
>
>
>
> People may forget exactly what it was that you said or did,
> but people will never forget how you made them feel.......
>
> Our scars remind us of where we have been........they do not have to
> dictate where we are going.[attachment "WCAG 2.1 Guideline Suggested
> Changes.docx" deleted by Michael Gower/CanWest/IBM]
>
>
--
Shadi Abou-Zahra -
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_People_shadi_&d=DwID-g&c=jf_iaSHvJObTbx-siA1ZOg&r=o0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ&m=ranJttITMbcdRl9_7dVZqyIcWL-kdV_8j3Sm7YMcMUM&s=g9MATjnWXO57uknjABUji_iY8u58cJXnou4TK04jFIg&e=
Accessibility Strategy and Technology Specialist
Web Accessibility Initiative (WAI)
World Wide Web Consortium (W3C)
Received on Wednesday, 11 April 2018 13:57:15 UTC