Meeting minutes
<bailey> precent+
Mary Jo: Announcement , we did introduce WCAG2ICT the issue w3c/
We may be delayed per what we are introducing today.
Daniel may be needed to included or Kevin or Shawn on ready for publish GitHub template
Review to end upcoming Tuesday. Changes may cause a restart or delay.
Communication is being drafted , working with Shawn H. and Tasmin.
zakim , take up next
announcements
<Zakim> bailey, you wanted to ask where to add typos and to
Bruce: Can Tasmin do the pulls?
<bailey> w3c/
Mary Jo: She may.
Bruce: I submitted some typo edits.
Mary Jo: She did have questions on what you submitted.
Issue 752 - 2.1.1 Keyboard: Precondition doesn't include non-web documents (this is crucial for the publication)
<maryjom> w3c/
Mary Jo: Per EN , it reads as written. A statement from WCAG2ICT should say that non-web documents applies directly as written.
<Zakim> bailey, you wanted to say i expected to see sub headings
Bruce: I thought we were going to have sub headings on sub headings to distinguish between non-web documents and non-web software?
Mary Jo: We haven't included page title scenario, however we could introduce it.
Gregg: This would be place to do it.
<maryjom> Under a heading "Applying SC 2.1.1 Keyboard to Non-Web Documents" state: This applies directly as written, and as described in Intent from Understanding Success Criterion 2.1.1.
<maryjom> Also make sure we have a different heading "Applying SC 2.1.1 Keyboard to Non-Web Software"
Mary Jo: proposed edits in IRC.
<bailey> +1
<maryjom> DRAFT RESOLUTION: Update 2.1.1 Keyboard as stated in IRC above to address issue 752
<Mike_Pluke> +1
<ChrisLoiselle> +1
<bailey> +1
<maryjom> +1
<GreggVan> +1
RESOLUTION: Update 2.1.1 Keyboard as stated in IRC above to address issue 752
Issue 753 - 1.4.4 Resize text: EN 301 549 has additional note (this can be put off until later)
Mary Jo: Is this needed in WCAG2ICT?
<maryjom> EN 301 549 has this note for non-web documents in 1.4.4 Resize Text - NOTE: It is best practice to use only fonts that allow for scaling without loss of quality (e.g. pixelized presentation). This applies in particular to embedded fonts
Gregg: I think it is a good note. Old fonts that pixelates would be impacted. If there are fonts that are impacted, we are assuming it doesn't exist anymore.
Gregg: Not sure what happens on other platforms.
Mike: Some systems may not have scaling. I don't know of practical systems that pixelate. It is useful if it does apply.
<Zakim> bailey, you wanted to ask why not apps?
Gregg and Mike: I'd recommend keeping in EN.
Bruce: Would we apply it to software and documents?
Gregg: I think it should go in both places.
Gregg: More in documents compared to software
<maryjom> POLL: Should we add this note into WCAG2ICT?
<bailey> +1
<Mike_Pluke> +1
<ChrisLoiselle> +1 , think it helps clarify use case.
<GreggVan> +1
RESOLUTION: Add the EN 301 549 note and apply it to both non-web documents and software.
Triage for AG WG comments on the draft
Mary Jo: 6 thumbs up on review. No comments yet.
Mary Jo: Please continue to review.
<Zakim> bailey, you wanted to ask about "view"
Mary Jo: We don't use view
Bruce: Ok.
Mary Jo: You can test views but it is aggregated up.
Mary Jo: Daniel copied what was in editor's draft. It was forked in to a publication repo.
Bruce: I'm not sure people would know to comment on branch
Bruce: If people were to comment on W3C Group Note (staging) it , https://
Bruce: So my PR on editor's draft may not be a one for one against the staging document issue 750 was based on.
Bruce: I wanted to make sure I was on the correct rendered version on https://
https://
Mary Jo: Note is stated backwards within hardware.
Mary Jo: Need PR on editor's draft
Gregg: Never seen a pull request push .
Note 1
Contrast requirements for hardware are out of scope for WCAG2ICT (and this success criterion).
Note 4
Hardware requirements for contrast are out of scope for WCAG2ICT (and this success criterion).
Bruce: Consistency is key on phrasing.
Gregg: Contrast requirements for hardware should be phrasing.
<maryjom> DRAFT RESOLUTION: SC Problematic for Closed - Change note for 1.4.11 to be what is found in 1.4.3.
<ChrisLoiselle> +1
<maryjom> "Contrast requirements for hardware are out of scope for WCAG2ICT (and this success criterion)."
<Mike_Pluke> +1
<bailey> +1
<GreggVan> +1
RESOLUTION: SC Problematic for Closed - Change note for 1.4.11 to be what is found in 1.4.3.
Mary Jo: We will get those three changes.
Bruce: Will review 751 PR to include the resolution for 1.4.11 and 1.4.3 phrasing.
TF review of the WCAG2Mobile document
chris: WCAG2Mobile: Draft feedback on the use of "view"
https://
chris: There's a long conversation in the issue about concerns about using "view"
… There's concern with using in the guidance a definition that is under development
gregg: In WCAG 3, if we can make the definition of "view" work, we'll be using "web page" and "view". WCAG2ICT shouldn't use "view" because, in WCAG 2.2 there is no "view" defined.
… they are using "view" without really knowing for sure that it will work and which won't be proven until WCAG 3 is further along and tests the concept and definition.
… Since the WCAG2Mobile is also going into web on mobile, there use of "view" when applied to web content isn't par of WCAG 2.2
ChrisLoiselle: Agree with Gregg. Though they are really trying to pull in the capabilities in mobile for titling a view, it doesn't seem ready to definitively require it. Do we need to open an issue in WCAG2Mobile?
GreggVan: The differing interpretation in WCAG2Mobile causes some confusion.
… also that they have their own WCAG2Mobile document it is confusing when the advice differs as a whole.
ChrisLoiselle: The problem is bigger than use of the term "view". It's worth filing an issue on this specifically, but think there needs to be a conversation with the facilitators regarding the broader concerns.
bruce: We aren't adding a definition of "view" to WCAG2ICT, right?
maryjom: No, no plans to do that
Gregg: This is a future state, so since WCAG doesn't use the term "view" it's problematic to use it in WCAG2Mobile.
ChrisLoiselle: The WCAG2Mobile isn't enforceable - none of the current standards use this term.
Gregg: EN 301 549 can't pick up new terms used in WCAG2Mobile
… at least not this late in the process.