Meeting minutes
Agenda Review & Administrative Items
sajkaj: Announcements - we have media considerations after some edits following previous meetings
Media Considerations Followup https://www.w3.org/WAI/GL/task-forces/silver/wiki/Media_Considerations
sajkaj: have made a human readable diff. We have reverted the second paragraph of media considerations.
* reword not revert
"Each of these categories of media content may have methods for making them accessible—or not. There may be methods for some classes of persons with disabilities, but not for others. Whether or not accessibility methods exist, WCAG requires web publishers to apply all available context appropriate methods at the time of digitization, and then again upon any major refresh of the content. However, there are still additional situations that req[CUT]
sajkaj: we start general and get more specific as we progress
PeterKorn: reads the changes to break into two sentences: "An important part of WCAG Conformance are the specific requirements that are associated with individual WCAG 3 guidelines and outcomes. As of this publication, none of these have yet been created. Some guidelines will be explicitly identified as media related guidelines. Other guidelines may include media related outcomes, and those will be so identified."
<PeterKorn> Old: "An important part of WCAG Conformance are the specific requirements that are associated with individual WCAG 3 guidelines and outcomes, which have not been created."
sajkaj: we also changed the verb tenses
<PeterKorn> New: "An important part of WCAG Conformance are the specific requirements that are associated with individual WCAG 3 guidelines and outcomes. As of this publication, none of these have yet been created. "
sajkaj: Throughout the document we had referred to "techniques" (a WCAG 2.x term) this is now chanages to "methods" or for looser use "mechanisms"
sajkaj: Added a paragraph to the second editors note. Now includes: "We seek comment on what programmatically exposable metadata types and values are needed to express a full range of possible accessibility-related features in media. We also seek comment on how best to expose which specific ones are available to users within any particular media publication." This was in response to our discussion last Thursday.
<PeterKorn> Old penultimate Editors Note 2nd sentence: "We are looking for suggestions on if and how third-party tester should be able to identify and validate when media has limited rights."
<PeterKorn> New: We seek comment on whether and how a third-party tester should be able to identify and validate when media has limited rights."
sajkaj: Formalised the note under "Media with Limited Rights for Publishers"
In the final Editors not added the missing "or"
Wilco_: requests to break up the final sentence.
<PeterKorn> https://
Moves back to "Media conformance"
<PeterKorn> We seek comment on what programmatically exposable metadata types and values are needed to express a full range of possible accessibility-related features in media. We also seek comment on how best to expose which specific ones are available to users within any particular media publication.
JF: Agree this belongs here. Concern is how the metadata will be attached to the asset.
sajkaj: this is on APA's agenda and is being discussed with others. It has not been forgotten
it is beyond accessibility's remit to refine.
<Wilco_> +1
<ToddLibby> +1
PeterKorn: believe this has to be done by media type not a global mechanism and don't believe we can have a single general statement.
JF: agree with PeterKorn. We need to state we have questions and we don't know rather than avoid the discussion.
JF: suggest adding a sentence at the same location. Happy to draft something.
Rachael: Confirms we are on schedule for Tuesday
<JF> We seek comment on a number of outstanding issues related to metadata, including: * what programmatically exposable metadata types and values are needed to express a full range of possible accessibility-related features in media * how best to expose which specific ones are available to users within any particular media publication * What mechanism or mechanisms can be used to associate metadata to media assets
<PeterKorn> We expect the metadata types, values, and disclosure mechanisms will vary with the media, and will be described within the guidelines, outcomes, and mechanisms addressing media.
PeterKorn: suggests adding the above sentence as an alternative
<JF> WFM
PeterKorn: added that sentence at the top of the note
<Zakim> JF, you wanted to discuss a minor wordsmithing
sajkaj: what question do we want the WBS to ask? Propose is this ready to go into the next public working draft?
Sampling & Reporting -- Initial Use Cases https://docs.google.com/document/d/1YgiOg3CZz-LAVxRT0CWUTWHzyVa3UrjqdU4NvoyUZ_8/
PeterKorn: explains the document linked above and the three initial scaling challenge use cases detailed.
Did not get round to creating fictitious examples of the use cases yet
Wilco_: The base scenario - any site more than 20 pages is probably too big to test manually.
20 = arbitrary number
sajkaj: you need an actual number to put into a specification. Picking a number is difficult to have agreed
JF: The bigger problem is how to scope an evaluation? We would need a protocol for that to help people understand how to scope large sites.
<PeterKorn> "Large sites that may be static, but are still too large to have humans exhaustively evaluate in a reasonable amount of time"
Wilco_: Disagrees is definition of a scope outside of what we worry about
PeterKorn: has added a use case to cover the concern
"Large sites that may be static, but are still too large to have humans exhaustively evaluate in a reasonable amount of time"
sajkaj: we will develop a full range of use cases and then have to test and work out what an acceptable variation rate is
PeterKorn: suggest we stick to what we have done before - not trying to solve too early
Wilco_: question where do sampling and reporting overlap and why they are not two separate topics
PeterKorn: the challenges arising in both come from scaling so let's begin with scaling use cases
Wilco_: what if you have no budget and want to do accessibility?
sajkaj: I think you gave a use case for that
PeterKorn: Seems to be a resource challenge rather than scaling challenge
sajkaj: Lets bring the hair salon use case into the doc