- From: Kim Patch <kim@redstartsystems.com>
- Date: Thu, 6 Dec 2018 12:25:01 -0500
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <aea68cfa-5c0c-ce03-8b29-84df4743b33d@redstartsystems.com>
*MATF Minutes 29 November 2018 link:
https://www.w3.org/2018/12/06-mobile-a11y-minutes.html*
*
Text of the minutes:
*
Mobile Accessibility Task Force Teleconference
06 Dec 2018
Attendees
Present
kim, Kathy, JakeAbma, MarcJohlic, Detlev
Regrets
Chair
Kathleen_Wahlbin
Scribe
kim
Contents
* Topics <https://www.w3.org/2018/12/06-mobile-a11y-minutes.html#agenda>
1. concurrent mechanisms at AAA
<https://www.w3.org/2018/12/06-mobile-a11y-minutes.html#item01>
2. biometrics
<https://www.w3.org/2018/12/06-mobile-a11y-minutes.html#item02>
3. Next Steps
<https://www.w3.org/2018/12/06-mobile-a11y-minutes.html#item03>
* Summary of Action Items
<https://www.w3.org/2018/12/06-mobile-a11y-minutes.html#ActionSummary>
* Summary of Resolutions
<https://www.w3.org/2018/12/06-mobile-a11y-minutes.html#ResolutionSummary>
------------------------------------------------------------------------
https://docs.google.com/spreadsheets/d/1wRAViPfAJ4Ytqc71tGZp6gU07HNd2QQaNgtJsog-D90/edit#gid=0
concurrent mechanisms at AAA
Kathy: challenge focus indicators different
Kim: using different mechanisms as a mix – mechanisms don't have to know
about each other, just user using method of choice for any given moment
Jake: just a choice for a person building a specific widget – not that
one is better than the other it's just a choice.
... focus management must be so that the browser focus as well as the
accessibility tree focus are on the same point, the same component. This
is an option you may use if you do have a box with a read-only input
field so when you start typing it won't change the input field and you
want the browser focus as well as the mouse focus
... just switch to the next mechanism – two focuses, accessibility focus
and browser focus
... Google not real combo box browser focuses on but the moment you
start typing suggest but the mouse focus will be in the accessibility
tree focus so it's a choice what component you like if those two focuses
are exactly the same, browser, mouse access tree or you split them –
that's a choice for what type of component you would like to build and
those two options are available
Detlev: I completely agree – I wasn't suggesting we restrict things in
any way but there are different choices depending on the scenario. Good
or bad choices are trade-offs where one thing is better for – mouse
focus same as keyboard focus might be best practice but for others is
distracting just have cursor and anything else there is distraction. So
a trade-off no clear you must do this or that, and that exactly brings
me to the point that I still don't[CUT]
... … Understand, what is needed to focus concurrent mechanisms – what
this actually does. What is the actual requirement. What would you want
and what might be techniques to meet those. I still don't Quite understand
biometrics
Kathy: Maybe potentially covered under 1.1.1
Shadi: but biometrics is input – it's different that way, facing camera
or put your finger. But essentially the same and really simple. I think
where this came from is when we were talking early this week I was
saying I'd like to go through the European standard and see what's in
there. There are some really simple things that are traditionally not
under web but are now finding more space for this – this biometrics
thing is under general requirements in [CUT]
... you can now use your finger to login etc. – very closed now, but
biometrics and authentication mechanisms increasingly used
Detlev: also icon and will put in your password under some conditions –
I'm not sure what conditions and whether that is something the web
author can influence – where that comes from I'm not sure
Shadi: whether the author can influence earn or not it's third-party
aspects. If you are providing such a login method that requires
fingerprints or face recognition which may not work for you – whatever
mechanism you provide you should provide alternatives to that.
Detlev: it sounds like a pretty straightforward new success criteria
Next steps – Shadi may have more by January 10 European
Kathy: need to do a summary, list out what we are thinking about for
people who weren't on the call
Next Steps
Add any other potential 2.2/silver to spreadsheet.
Note that we also added to the spreadsheet during the call:
https://docs.google.com/spreadsheets/d/1wRAViPfAJ4Ytqc71tGZp6gU07HNd2QQaNgtJsog-D90/edit#gid=0
Summary of Action Items
Summary of Resolutions
[End of minutes]
------------------------------------------------------------------------
Minutes manually created (not a transcript), formatted by David Booth's
scribe.perl
<http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm> version
1.154 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2018/12/06 17:20:44 $
------------------------------------------------------------------------
Received on Thursday, 6 December 2018 17:25:28 UTC