Reminder of accessibility metadata call coming up in an hour (9:00 AM PDT)

I'm back and caught up on accessibility metadata from the calls of two weeks ago.  The eganda for today's meeting cal be seen below and at https://wiki.benetech.org/display/a11ymetadata/Next+Accessibility+Metadata+Meeting+Agenda

I also wrote our minutes from the last two meetings at https://wiki.benetech.org/pages/viewpage.action?pageId=58853548 and the issue tracker has been updated on the mediaFeature issue. http://www.w3.org/wiki/WebSchemas/Accessibility/Issues_Tracker#What_is_the_goal_of_mediaFeature.3F_.28conforming_or_informational.29_Do_we_have_this_right.3F

Note that we have a new conference call number this week.  And we will be back on a regular weekly schedule from this point on.
October 22, 2013 Accessibility Metadata working group call
Weekly Meeting
Schedule: The next call will be Tuesday, October 22, 9:00am PDT (California), 12:00am EDT (Ontario, New York), 5:00PM in London and 6:00 PM on the continent, 3:00 AM in Australia
Conference call: +1-866-906-9888 (US toll free), +1-857-288-2555 (international), Participant Code: 1850396#
Etherpad: (10/22/2013<http://piratepad.net/ci5bmBFCwR>)
IRC: Freenode.net #a11ymetadata (although more of the collab seems to happen in the etherpad)

The goal of the call will be a review of the open issues on the w3c wiki and get to closure on these issues and work these with schema.org representatives.  See issues<http://www.w3.org/wiki/WebSchemas/Accessibility/Issues_Tracker> and accessMode/mediaFeature matrix<http://www.w3.org/wiki/WebSchemas/Accessibility#Access_Modes_Media_Features_Framework:_a_tabular_view>. There will also be a discussion of the use of these attributes for search, as shown in the blog article.

The next call will be October 22 and then will settle into weekly meetings as required.

The public site is http://www.a11ymetadata.org/ and our twitter hashtag is #a11ymetadata.


Overall Agenda

New Business - We will start discussing this promptly at the top of the hour.

  *   mediaFeature - our goal is to get agreement on the mediaFeature properties, as noted in the issue list<http://www.w3.org/wiki/WebSchemas/Accessibility/Issues_Tracker#What_is_the_goal_of_mediaFeature.3F_.28conforming_or_informational.29_Do_we_have_this_right.3F>.  As noted in the last call's minutes, we did a deep dive into visual and textual transform features last time. I've editted the list down to reflect both new properties that we decided on last time and some of the simplifications that come with the extension mechanism. I'd like to reach a conclusion on those, both for the specific names but also for the general framework, so that one can see the extension mechanism.  I'd like to propose even that we segment this discussion into two parts... agreement on the current properties and then consideration of new properties (I want to see the discussion make progress)
     *   transformFeature - do we mike that name (against the "content feature")
        *   Finish discussion on visualTransformFeature and textualTransformFeature
        *   Consider auditoryTransformFeature (structural Navigation will be covered in textualTransform) and tactileTransform
     *   Review contentFeature side of the mediaFeatures starting from the proposed table in the issues list<http://www.w3.org/wiki/WebSchemas/Accessibility/Issues_Tracker#What_is_the_goal_of_mediaFeature.3F_.28conforming_or_informational.29_Do_we_have_this_right.3F>
        *   textual (note the removal of desacribedMath) - alternativeText, captions, chemML, laTex, longDescription, mathML, transcript
        *   tactile (note the simplication of braille to be the extended form) - braille, tactileGraphic, tactileObject
        *   auditory - audiDescription
        *   visual - signLanguage, captions/open
  *   ATCompatible
  *   ControlFlexibility and accessAPI (we'll be lucky if we get to this point)
  *   accessMode and the three proposals for the available access modes (this is a topic for a future call)
  *   is/hasAdaptation