<Matt_King> MEETING: September 24, 2019 Authoring Practices Taskforce Meeting
<jamesn> Meeting: September 24, 2019 Authoring Practices Taskforce Meeting
<scribe> scribe: carmacleod
<Jemma_> https://github.com/w3c/aria-practices/milestone/10
mck: as of right now, it looks like we are only at 50%, but that will change in the next few hours
Regarding https://github.com/w3c/aria-practices/issues/727 - don't link directly into spec for now
mck: meter pattern, colindextext, rowindextext should have something to review next week
mck: one part of TPAC agenda to
review
... long-term goals related to APG
... first goal has always been to get full coverage of aria
spec so that folks can get guidance
<Jemma_> 1. Full coverage of ARIA spec
<Jemma_> 2. Integration of assistive technology support tables
<Jemma_> 3. Code quality and readability
<Jemma_> 4. APG Usability
<Jemma_> 5. Integration with other W3C accessibility educational resources
mck: add info about which
examples can be used "right now"
... on track to deliver AT support tables next year
... quality of code, i.e. contrast issues, etc
... goal that by the end of next year that we have done an end
to end audit
... longer term: usability of the apg itself, convert APG from
a monolithic note into a web site.
... like WAI-ARIA Tutorials
... every time we publish, new versions of examples are
created, old ones live forever
... need more educational/explanatory resources, all under one
umbrella
... would need support from other groups, might need joint task
force to make it happen
jon: what happened with combo box?
mck: microsoft isn't willing to
go along with proposal, so more discussion is necessary
... nvda made fixes to support 1.1 model, so if we can get 1.1
pattern to work in AT, may be better not to introduce another
new pattern
<Jemma_> http://a11y.pro/combobox-TPAC2019/
mck: not sure all problems can be solved robustly with 1.1
<Jemma_> I copied the url of Matt's presentation
zoe: regarding code readability, I am drafting guidance in issue 1180 - please add comments
<Jemma_> https://github.com/w3c/aria-practices/issues/1180
evan: I can do a PR for modernizing using build
sarah: I can help with build processes so that we can use more ES6 code, etc, and update examples
mck: how would this look for users?
zoe: we would still link to our js files to show the javascript
evan: can separate the type of code we require authors to write from the deployed code
james: debugging through code would not look the same as source code
sarah: can use source maps
jon: need to be careful that the code that you are seeing is not the code because is executing in the browser
mck: how much longer will we care
about IE11
... people might still be required to produce stuff that works
in IE11, and possibly not our job to show them how to support
it
zoe: that boils down to "how many people use AT that only supports IE11"
mck: I am not aware of any AT that only supports IE11
<Jemma_> https://webaim.org/projects/screenreadersurvey7/#browsers
<Jemma_> https://webaim.org/projects/screenreadersurvey7/#browsercombos
<Jemma_> the data is from Oct, 2017
mck: we have said that our scope is modern and popular browsers, and we have historically included IE11
<MarkMccarthy> Maybe once the new WebAIM survey comes out we can get a little bit of a clearer picture, understanding its scope is limited
sarah: many microsoft products no longer support IE
mck: I would like to move on, but
we will bring this up again at the beginning of the year, and
we may decide to drop support for IE11 then
... Next issue: spinbutton in Safari
github: https://github.com/w3c/aria-practices/pull/1154
mck: works with month and day,
but not year?
... is this a bug in the example, or a safari bug?
jon: spinbutton doesn't work in vo
mck: MacOS safari does work with VO - it just doesn't work with VO commands
jon: could use aria-valuetext instead of aria-valuenow
mck: need to report VO bug
jon: I can look into this
mck: need someone to do some css, then Jesse Beach will add to all of the examples
github: https://github.com/w3c/aria-practices/pull/1110
zoe: I will make the button pretty
<MarkMccarthy> This widget may have support gaps that can only be filled by the development of new technologies. Authors should fully test this widget before using it for a production ready project. Likewise, it may be poorly supported by certain browsers or assistive technologies.
github: https://github.com/w3c/aria-practices/issues/1150
mark: wrote it so it can be generically used
mck: if it is so general that it
doesn't give any idea about what the gaps are, then users won't
know if it affects them
... should we scope this warning to just be mobile, touch
screen, or similar?
mark: open to making that change if others agree
mck: ... assistive technologies
offered via touch interaction ... ?
... do we want to use the word "widget" or "pattern" here? Or
"widgets implemented using this pattern"?
... might depend on context (i.e. does it appear of pattern
page or example page)
... do we need the "Likewise" part?
<Jemma_> "This widget may have support gaps that can only be filled by the development of new technologies. Authors should fully test this widget before using it for a production ready project. Likewise, it may be poorly supported by certain browsers or assistive technologies."
<Jemma_> +1 for Matt's comments on the first sentence
mck: maybe first sentence and last sentence are redundant?
<Jemma_> other than that, this looks great, Mark
mck: which examples need this,
other than slider?
... add it to slider first, then duplicate as needed
<MarkMccarthy> Thanks Jemma
mck: new technologies like AOM
jemma: "new technologies" sounds vague - maybe we need to specifically include AOM?
mck: don't want a dependency on AOM in wording
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) Succeeded: s/Meeting: Accessible Rich Internet Applications Working Group Teleconference/Meeting: September 24, 2019 Authoring Practices Taskforce Meeting/ Succeeded: s/copied/copied the url of/ Succeeded: s/that/because/ Succeeded: s/than this/than that, this/ Default Present: Matt_King, jongund, MarkMccarthy, Jemma, ZoeBijl, evan, carmacleod, Sarah_Higley, curtbellew, jamesn Present: Matt_King jongund MarkMccarthy Jemma ZoeBijl evan carmacleod Sarah_Higley curtbellew jamesn Found Scribe: carmacleod Inferring ScribeNick: carmacleod Agenda: https://github.com/w3c/aria-practices/wiki/September-24%2C-2019-Meeting Found Date: 24 Sep 2019 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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]