W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

24 Jan 2019

Attendees

Present
Laura, Jim, JohnRochford, AllanJ, jon_avila, SteveRepsher
Regrets
Laura, Shawn
Chair
jim
Scribe
AllanJ

Contents


https://docs.google.com/spreadsheets/d/1gwp30K0OJ46mtjKCwo__cCIHn6mgTl-fvn2A_ADzwEc/edit#gid=0

<steverep> Barely... lots of background

<steverep> Can anyone hear me?

1.4.13 work session

reviewed various sites for functioning

rule for 1.4.13 functioning

mouse -

mouse moves and hovers

if hover causes additional content

- mouse can be moved to additional content

additional content can be dismissed

-if mouse moves outside additional content, the additional content disappears (assumes trigger and additional content are seen as one unit).

-if mouse move off trigger and additional content, the additional content disappears.

-if ESC is hit the additional content disappears.

-if focus (keyboard) moves the additional content disappears

Special case: if additional content appears and contains actionable elements is it reasonable for the user to hit the tab key to focus on the actionable element in the additional content?

sr: need to publish a technique for the keyboard/mouse combo interaction.

use the rules from mouse and keyboard and combination

sr: mouse and keyboard should be independent following the rules.
... need additional example in Understanding

keyboard

tab moves focus

if focus causes additional content

- arrow keys can be used to view additional content

- mouse can be used to view additional content

Additional content can be dismissed by

- moving focus off triggering element and any actionable items within additional content (e.g. tabbing through the menu. )

- hitting ESC

- using mouse to click elsewhere on page (causing a focus change. Note: focus does not have to be on another element. focus- dom pointer location can be anywhere on the page.)

trackbot, end meeting

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/01/24 16:58:03 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: Laura, Jim, JohnRochford, AllanJ, jon_avila, SteveRepsher
Present: Laura Jim JohnRochford AllanJ jon_avila SteveRepsher
Regrets: Laura Shawn
No ScribeNick specified.  Guessing ScribeNick: AllanJ
Inferring Scribes: AllanJ
Found Date: 24 Jan 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]