Meeting minutes
Announcements
maryjom: 1) little change in process: for the surveys, will start closing surveys the day before the meeting to have time to prep all the responses and come up with common topics. make sure you respond before that
maryjom: 2) label in name has been incorportated into the draft as well as some editiorial and formatting. The includes are working only when you are doing PRs, for some S.C but not all; still work in progress
maryjom: 3) have created a schedule with milestones so we have targets to work toward
<maryjom> https://
maryjom: the tables are done with markdown
<maryjom> https://
maryjom: 4) have created a status that tracks the status of a page so it keeps a rundown of all the sections of the document, to see it all in one space
maryjom: this will help us understand the work that we need to accomplish, if you have a 2.1 S.C. take a look at the schedule; if you don't think it will be ready by then, please let me know/ ask for help
maryjom: 5) there is a survey for the AGWG for the first 4 S.C. we can all respond to that too
maryjom: the results of the survey will be discuss at March 21st, meeting will be 2 hrs long and you are welcome to join and hear feedback
Chuck_: normally the survey would be open a week and then review the following week, however the meeting of the 14th will not happen because of CSUN and AxeCon, everything has been pushed out a week
maryjom: would we meet during that week?
<maryjom> Poll: Are you going to CSUN or particpating in AxeCon?
<Chuck_> Oracle will not be attending CSUN unfortunately.
<mitch11> is attending CSUN
<ChrisLoiselle> I can meet , not currently attending either in person
<Chuck_> I can be available for WCAG2ICT that week.
<maryjom> I can meet too
<BryanTrogdon> not attending CSUN
<shadi> yes, going to CSUN and planninf to listen in to aXe con (prefer not to meet that week)
<olivia-hogan-stark> Yes, attending CSUN
maryjom: will send an email, we could make a working meeting with no decissions for that week
maryjom: 6) maybe 1-2 surveys due on the 8th, smaller with new proposals for text so we can hopefully reach consensus for that
mitch11: meeting times: US will have day light saving times and Europe will not, what time should be using?
maryjom: it is set to Eastern Time
maryjom: when there are mismatches, we will follow ET
maryjom: will send an email about it
Chuck_: I will be doing some announcement in the AGWG call, its up to the individual teams; AGWG will stick as well with US Central
Project standup (status of your assigned issues)
maryjom: for our project, we have 3 ready for review, in progress the includes are work in progress; will reach out to Laura
olivia-hogan-stark: in progress (with S.C. assigned to Olivia)
maryjom: we will talk about reflow today; need status on 2.5.1
maryjom: looks like we are kind of on track, like I said, take a look at the schedule and confirm that the timeline works or let me know if you have issues
zakim take up next
Review Survey results for Key Terms and Glossary Items Used Only in AAA Success Criteria sections
<maryjom> • https://
maryjom: 7 responses, incorporate as-is
FernandaBonnin: for key term, 3 ready as is, 4 incorporate with some changes
maryjom: Phil comment on capitalization of Web, that is how we capitalize across W3C; Loic, some comments on formatting it is a result of the old formatting, we will need to figure that out. Loic also had a couple of comments on text. Mike and Bruce also weight in
maryjom: Mike said likes the separation of notes so they are clear
<maryjom> hard drive file, or stored in a single encrypted file system file, do not constitute a single document. The software that archives/encrypts those files or manages the contents of the virtual hard drive does not function as a user agent for the individually collected files in that collection because that software is not providing a non-fully functioning presentation of that content.
maryjom: wanted to get into Loic's edits and then we can talk about the number of notes
<maryjom> A collection of files zipped together into an archive, stored within a single virtual hard drive file, or stored in a single encrypted file system file, do not constitute a single document. The software that archives/encrypts those files or manages the contents of the virtual hard drive does not function as a user agent for the individually collected files in that collection because that software is not providing a non-fully functioning prese[CUT]
maryjom: didn't modify the content of these bullet points from the original WCAG2ICT
<Zakim> Chuck_, you wanted to say 'file system' file.
<maryjom> A collection of files zipped together into an archive, stored within a single virtual hard drive file, or stored in a single encrypted "file system" file, do not constitute a single document. The software that archives/encrypts those files or manages the contents of the virtual hard drive does not function as a user agent for the individually collected files in that collection because that software is not providing a non-fully functioning pre[CUT]
Chuck_: in queue to say a minor recommendation: the file system file reads odd to me. Also, could we put quotes for "file system"
<mitch11> not quite: stored in a single encrypted "file system" file
<mitch11> it means: stored in a single "encrypted file system" file
<mitch11> neither is great, but the latter is accurate
maryjom: if no issues raised on that, we will take that update
maryjom: mitch tweak, it may or may not be encrypted
mitch11: the original is ambiguous
<Chuck_> +1 to mitch
<maryjom> A collection of files zipped together into an archive, stored within a single virtual hard drive file, or stored in a single "encrypted file system" file, do not constitute a single document. The software that archives/encrypts those files or manages the contents of the virtual hard drive does not function as a user agent for the individually collected files in that collection because that software is not providing a non-fully functioning pre[CUT]
<maryjom> Example: One example of a set of documents would be a three-part report where each part is a separate file. At the beginning of each file the table of contents for “navigating” to the other parts is repeated.
maryjom: onto the "set of documents", any have any issues with that change?
<maryjom> Draft RESOLUTION: Incorporate both the Key Terms and Level AAA-only definitions sections with the notes changes Loïc proposed.
<maryjom> Draft RESOLUTION: Incorporate both the Key Terms and Level AAA-only definitions sections with the note and example changes as edited in the meeting..
<mitch11> +1
<olivia-hogan-stark> +1
<Devanshu> +1
<maryjom> +1
+1
<BryanTrogdon> +1
<Sam> +1
<PhilDay> Apologies for being late - had some technology issues!
RESOLUTION: Incorporate both the Key Terms and Level AAA-only definitions sections with the note and example changes as edited in the meeting.
Review Survey results for SC 1.4.13 readiness to incorporate into editors draft
<maryjom> https://
maryjom: there where 10 responses, 8 incorporate with changes and 1 and 1 with as-is and not ready
maryjom: Mitchell, proposed changes in the issue comment
<maryjom> Mitch's proposed changes: w3c/
<maryjom> Loïc's modification to Mitch's proposal plus additional changes: w3c/
maryjom: Phil, Fernanda and Sam agreed with those changes. Then Loïc wanted to do some additional editiorial changes
maryjom: Fernanda would like to see the notes numbered, formatting thing. Its another style thing, its not numbering notes anymore, we will have to look into this
maryjom: created a comment that combines all comments with edits for consistency
<maryjom> Mary Jo's updated proposed changes, incorporating others' thoughts: w3c/
maryjom: Shadi and Bruce gave a +1
<maryjom> This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.13 (also provided below), replacing "user agent" with "user agent or platform software", "browser tooltips" with "tooltips", and "the HTML title attribute" with "user interface object attributes".
<maryjom> Exception would read as: Exception: The visual presentation of the additional content is controlled by the [user agent or platform software] and is not modified by the author.
<maryjom> First note would read: Note: Examples of additional content controlled by the [user agent or platform software] include tooltips created through use of [user interface object attributes].
maryjom: any concerns with the modifications?
<Sam> +1
<maryjom> DRAFT RESOLUTION: Merge the proposal for 1.4.13 into the editor’s draft with the edited text in Mary Jo’s comment on the issue (linked above)
<shadi> +1
+1
<mitch11> +1
<Devanshu> +1
<PhilDay> +1
<maryjom> +1
<BryanTrogdon> +1
<Sam> +1
<olivia-hogan-stark> +1
<ChrisLoiselle> +1
RESOLUTION: Merge the proposal for 1.4.13 into the editor’s draft with the edited text in Mary Jo’s comment on the issue (linked above)
Continue previous discussion on applying 1.4.10 Reflow to non-web documents and software
<Sam> I set on my phone
<maryjom> https://
maryjom: we started this discussion last time, it went over; appreciate everyone that has been weighting in on the discussion board in GitHub
maryjom: conversation was on what do we call the CSS pixel?
Sam: there's been a lot of comments around how this is not a hardware level, or its a closed system. In the end, there is something that makes it from the human to the device. With the CSS pixels and the sizing, we are forced to talk about sizes, physical measurements
maryjom: that its probably truth and Mitchells' discussion refers back to the definition of CSS pixel and it talks about the visual angle. the suggestion was to get the S.C. rewritten which we cannot do; Loïc made a suggestion to redifine what a pixel is: reate a new definition of a device independent pixel talking about the visual angle
maryjom: with the size of the device defined by the assumed viewing distance between the user and hardware
maryjom: what are folks thoughts on this new definiton?
<BryanTrogdon> +1
maryjom: new definitions are not outside of what we can do
PhilDay: agree with removing the CSS word; but to Sam's point we already have guidance on accessibility standards and this is reinventing the wheel
Chuck_: this isnt necessarily changing the boundary too much, but the change of the CSS pixel would need to be discussed to the group. Some approaches: 1) make a recommendation to review with AGWG
Chuck_: 2) if we do tackle this is a significant journey and then the AGWG would need to repeat the journey, so if we do want to change this, then lets elevate it so we can take the journey together and have a wider conversation
Sam: I also have issues with the AR angle, there is an assumption that smaller screens will be closer to the screen and I don't know if this is the right way to approach this. There is already a lot of definitions about text sizing
maryjom: agree there is about text sizing, but this is about scrolling in a single direction
mitch11: already said in comment I like the direction of Loïc's comment, and to the point made about that the EN already has conflicting criteria to close functionality; I don't think we are creating a third thing we are really doing the same thing.
<Chuck_> Siri says 5 minute warning
mitch11: it might be easier to kick the tires of the visual angle approach and to contemplate closed functionality on larger screens and to understand if its a problem of small screen or closed functionality
<Chuck_> understood that this would be for WCAG2ICT and not change an existing defintion.
maryjom: to Chuck's point, we don't want to change the WCAG definition, it would be a new WCAG2ICT term, has been done before. this would help people get out of the CSS mindset
PhilDay: to Mitch's earlier point about larger screens, we can do that for text resize but most closed systems will not support reflow
PhilDay: there are some systems where the display system will significantly change; e.g. ATM vs ordering food kiosk. It will be hard for someone to meet this if they are designing for systems that do two things
<Chuck_> I do have a hard stop at top of hour.
shadi: I do think there might be cases where this has not been consistent, so additional notes on how this would not apply will help address exceptions. But for the majority of the use cases, I like the directions of dip
<Chuck_> +1 on awesome discussion!
<Chuck_> I must depart and join another call.
maryjom: great discussion, I know it will not be the last of this, but will take content and suggestion under advisement and will try to make a proposal and take it in front of the AGWG