Setting up a conference call on accessibility metadata, especially accessMode/mediaFeature for Thursday, 9/26

I've made enough progress and heard back from enough people that I'd like to propose a call and agenda for tomorrow, Thursday, September 26 at 8:00 AM PDT. If we need to, I'd like to also set a call for Monday at that same time.

The call details are on our wiki, https://wiki.benetech.org/display/a11ymetadata/Project+Overview
Weekly Meeting
Schedule: Thursday, September 26, 8:00am PDT (California), 11:00am EDT (Ontario, New York), 4PM in London and 5 PM on the contrtinent
Conference call: 1-866-210-1669 (US toll free), 1-404-835-7069 (international), code 7203478#
Etherpad: (9/26/2013<http://piratepad.net/ci5bmBFCwR>)
IRC: Freenode.net<http://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.  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.

I've not accomplished all that I wanted to at this point, but I have enough to have a discussion.
>From the last email, here's the list and the progress


  *   a recording of the demonstration that Madeleine did on the second day of Moscow, showing accessMode and mediaFeature in action

See http://www.a11ymetadata.org/accessibility-metadata-in-action-at-teachers-domain/

  *   a general framework for accessMode and mediaFeature for content, which will provoke some discussion, I'm sure.

Avalailable on the wiki.. http://www.w3.org/wiki/WebSchemas/Accessibility#Access_Modes_Media_Features_Framework:_a_tabular_view
(I'll be doing use cases beyond Madeleine's tonight).  This is the prime purpose of the call. There are also comments on this in the issues list. http://www.w3.org/wiki/WebSchemas/Accessibility/Issues_Tracker#What_is_the_goal_of_mediaFeature.3F_.28conforming_or_informational.29


  *   Moving the current spec to a baseline, .6, including a few changes in bookformat
  *   An updated, edited and more useful issues list on the public vocabs wiki to drive the next calls

I have updated some of this.  See http://www.w3.org/wiki/WebSchemas/Accessibility/Issues_Tracker
The key items updated are on ATCompatible, with references to DAP (I propose that we remove ATCompatible from the specification) and references of the is/has adaptation to the current collections work being done and "isBasedOn" (both lower level issues... lower in importantce than accessMode and mediaFeature.)

On Sep 23, 2013, at 7:16 AM, Charles Myers <charlesm@benetech.org<mailto:charlesm@benetech.org>> wrote:

First, my apologies... after our conference calls in Moscow two weeks ago, I've been a bit preoccupied on other activities (including a general framework for understanding the metadata framework and loads of data into a Learning Registry, working out good search terms).  All good, but it took away from the process of getting to closure on the schema.org<http://schema.org> proposal. I'm back.

To get a sense of urgency back into this, I'd like to get some conference calls scheduled to start hashing things out (and to get the email thread resuscitated). My proposal would be that we plan two calls for this week (Tuesday and Friday) and then one for next Monday.  I do not expect that we'll need three, but I'd rather plan ahead for people's calendars and then cancel if we've accomplished our goals. Our issue with calls is finding a useful time , as we span North America and Western Europe, with possibilities in eastern Europe and Australia.  We've tended to do calls in the early morning in California (7-9 AM PDT, pushing to 6 AM if required), which accommodates western Europe well. I plan to put out a "doodle" on this in a few hours, but would first like to know who cares to be in the calls... it doesn't make sense to invite the w3c public vocabs list.

The specific requests are:

  *   Let me know if you want to be on the calls (reply just to me, not /all)
  *   Let me know if you feel that you must be in the call, or consider yourself interested more than crucial
  *   Let me know if there are any times that are better or worse (and the timezone you're in)

When we do get these scheduled, I will send the information out to both of the mailing lists and this group of people.

I'll be sending out a set of emails today that include

  *   a recording of the demonstration that Madeleine did on the second day of Moscow, showing accessMode and mediaFeature in action
  *   a general framework for accessMode and mediaFeature for content, which will provoke some discussion, I'm sure.
  *   Moving the current spec to a baseline, .6, including a few changes in bookformat
  *   An updated, edited and more useful issues list on the public vocabs wiki to drive the next calls

On 9/16/2013 9:10 PM, Gerardo Capiel wrote:
Chaals,

I agree that mediaFeature is the most important property here and I think you're right that we need to be thinking about how we can make implementation easy for developers of search software. Your point on accessMode is also particularly strong when we consider that many times users have already filtered out a lot of content by the type of resource they have chosen to search for.  For example, if a user is doing a video search on Google on Yandex, they have already narrowed the accessMode possibilities to visual and auditory combined.  If they are deaf, they are most likely only looking to filter their video search by mediaFeature equal to captions or transcript.  And if they are blind, they are most likely only looking to filter on mediaFeature equal to audioDescription or transcript.  The transcript choice is a fallback choice for both cases.

During the development of the proposal we did a lot of work on use cases and also relied on significant prior work.  Chuck Myers is compiling that work in a more consumable form and will be following up shortly.

Cheers,

Gerardo

Gerardo Capiel
VP of Engineering
benetech

650-644-3405
Twitter: @gcapiel<http://twitter.com/gcapiel>
Fork, Code, Do Social Good: http://benetech.github.com/



On Sep 11, 2013, at 1:05 PM, Charles McCathie Nevile <chaals@yandex-team.ru<mailto:chaals@yandex-team.ru>>
 wrote:

On Wed, 11 Sep 2013 18:43:06 +0400, Gerardo Capiel <gerardoc@benetech.org<mailto:gerardoc@benetech.org>> wrote:

Common use cases we have not really discussed much are based on what happens in integrated classrooms where teachers are trying to serve both students with no disabilities and student(s) with different disabilities.  Below are some use cases based on my experiences with users of our Bookshare web library and it's related applications:

[snipped some really good use cases]

Some of these use cases indicate a need for the user to know about the combination of access modes the resource uses and what adaptations exist within the resource to support the assistive technology used by the end user.  I believe that merging accessMode and mediaFeature into one property makes it harder for users to make those determinations themselves.

Yeah. I totally agree.

My basic thinking is in part conditioned by how I present this to engineers in Yandex, and in part by what I heard, which included several times that "accessMode isn't really that helpful and we rely on mediaFeature and a set of complex algorithms for matching".

As I see things right now, mediaFeature seems really important as a way to rank results for things that can be useful. I see accessMode as a quick way of removing things that the user simply won't want from that sorting process.

The idea is that if we have 200 resources, and 120 are unable to meet the user's need, we save a LOT of processing by eliminating them quickly. Then we run the more complex ranking algorithms on the smaller set of things that, in principle, *could* meet the user's *needs* - but not all will be equally preferred.

One way I am thinking is that I want to use accessMode as a shortcut to make it cheaper to do more careful checking of mediaFeatures, so users get an exact match.

I'll keep the use cases Gerardo posted, because they are along the lines I have been trying to build up. I think we actually need to make a lot of these, to work through the issues of how we best satisfy them.

cheers

Chaals

--
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
     chaals@yandex-team.ru<mailto:chaals@yandex-team.ru>         Find more at http://yandex.com<http://yandex.com/>



--
You received this message because you are subscribed to the Google Groups "Accessibility Metadata Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to a11y-metadata-project+unsubscribe@googlegroups.com<mailto:a11y-metadata-project+unsubscribe@googlegroups.com>.
To post to this group, send email to a11y-metadata-project@googlegroups.com<mailto:a11y-metadata-project@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.