W3C

- DRAFT -

Mobile Accessibility Task Force Teleconference

11 Jan 2018

Attendees

Present
Detlev, Kim, Chris
Regrets
Chair
Kimberly_Patch
Scribe
Kim

Contents


https://github.com/w3c/wcag21/issues?q=is%3Aissue+label%3A%22Implementation+Follow-up%22+label%3AMATF+-label

https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

TOPIC Understanding and techniques going forward

https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

https://github.com/w3c/wcag21/issues?q=is%3Aissue+label%3A%22Implementation+Follow-up%22+label%3AMATF+-label

TOPIC Thoughts to make working with Github easier

Chris: spending a lot of time helping people would Github – ideas to make things more efficient
... text editor plug-ins
... eventually custom plug-in
... possibilities
... make this as easy for people as possible – workflow is the same but make the workflow familiar
... the complications are no more or less complex – the complication of working on the right branch can't be removed. There are 200 branches out there. That problem exists in both methodologies.
... talking about getting to the point where his save is just a commit. Without changing the brand structure you're still going to have the problem of making sure you're working on the same branch – that's a separate issue, not talking about that
... it's not something everybody would have to use – it's just a choice. Doesn't require any change in workflow just simplifying if you want to use it. I can teach this to somebody once so they are comfortable with it

Detlev: the one thing I'm missing is having a view of the page

Chris: that's why I prefer working on my own file system and doing commits – load up in my browser – that's the workflow I use
... I have plug-ins and suggestions now. anything better would be later
... will send a message with current plug-in suggestions
... ultimately simplifying the branch structure in the future would help as well

Chris will send some plug-in suggested best practices to the list that will make using Github a bit easier for the moment and is willing to walk folks through them if necessary

Next meeting January 18, move forward with understanding and techniques using links above

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/01/11 16:35:37 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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: Detlev, Kim, Chris
Present: Detlev Kim Chris
No ScribeNick specified.  Guessing ScribeNick: Kim
Inferring Scribes: Kim

WARNING: No "Topic:" lines found.

Found Date: 11 Jan 2018
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]