W3C

- DRAFT -

Mobile Accessibility Task Force Teleconference

30 Apr 2020

Attendees

Present
Kim, Kathy, Jonathan
Regrets
Chair
Kathleen_Wahlbin
Scribe
Kim_patch

Contents


Kathy: dragging examples?
... slider

Jon: will do

Kathy: dragging examples, we have some pictures in there now. We've got several ideas for techniques and also a failure presume, we don't have any of them written. But Jonathan if you've got some time it would be great for you to read through that and see if you have any suggestions for those graphics, or the text that's related to them.

https://docs.google.com/document/d/1LaVX-RTaLQL0tN4G3NhOTlmj16swt0VzC7ssaAjqIwg/edit#heading=h.mntlv4jvrc29

here's the link for dragging

Kathy: also the techniques and examples list has more

Link for techniques and examples list: https://docs.google.com/document/d/1H6OBXEJE-5r3_q2OKwDGhGyg5rcfV9kS9-Wthf-3fK8/edit

Kathy: looking for the exception

Jonathan: thinking that might be too lenient

Kathy: we had that in the intent document – we need to write up something

Jonathan: I don't know if it was a problem with just the wording – if something is on top of another object you couldn't need to take it into account in some way. So I wasn't sure if people had a problem with the wording or if it was impossible to do without the exception. If you can put in space around something that's not overlapping why can't you put space around something that's overtop something by using padding or some layer between that [CUT]
... I think people thought it would be too hard to test when something was overlaying something you wouldn't know because of responsive design
... my concern is something could pop up that was too narrow

Kathy: we could put a sentence in the intent to say that if you have a layer such as emotive dialogue and the user cannot access the information behind the layer then you don't need to have this spacing – does not apply to the underlying, the background layer

Jonathan: that would make sense because it wouldn't be actionable anyways. What about things that aren't mortal – what about a pop-up menu that isn't modal. Right now it read like there would be an exception for that. I was concerned that from the user perspective maybe that wouldn't be good to have an exemption there in that case.

Kathy: what if we change the SC text and said for each active target there's an area…

Jonathan: I don't know, might cause confusion about what's an active target. We might have to clarify what that is

Kathy: is there another word for that…

Jonathan: exactly, that's why I wondered if it was just wording for people rather than actual situation we were trying to solve. There will be targets, but if they're not active they shouldn't be taken into account.
... maybe active targets would go after the other targets. You probably saw the thread from Wilco as well, definition of target.
... that's one possibility – I'd like to get opinion from people like Wilco who probably have very specific interpretations of what is meant by target

Kathy: added comment to the document – that might be enough just to alleviate this

Jonathan: yes, if it's not a target you just ignore it – makes sense

Kathy: we can bring that up – we may need a definition. It looks like were going to talk about target definition anyways

Link to touch target: https://drive.google.com/open?id=1sszSUKB8t3VuRzxHtOjLfQZjNYCw-xr_EbuMwW7WiGc

Jonathan: what if you could do it with the keyboard already

Kathy: may not have a keyboard access on all mobile devices

Jonathan: are we saying the keyboard alternative you would have to meet that as well?

Kathy: yes

Jonathan: I mention it because I thought wording – mechanism is available

Kathy: mechanism is available to change the height, not for secondary control

Jonathan: I'm thinking PowerPoint you can use the thing to rotate the image, but there's also a box – spinner control, not just keyboard, doesn't require keyboard
... you asked about examples – I was trying to think of resizing things that are very small as examples of this
... PowerPoint – I do notice that Microsoft has made for target size. There's also downsides of that, maybe this is where the comment in the understanding dock that different people have different needs.
... because I need a lower resolution screen all my items in PowerPoint are groups – I have to drill down into a layer to access any items on the ribbon because there's not enough room for them to be big enough so they made them secondary or tertiary levels. So now I have to go through a bunch of extra steps to access the same things on the desktop and I would normally have – adjust spread things out for me. And so I do notice that some[CUT]
... offer a more condensed view, where you can go back and get that view – that's a good thing to make it work for everybody

Kathy: can you add that to the understanding?

ACTION on Jonathan, add comment about different users have different needs, condensed view nto intent section below pictures

<trackbot> Error finding 'on'. You can review and register nicknames at <https://www.w3.org/WAI/GL/mobile-a11y-tf/track/users>.

Kathy: that's it for that – we do need to create some techniques and the one failure. The last thing is what we are going to do with the active targets and how were going to do that and update the intent
... I think that's it for now, we just have to work on the techniques for dragging and also this one

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: 2020/04/30 15:25:32 $

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)

Present: Kim Kathy Jonathan
No ScribeNick specified.  Guessing ScribeNick: Kim_patch
Inferring Scribes: Kim_patch

WARNING: No "Topic:" lines found.

Found Date: 30 Apr 2020
People with action items: 

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


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]