Meeting minutes
Announcements
<bruce_bailey> https://
MaryJo: Open issue meeting will be held next week. Bruce to facilitate while Mary Jo is out.
… only out a week. I opened a survey and covers six issues.
August 6th survey close will help us collate answers and organize. Please respond today if you can. Especially question 6.
… links in Google doc may be broken, apologize if so.
<maryjom> Google doc: https://
Mary Jo: We are working in Google doc for work on proposals.
partial search on heading text in Google doc will help you find what issue we are cross referencing on survey.
Bruce: If you scroll (use side bar) focus does move inside the doc.
<bruce_bailey> https://
Daniel: I will be there too , Bruce.
Mary Jo: I'll email you the scribe commands I use.
Issues Mitch opened (Issue 424, Issue 427, Issue 432, Issue 436, Issue 437)
Mary Jo: Thank you for taking this on Mitch!
<bruce_bailey> +1 on thanks to Mitch !
<Chuck> Yes we did express our support!
Mitch: You are welcome.
<Chuck> Our support and appreciation.
Many give +1's to Mitch for the amazing work!
Mary Jo: Open issues not under survey - here's the link for these items.
Issue 436 – The definition of ‘large scale’ needs substitutions or notes
<maryjom> Link to issue: w3c/
Mary Jo: Definition of large scale term. In evaluating non web, it is unclear how to measure text that is large scale. Mitch has a proposal.
talks to user agent being used and browsers and content for non web not having user agents.
how to interpret the PT. References math equivalents
Mary Jo: Reads Jon's thread comment.
Mitch: Note 3 on screen share - I think we should mention body text but I don't think the reference works entirely.
… reflow and body text...what is body text? What is the size of it?
… body text across all application or all documents ? consistency on size needs to be determined.
… does wcag2ict have that terminology?
Mary Jo: We don't do any word substitute on large text.
WCAG large scale text is what we are referencing on screen. We reference large scale text in our document but don't substitute it.
Mary Jo: Do we really need a change?
Mitch: word substitute issue is on note 3, last sentence. "user agent" does. There is no "user agent" for non web. Perhaps "user agent" word substitute is the solution.
User agent is used but not dependent on elsewhere but the "what you should do" is user agent and major browsers which wouldn't apply to non web.
Mitch: Note 4 talks to major browsers . Which font to assume to occur for users. References what browsers should do , you should do. If software, it would be platform?
Mary Jo: Copies notes from term in WCAG22 in to the Google Doc for wordsmithing on large scale text and user agent and browser word replacement
Mary Jo : Edits in Google Doc. Mitch also edits.
Mitch: Adds edits as well.
Mitch: display settings are platform settings, does any one agree or disagree?
Mary Jo: We can describe in text.
Mitch: I'm done on note 3 on proposal in Google Doc.
Mary Jo: I think note 3 is ok in Google doc.
Note 4 talks to major browsers. I think it would be platform software
Mitch: Platform software.
… then for user agents, documents.
Mary Jo and Mitch review Google Doc edits for word replacement.
Mary Jo: Do you agree Mitch?
Mitch: Let us go with this for the proposal, yes.
<maryjom> POLL: Should we survey the changes to Notes 3 and 4 of the definition of 'large scale' as proposed in the Google doc?
<shadi> +1
<mitch11> +1
<bruce_bailey> +1
<Bryan_Trogdon> +1
<Sam> +1
<ChrisLoiselle> +1
<ShawnT> +1
Mitch: Notes 3 and 4 were covered.
I didn't want to ignore any other phrasing concerns.
… point unit reference PT
Mary Jo: References the large scale font wcag22 definition
Mitch: proposal is to 1 point equal to the CSS pixels , however not clear on typography on native apps.
@mitch hope I captured that correctly for you.
Note 5 references pt but other notes mention point
Sam: I think there is enough here. CSS conversion is there where it needs to be. In native apps, there is a default font usually.
Mary Jo: The point size reference of pt may not be worth moving forward on. Do we agree?
<maryjom> Poll: Do we need to provide any additional guidance or info on pt or point size?
Mitch: We may not change it, but polling both choices would be great for me so we can see whether or not it is worth doing.
Mitch: I'd like to survey both if we can
Mary Jo: We will survey both options on pt vs. point and CSS pixel reference
Mary Jo: Edits Google doc on large scale text discussion topic
Then adds in option 1 leave as is. Option 2, Mitch to add his proposal.
Mary Jo: The next one we wanted to meet on is parsing. There are two issues open on parsing.
<bruce_bailey> If next week we think we have 4.1.1 put to bed, that will be great!
Do we need to add it to problematic on closed? Maybe you can discuss next week. If it needs to be there, what would it be.
The other topic is the word substitution aspect of prior vs. current versions of wcag and use of parsing.
… Daniel has been working on wcag notes and wcag2ict notes that we've added.
<bruce_bailey> If I am the only one who thinks something is better than nothing (for parsing wrt closed functionality), I won't object.
<bruce_bailey> I had expected that I would have had something in writing for folks to react to by now.
Daniel: Nothing at moment to showcase, but we are working on issue on class replacement and another note class to determine what is done on current notes.
Daniel: I could scrape per styled notes.
Mary Jo: Notes on wcag, notes we've edited, add notes and case where we replace a wcag note with wcag2ict version of note.
Mitch: I think the wcag2ict add notes would be great to use as "added".
Need to drop , sorry!
minutes are created.