WCAG Weekly Telecon

Draft Techniques and proposals for Guideline 3.2 from 02 February

resolution: accept unanimous and unanimous with comments items - Proposed revisions to SC 3.2.4, Issue 974, Issue 1596, Issue 1847, Issue 717, Issue 1033, Issue 1844, Issue 1572, Issue 386, Using both keyboard and other device-specific functions, Failure due to using script to remove focus when focus is received

Failure due to opening a new window as soon as a new page is loaded

<Zakim> Yvette, you wanted to ask "Gregg, could you speak up?"

action 1 = team a to consider new title and description revisions to ensure that it does not cover purposeful (user-initiated) opening of multiple windows.

Presenting navigational components in the same relative order each time they appear

resolved, remove technique, "Presenting navigational components in the same relative order each time they appear" and combine with more general technique about repeated components

Failure due to using different text alternatives for components with identical functions

Failure due to using two different labels for same function on different pages

<scribe> ACTION: alex to send gregg example regarding print invoice vs. print receipt, gregg to include in draft, "Failure due to using two different labels for same function on different pages" [recorded in http://www.w3.org/2006/02/16-wai-wcag-irc]

resolution: accept propsoed technique, "Failure due to using two different labels for same function on different pages"

Failure due to using different text alternatives for components with identical functions

<scribe> ACTION: team A to combine "Failure due to using different text alternatives for components with identical functions" and "Failure due to using two different labels for same function on different pages" as "Failure due to using different labels or text alternatives for components with identical functions" [recorded in http://www.w3.org/2006/02/16-wai-wcag-irc]

Providing a mechanism to request an update of the content instead of updating automatically

resolution: accept proposed technique, "Providing a mechanism to request an update of the content instead of updating automatically" with edits.

Implementing automatic redirects on the server side instead of on the client side

<rscano> it easy to test: if in the page there are meta elements that made redirect, the page don't pass the SC

<rscano> yes good :)

resolution: accept proposed technique, "Implementing automatic redirects on the server side instead of on the client side" with the revisions to test as follows, "06 For each link or programmatic reference to a URL in the set of develivery units being evaluated, check if the referenced delivery unit contains code (e.g. meta element or script) that causes a client-side redirect.01"

Failure due to unrequested removal of controls of user agent

resolution: move "Failure due to unrequested removal of controls of user agent" to the boneyard since the failure is not currently covered in this SC.

<scribe> ACTION: david to explore whether Failure due to unrequested removal of controls of user agent fits someplace else in the guidelines [recorded in http://www.w3.org/2006/02/16-wai-wcag-irc]

Using an instant client-side redirect

<rscano> <meta http-equiv="refresh" content="0; url=http://www.example.com/newpage" />

resolution: accept proposed technique, "Using an instant client-side redirect" with edits.

Failure due to opening a new window or a pop-up after a click on content that does not perform a function

back to team A for additional revisions

<scribe> Topic: Failure due to using meta refresh with a timeout

resolution: accept technique, "Failure due to using meta refresh with a timeout" with edits

GL 1.3 Techniques and issues (Feb 9)

Failure due to using th elements, and

summary attributes in layout tables

<rscano> in WCAG 1.0 was for *all* the table: 5.5 Provide summaries for tables. [Priority 3]. But we really need to have summary for simple layout table?

<rscano> why should be used as null? it is no required by specifications.

no resolution

Failure due to providing text alternatives that include words that appear in a text image, but fail to include information that is conveyed by the color of certain words in the image

<Andi> /me Yvette's proposal ""Failure due to having a text alternative that does not include information that is conveyed by color in the image"

<Andi> /me ""Failure due to having a text alternative that does not include information that is conveyed by color in the image"

<rellero> sorry, I have to go, bye

resolution: accept technique with edits and retitle as, "Failure due to having a text alternative that does not include information that is conveyed by color in the image"

<Andi> scribe: Andi

Failure due to using CSS to create variations in presentation of text that conveys information without also using structure

resolution: Accept technique with edit - create a new example using color or bold and move the heading example to 1.3.1

Failure due to identifying content only by its shape or location

resolution: accept with suggested edits

GL 2.4 Techniques and issues (Feb 9)

Rewording 2.4.3 and moving it up to Level 1

<Zakim> Christophe, you wanted to say "last week we said that the nl element in XHTML 2 would meet the SC without the author having to add a skiplink"

<Becky> q

<sorcha> apologies, have gotten cut off skype - am rejoining

<sorcha> Apologies, but must exit call early.

2 proposals: change 2.4.3 to require only an invisible mechanism and move it to Level 1 and add a Level 2 SC for a visible mechanism.

resolution: adopt proposal to have a Level 1 SC for an invisible mechanism - structure that can be used to navigate would be sufficient
... reject proposal to add a Level 2 SC for a visible mechanism

The title element

Using the title attribute of the frame element

resolution: accept as a technique for 2.4.6 with a proviso that it makes sense there.

Providing descriptive headings

resolution: accept technique with suggested edits

GL 3.1 Techniques and Issues (Feb 9)

proposal to change the wording of 3.1.2

resolution: reject proposal to change wording of 3.1.2. Remove the word "foreign" in the current wording of 3.1.2.
... reword Note on 3.1.2 - "...apply to individual words or phrases that have become..."

How to meet 3.1.4

resolution: accepted with edits

Providing the expansion or explanation of an abbreviation

resolution: accept with edits and approval from people who have concerns - team to decide if needs another WG review

Providing the abbreviation immediately following the first use of the expanded form within the delivery unit

resolution: accept with edits (understanding that "delivery unit" is still under discussion in the group)

Linking to definitions

resolution: accept with edits

<scribe> topic: Using a Glossary

resolution: accept with edits

Abbreviations

resolution: accept this as one technique with edits

Supplemental Meaning Cues

resolution: accept as advisory technique, not a sufficient technique, as revised
... change title to "Using the link element to link to a glossary"

Glossary Page

resolution: accept with edits

Issue 1753

resolution: "Using the link element to link to a glossary" is the new title for "Glossary Page"
... issue 1753 proposal accepted with Gregg's alternative closing comment

3.1.5 success criteria rewording

resolution: accept with edits

Measuring the readability of text content

resolution: refer back to committee

Providing a text summary that requires reading ability less advanced than lower secondary education level

resolution: accept with edits

Providing visual illustrations of complex ideas, events, and processes

resolution: accept with edits

Providing a spoken version of the text

resolution: accept with edits

delivery unit

problem with using delivery unit because each jpg within a page would be a delivery unit and would have to include a title