Meeting minutes
Announcements
Mary Jo: No date on WCAG2Mobile comments. JJ is trying to finish document by end of year.
Open issue in WCAG2ICT and then move to WCAG2Mobile when we feel we can give proper feedback.
<PhilDay> Draft issue for WCAG2ICT TF to discuss prior to raising on WCAG2Mobile w3c/
<bbailey> https://
Bruce: I found spreadsheet a bit hard to work in. I will try the issue route in GitHub.
Survey results: Review proposed updates to 2.4.2 Page Titled
<maryjom> Link to results: https://
Mary Jo: Reminder - we did make some progress on 2.4.2 page title. We agreed on introductory and word replacement. We worked on that language. We made update to shortname.
<maryjom> Link to Proposal 2 PR: https://
We made updates to survey on proposal 2 PR.
Question 5: (3 of 3) Non-web Software - Notes
<maryjom> Link to survey results for Q5: https://
Mary Jo: Let us continue on the notes.
<PhilDay> Proposal 1 language:
<PhilDay> NOTE 1 (ADDED): As described in the WCAG intent, the name of a non-web software application is a sufficient title if it describes the topic or purpose.
<PhilDay> NOTE 2 (ADDED): Although not required by this success criterion, ensuring that individual windows or screens have a title (where that title describes the topic or purpose) addresses the user needs identified in the Understanding Success Criterion 2.4.2 Intent section, and is generally considered a best practice.
<PhilDay> NOTE 3 (ADDED): See also the Comments on Closed Functionality.
<PhilDay> Proposal 2 has no notes.
<PhilDay> Which approach do you prefer?
Results of survey 1 said keep as is. 2 proposal 2 as is , no notes, 1 proposal 2 needs notes.
Bruce: I think we are missing a verb in the PR.
Mary Jo: We may want to have conversation on closed functionality.
Gregg: I'm not sure as we re-worded that closed is a problem.
<PhilDay> Closed functionality may never have page titles, as there may be no windows
Mary Jo: Let us go note by note.
Phil, did you change your position?
Phil: I'm happy to change mind.
Mary Jo: I think we are in agreement. Notes one and two can go away.
<PhilDay> +1 to remove notes 1 and 2
Let us review closed functionality , which was note 3 added for 2.4.2
<PhilDay> https://
Closed functionality intent within closed functionality is discussed
<bbailey> +1 that each screen would need something like a title meeting 2.4.2
Gregg: If it has multiple screens, why wouldn't it be needed?
<Zakim> PhilDay, you wanted to say we still need note 3
Phil: I think I disagree. There are some closed systems that look like multiple screens but it is one. I think that is the use case we were after on the note. Locked systems already vocalizing
Gregg: If it has one menu and everything is driven from that menu, then it wouldn't have multiple screens. If it has multiple screens and multiple menus, then menu could change. That would give user need for title for wayfinding.
Gregg: I would need an example for context.
Phil: ATM with voice guidance. Each screen gives descriptor and cause to action . Doesn't typically voice a page title.
Gregg: Seems content would be present but not in page title , but still giving the data. For example, deposits then what the screen selection offers.
Gregg: Title on a page vs. landing on a page / screen and trying determine where you are.
Phil: Page descriptor is great, page title would not necessarily useful.
<bbailey> this paragraph is from before we split 2.4.2 between documents and software
Bruce: I would expect we would want to revisit this paragraph on problematic because it was written before we settled on having separate recommendations on 2.4.2 for document versus 2.4.2 for software.
<bbailey> From 2013 version: 2.4.2 Page Titled—where software is an integral part of hardware that provides a single function, such as a calculator or IP telephone, there is no need for a title;
Gregg: I can go along with it if we add it to end. If it includes a descriptor of new page when you arrive at that page. The descriptor would describe the page / screen's function. I.e. page title or something like a page title.
<bbailey> 2013 ref is just an FYI https://
Gregg: Page title could be redundant, but want to make it clear why.
Mary Jo: Similar language in 2013 as what Bruce just shared.
<maryjom> In 2013, the language was: 2.4.2 Page Titled—where software is an integral part of hardware that provides a single function, such as a calculator or IP telephone, there is no need for a title;
Gregg: 2.4.2 is talking toward systems that don't have multiple screens.
Mary Jo: I want to mention it is more than ATMs. We were thinking of printers that have menus. These may have entry field. That triggered the menu driven interface.
Gregg: Menu driven interface on selection gives you more options and those could serve as purpose.
Mary Jo: May not want to revisit and expand the terms too much.
Gregg: We should fix what we aren't happy with.
Bruce: The separate software from documents makes this maybe not necessary. We could just add note to state where it is problematic.
Bruce: We'd need to revisit the closed functionality due to what we've changed in 2.4.2.
Gregg: If you have the title, it should make sense. If it doesn't have the title, then you'd want to add one.
Phil: I agree with Gregg that we no longer need the note for closed functionality.
<Zakim> PhilDay, you wanted to say non-web software titled means we don't need the extra note for closed functionality
<maryjom> DRAFT RESOLUTION: Do not add any notes for the newly created Non-web Software Titled criterion.
<maryjom> DRAFT RESOLUTION: Do not have any notes for the newly created Non-web Software Titled criterion.
<PhilDay> +1
<ChrisLoiselle> +1
<GreggVan> +1
<bbailey> +1
<Mike_Pluke> +1
RESOLUTION: Do not have any notes for the newly created Non-web Software Titled criterion.
<maryjom> DRAFT RESOLUTION: Remove the closed functionality bullet for 2.4.2 Page Titled.
<bbailey> +1
<Mike_Pluke> +1
<ChrisLoiselle> +1
<GreggVan> +1
<PhilDay> +1
RESOLUTION: Remove the closed functionality bullet for 2.4.2 Page Titled.
Bruce: We would be removing the bullet from closed functionality?
Mary Jo: Yes.
<Zakim> bbailey, you wanted to ask if this the same as removing 2.4.2 from SC problematic for closed functionality ?
Question 2: Non-web documents proposal comparisons
<maryjom> https://
Prefer proposal 1 , had 1 vote. Prefer Proposal 2 had 2 votes. Prefer a combination of two had 1 vote. Someone voted for something else.
Gregg: I would make it non web documents. As for the note, the name meaning name within the document or file name?
Gregg: media file reads to me as file name. Do we mean file name or name of document ? We should make titles and file names or whatever we mean.
It reads as it is sufficient if it does what it says. The meaning of name would dictate interpretation.
Mary Jo: We didn't change language.
Gregg: Title name and file name. Not clear what it is intended.
Mary Jo: A document , for example may be described there.
Gregg: This one says have titles that describe topic or purpose.
Mary Jo: Discusses with Gregg about descriptors vs. titles of videos for use cases.
Mary Jo: What did WCAG mean for how these are served up?
Mary Jo: I don't think it was about content of document. I think it was about knowing what the document was.
Gregg: Why was it put there? So a person that is Blind has ability to know what the file (document) is about.
Gregg: I would say that requiring of title would be important for non web document.
Gregg: Counterpoint would be a letter based document , content contained in letter is known once they read the letter.
Mary Jo: For example, movies like the Matrix. What is that movie actually about?
<bbailey> i think this another example of 1.1.1 "descriptive identification" versus "describe topic or purpose"
Gregg: I think we can find issues with both when reviewed in depth.
Gregg: For example, untitled number 2 , is not an unique identifier.
Gregg: Same for plays, artwork.
<PhilDay> I think we might need to pick this up next week
Gregg: I think we need to think through art work or works of art. The examples need to walk through a bit more.
<bbailey> w3c/
Mary Jo: Read through PR comment from Bruce. Thumbs up or down on change please.
<bbailey> topic purpose or name of the work
Gregg: Topic describes name, purpose or name or work.
I need to drop as well.
<maryjom> Topic, purpose, or name of the work - to solve non-web document application of 2.4.2
sorry, needed to go to another meeting.
<GreggVan> non-web documents have title that describes topic, purpose, or name of the work
<GreggVan> If non-web documents support a title, it describes topic, purpose, or name of work