W3C

Web Content Accessibility Guidelines Working Group Teleconference

21 Mar 2013

Agenda

See also: IRC log

Attendees

Present
Gregg_Vanderheiden, Marc_Johlic, Loretta, Katie_Haritos-Shea, Kathy_Wahlbin, Michael_Cooper, Kerstin_Probiesch, Adam_Solomon, Andrew_Kirkpatrcik, Andrew_Kirkpatrick, Bruce_Bailey, Cooper
Regrets
Chair
Loretta Guarino Reid
Scribe
Kathy

Contents


<trackbot> Date: 21 March 2013

<MichaelC> scribe: Kathy

<MichaelC> chair; Loretta_Guarino_Reid

LC-2744 : Proposed a failure of 2.4.3 focus order when dynamically inserting content

<adam_solomon> http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-TECHS/SCR26

<greggvanderheiden> We do note that having content inserted above the current focus point without notifying the user of it and its location can be a problem for users who cannot see this. We don't currently have an SC however that forbids this. An advisory technique describing solutions to this, such as ARIA Live Regions, would be helpful. We have added this to our Post WCAG 2.0 wiki as well.

<greggvanderheiden> This provision only says the the content is in a linear order. IF the person activates a control and changes the context - the (new/revised) content may still be in a logical order and meet the success criterion (2.4.3). Putting it behind their point of focus may not be helpful or even good but it is not a violation of 2.4.3. (Dropping the focus partway down the page on page entry would also have similar problems and not be good

<greggvanderheiden> but is not a violation of 2.4.3 either.)

<greggvanderheiden> This provision only says the the content is in a logical order. IF the person activates a control and changes the context - the (new/revised) content may still be in a logical order and meet the success criterion (2.4.3). Putting it behind their point of focus may not be helpful or even good but it is not a violation of 2.4.3. (Dropping the focus partway down the page on page entry would also have similar problems and not be good

<greggvanderheiden> but is not a violation of 2.4.3 either.)

<greggvanderheiden> We do note that having content inserted above the current focus point without notifying the user of it and its location can be a problem for users who cannot see this. We don't currently have an SC however that forbids this. An advisory technique describing solutions to this, such as ARIA Live Regions, would be helpful. We have added this to our Post WCAG 2.0 wiki as well.

<greggvanderheiden> v

<greggvanderheiden> We do note that having content inserted above the current focus point without notifying the user of it and its location can be a problem for users who cannot see this. We don't currently have an SC however that forbids this. An advisory technique describing solutions to this, such as ARIA Live Regions, would be helpful. We have added this to our Post WCAG 2.0 wiki as well.

<greggvanderheiden> This provision only says the the content is in a logical order. IF the person activates a control and changes the context - the (new/revised) content may still be in a logical order and meet the success criterion (2.4.3).

<greggvanderheiden> We do note that having content inserted above the current focus point without notifying the user of it, and its location can be a problem for users who cannot see this. We don't currently have an SC however that forbids this. An advisory technique describing solutions to this, such as ARIA Live Regions, would be helpful. We have added this to our Post WCAG 2.0 wiki as well. (Dropping the focus partway down the page on page entry

<greggvanderheiden> would also have similar problems and not be good but is not a violation of 2.4.3 either.)

RESOLUTION: Accepted as amended

LC-2728 : Visual styling

RESOLUTION: Accepted as proposed

LC-2718 : H91: Using HTML form controls and links

RESOLUTION: Change back to open issue

LC-2631 : SCR18: Providing client-side validation and alert

RESOLUTION: Accepted as amended

WCAG2ICT harmonization with M376 - Part 1 Introduction

Edit to WCAG2ICT language for SC 1.1.1

RESOLUTION: accept with removal of the "or appropriate" in rationale

Edit to WCAG2ICT language for SC 2.2.2

RESOLUTION: accept with addition "of the success criterion" after "...Note 2" or else it is unclear what note is being referred to.

Edit to WCAG2ICT language for SC 2.4.2

RESOLUTION: accepted as proposed

Edit to WCAG2ICT language for SC 3.3.4

RESOLUTION: accepted as proposed

<BBailey> bye

bye

<kerstin> bye

<kerstin> -kerstin

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2013-03-22 18:56:36 $