See also: IRC log
<mck> - Jemma Issue 240: Identify examples where the charCode property of keypress event is used https://github.com/w3c/aria-practices/issues/249
<mck> - Michiel: Issue 187: Updates needed for breadcrumb example page https://github.com/w3c/aria-practices/issues/187
<mck> - James: Issue 221: Update multi-thumb slider design pattern https://github.com/w3c/aria-practices/issues/221
<mck> MEETING Auhtoring Practices Task Force January 30
<scribe> scribe: jamesn
https://github.com/w3c/aria-practices/wiki/Scope
MK: what I did was worked on defining the rest of Minimum Viable Product. Had talked about covering all widget role and states/properties realted to widgets
WHat did on this page is took what we are trying to completed for the 1st release of the APG
what would like group to do is 1st tell me if you think there are things that should be added or removed
and then any feedback on how it is presented
Didn't want to state most frequently used.
AA: guidance for most aria
features
... suggest delete the and most
MK: doesn't say anything about how we are choosing
AA: Q - what does the count mean?
MK: number in that category
... could put a link to section 5.3 where they are
defined
... will be covering about 9 of the doc structure ones
In the 3rd column of the table am providing links to how they Are covered
I did not want to define all the categories here
only place would mention DnD is in the whats changed appendix
AA: noticed applications and region moved
JN: suggest to remove abstract roles from the table
MK: Any galring ommisions?
... probably obvious what uses the menu role but maybe the
seperator role is not obvious. An index would be useful
... would like to make it more strtaightforward for someone to
find things based on a role
JG: will the index inlcude an index of examples which use the things
MK: if we did that then might want a metadata phrase that could be included in the index
'JG: would be interesting to look at a JSON object in the example directory which could highlight what properties etc are used
MK: would rather have a script
which generated the JSON object
... I don';t think we want every row of the tables indexed
SB: will it list what the landmarks etc.
MK: yes - would take you to the section
MK: mapped issues to the states and properties
then created issues where there were gaps
grouped into topics or categories
MK: if you look, for each topic
in the 3rd column there will be specific states and properties
(and for Live regions, roles)
... in the 2nd column is the status
haven't started any of them except KB related stuff
MK: Feed is structural and will
be covered in a design pattern
... would be log role for IRC style chat
... at one point had aria-readonly as seperate - I put it under
communicating widget states
AA: might be helpful for the topics to be ini alphabetical order
MK: was trying to group them by
what they do
... also thinking about the architecture of the overall
document
AA: labelling and describing said
was global
... I think we need a new column 1 - which groups these
things
MK: this is for tracking
was thinking of making a seperate page for describing the IA of the entire guide
MK: other places we seperate done from incomplete
AA: I would vote for grouping things now you have called out what the thought process was
<jemma> I have to go to another meeting at 1. here is my update on keypress. https://github.com/w3c/aria-practices/issues/249
JG: would like to prioritize form control error feedback section
MK: are you saying you would liek to work on it?
all are equal priority for initial release of the guide
MVP scope
JG: would be willing to take it and draft it
MK: have next mil;estone defined already
<jemma> https://github.com/w3c/aria-practices/issues/249
Jon fixed for menu - need doing tree and menubar
JN: nothing to report
MK: I pushed some commits to your
branch
... the changes i made adding some of the features in the
template didnt seem to make it into your new files
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: jamesn Inferring ScribeNick: jamesn Present: AnnAbbott JemmaJaEunKu matt_king ShirishaBalusani JamesNurthen JonGunderson WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 30 Jan 2017 Guessing minutes URL: http://www.w3.org/2017/01/30-aria-apg-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]