Jan 31 Team B meeting minutes

	In attendance: John, Yvette, Becky, Loretta, Bengt

1.	What to do about 2.4.1
-	Using Javascript to add link behavior to non-link element
-	What problem are we trying to solve?
i.	Things can be used to navigation that aren't inherently
navigation mechanisms, e.g., Button
  		 Proposal to delete this SC: if kept, what is a
navigation mechanism and what techniques should be included
          		  Can think of any techniques that aren't
required elsewhere.

Team B proposes deleting SC 2.4.1 because navigational mechanism in
XHMTL content are covered under other SC like 1.3.1 and nav mechanisms
in other technologies are covered under GL 2.1, 4.1, and 4.2. 

2.	Assignments:
-	2.4.2 open issues (Loretta)
-	2.4.3 open issues (Bengt)
-	2.4.3 (Becky) look at HTML techniques, including user agent
issues
-	2.4.4 (John)
-	2.4.5 (Loretta) (Becky will help with HTML techniques)
i.	Proposal: accept David's proposal to make association
programmatic, remove first technique
ii.	Propose not adding hyperlink to wording
iii.	Note David's additional technique proposals (Becky to write up)
-	2.4.6 (John) "Using unique" instead of "avoiding repeated"
(Loretta)
-	2.4.7 (Yvette)
-	2.4.8 (Loretta)

Survey the following techniques and proposals:

Team B proposes deleting SC 2.4.1 because navigational mechanism in
XHMTL content are covered under other SC like 1.3.1 and nav mechanisms
in other technologies are covered under GL 2.1, 4.1, and 4.2. 

Accept proposed wording for 2.4.5 to programmatically associate link
with description, remove first technique

Table of Contents
Site Map (Loretta check that it address both 2.4.6 and 2.4.2)
Using the link element and navigation tool (2.4.2, 2.4.8): Becky will
add UA section, remove id attributes
Breadcrumb Tail (Becky will update to require programmatic references,
permit trails that don't include current page)


Reword 2.4.3
A mechanism is available to bypass blocks of content that are available
on multiple perceivable units.
Rationale: the current wording affects the blocks of content, and the
proposed wording affects the mechanism for bypassing them. How to meet
already focuses on mechanisms, not blocks.

2.4.3 general technique: 
Propose to change: "Using one of the following techniques to create
links to skip blocks of repeated material. Note: It is preferred that
these links be visible." to "Using one of the following techniques to
create links that are visible when they have focus to skip blocks of
repeated material."


Loretta Guarino Reid
lguarino@adobe.com
Adobe Systems, Acrobat Engineering