Re: 1.4.13 discussion

These were notes from a discussion that Steven and I were having. I believe
that he was going to respond on the issue.
Steve and I talked. The issue has be resolved. Happy with Mgower's
language.
Steve is going to work on updating the understanding document with
additional examples.

Jim


On Fri, Jan 25, 2019, 9:56 AM Jonathan Avila <jon.avila@levelaccess.com
wrote:

> Hi Jim,  thanks for the update.  I was not able to attend either meeting
> this week due to customer meetings.  From reading your notes and the github
> thread I am confused as to what the decision was.  I heard on the github
> thread that the language was fine and that my JS example was fine because
> it was not necessary to allow the additional content to remain on-screen
> when pointer was used if keyboard triggered.  From reading your notes it
> sounds like the opposite.   Can you provide more context?
>
>
>
> Jon
>
>
>
>
>
> *From:* Jim Allan <jimallan@tsbvi.edu>
> *Sent:* Thursday, January 24, 2019 2:00 PM
> *To:* public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
> *Subject:* 1.4.13 discussion
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
> from the minutes (
> https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2019Jan/0015.html
> )
>
>    -  if user causes content to appear on focus, is there a requirement
>    that the user can use the mouse to review the popup content. keyboard
>    trigger separate from mouse trigger.
>    - should be able to hit ESC from anywhere to dismiss additional content
>    -  if keyboard focus is still present, content should stay present
>    until keyboard focus moves or content is dismissed.
>    - focus move should be the dismissal action. hover should not cause focus
>    to move
>    - Understanding need another example (or 2) to explain the hover and
>    keyboard focus. need real world examples.popup info to disappear .
>    - 2.5.6 concurrent input mechanism - author taking active measures to
>    restrict user actions. None of 1.4.13 is inherent in browser/OS, author is
>    not restricting. Author is creating interactions. so 2.5.6 not
>    relevant @@call this out in 1.4.13 understanding doc
>    - keyboard focus should take priority. its ok to have focused menu,
>    and a hover menu at the same time - when something is clicked then focus is
>    moved and focus menu should disappear.
>
> based on the notes above, I needed a list of rules for interactions of
> mouse and keyboard with hover objects...
>
>
>
> *pointer (mouse) *
>
>    1. pointer moves and hovers
>    2. if hover triggers additional content
>
>
>    1.  pointer can be moved to additional content
>
>
>    1. dismiss additional content by
>
>
>    1. moving pointer outside additional content.
>       2. moving outside trigger and additional content
>       3. hitting ESC (keyboard)
>       4. moving focus (keyboard)
>
> 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? I think yes
>
>
>
> *focus (keyboard)*
>
>    1. focus moves
>    2. if focus triggers additional content
>
>
>    1. arrow keys can be used to view additional content
>       2. mouse can be used to view additional content
>
>
>    1. dismiss additional content by
>
>
>    1. moving focus off triggering element and any actionable items within
>       additional content (e.g. tabbing through a menu. )
>       2. hitting ESC
>       3. using mouse to click elsewhere on page. The click causes a focus
>       change. Note: focus does not have move to another actionable element.
>       focus- DOM pointer location can be anywhere in the DOM tree.)
>
> examples
>
>    1. www.utexas.edu have to hit enter on menu items to open the menu,
>    esc works on hover and focus
>    2. amazon.com Accounts & Lists (seems to be a modal). follows the
>    rules above. Make sure Caret navigation (F7) is turned off. with keyboard
>    focus you can move the mouse to the menu. once on the menu if you move off
>    the menu is dismissed.
>    3. http://heydonworks.com/practical_aria_examples/#submenus follows
>    all rules except ESC
>    4.
>    http://terrillthompson.com/tests/menus/accessible-mega-menu/test.html
>    5. www.costco.com open with mouse, but not keyboard (have to hit enter
>    - which seems ok).
>
> fail example
>
>    1. https://www.cbsnews.com/ open with mouse, but not keyboard, no menu
>    works from keyboard at all, no focus
>
> --
>
> Jim Allan, Accessibility Coordinator
>
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315    fax: 512.206.9452 http://www.tsbvi.edu/
>
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>