Minutes from the 26 January teleconference

Minutes from the ARIA weekly teleconference of 26 January are provided below
as text. They're also available as hypertext at:

http://www.w3.org/2017/01/26-aria-minutes.html

   W3C

                                                                                   - DRAFT -

                                                      Accessible Rich Internet Applications Working Group Teleconference

26 Jan 2017

   See also: IRC log

Attendees

   Present
          janina_, Rich_Schwerdtfeger, MichaelC, Stefan, Léonie, matt_king, MichielBijl, Joanmarie_Diggs, Joseph_Scheuhammer, jongund, JF

   Regrets
   Chair
          Rich

   Scribe
          matt_king, janina

Contents

     * Topics
         1. Testable statements and test files
         2. Test Harness
         3. HTML 5 Embedded content
     * Summary of Action Items
     * Summary of Resolutions
     _________________________________________________________________________________________________________________________________________________________________

   <richardschwerdtfeger> https://lists.w3.org/Archives/Public/public-aria/2017Jan/0048.html

   <mck> scribe: matt_king

Testable statements and test files

   <mck> rs: who can chip in?

   <mck> I am leaving in a couple of weeks and will be unable to work on it for a while.

   <mck> rs: stefan, can you help.

   <mck> stefan: if scope is limited, then probably yes.

   <mck> rs: I will point you to a couple of cases to work on ... stefan.

   <mck> rs: We have good examples of statements.

   <clown> I can do the next ones about accname.

   <mck> rs: Joseph, can you do some testable statements?

   <mck> rs: OK Joseph will do accname cases.

   <mck> rs: Joanie, question: there is one mac mapping that exposes a function for an action. How ref that in test harness?

   <mck> rs: This is for aria-haspopup = listobx.

   <clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaHaspopupListbox

   <richardschwerdtfeger> Expose AXShowMenu and AXPress actions

   <mck> rs: How do you represent that if there are no values?

   <mck> Joseph: that text was given to Andy when she was the editor. Was given by James Craig.

   <mck> Joanie: let me get back to you on that.

   <mck> rs: Where it says relations contains, can I use an ID?

   <mck> Joanie: for my platform, you can see if a relation of that type is there

   <richardschwerdtfeger> https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#combobox

   <mck> rs: take a look at last row of that table.

   <mck> you can have different types of relations.

   <mck> Joanie: that will work.

   <mck> I believe it is space delimited.

Test Harness

   <mck> rs: had good discussin with jon yesterday.

   <mck> Jon: Got pointers for AATA for msaa/ia2. And we will get it done.

   <mck> After we have the AT test adapter, students can work on test cases.

   <mck> RS: Will get together with Joanie next week?

   <mck> Jon: After we have some progress.

HTML 5 Embedded content

   <clown> https://www.w3.org/TR/html51/semantics-embedded-content.html#semantics-embedded-content

   <mck> RS: In aria 1.0, was decided not to do role for audio and video tag b/c required functionality we could not do with aria.

   <mck> Met with web components wg, and they want as much parity with html as possible.

   <mck> They had not thought about DOM apis for communicqating with script in an audio/video tag.

   <mck> This is just for parity.

   <mck> We need to gather some use cases, and Janina will talk about them today so we can determine where to go with audio/video.

   <mck> rs: Leonie, did you follow the list discussion and see no work has been done on it since september

   <mck> Janina: May have cases wider than a11y

   <mck> We do not have a defined way of handling medai in html spec. Kind of a free for all. Media controller effort is dead.

   <janina_> http://www.w3.org/TR/media-accessibility-reqs/

   <mck> We have a set of use cases and requirements for a11y.

   <mck> We published in this note.

   <mck> It is result of 6 year effort that started at meeting at stanfor in 2009.

   <mck> The alternatives to a primary resource, which is what we call in the tag, we call it primary media resource.

   <mck> Text alt would be markup, not juststraight text.

   <mck> There is a list of alternatives that are text based.

   <mck> There is a list of binary alternatives, which could be a an audio file.

   <mck> Antoerh binary alt is signed captions.

   <mck> That is where internationalization comes in.

   <mck> Each language would have its own alternative track.

   <mck> There is the real time aspect, which comes into play with web rtc.

   <mck> Might be streaming a conference live.

   <mck> Say in CA with a conf that is being real time streamed.

   <mck> In CA, has to be 2 languages; required by law.

   <mck> There could be someone doing simultaneous live translation.

   <mck> So, the consumer needs to be able to choose the appropriate lang track.

   <mck> There is no overarching thing that pulls this together to be something you can access through the browser.

   <mck> Need to give consumer control over the experience, choosing language, size/postion of alt, etc.

   <mck> How to discover options.

   <mck> How do you set default choices.

   <mck> How to create a profile.

   <mck> This could also be used in a theatre.

   <mck> If we get it all right, it should work ver well.

   <JF> https://www.w3.org/TR/html5/embedded-content-0.html#attr-track-kind

   <mck> jf: tagging on to Janina, html introduced 2kind

   <mck> You can dfine subtitles, captions, and descriptions.

   <mck> Has a keyword of metdata for scripting.

   <mck> Gap in tagging or labeling binary alternatives.

   <mck> Have a gap there.

   <mck> Other problem: 2 ways of delivering the alternatives over web.

   <mck> Could be stand alone files downloaded on demand where track is a child of video element.

   <mck> On mobile, it is often delivered in band

   <mck> That it is, the alt is part of the mp4 file.

   <mck> How do we label the alternatives and get it exposed.

   <mck> Janina: Some of the alternatives may not be provided by the original producer.

   <janina_> scribe: janina

   <janina_> janina: Sometimes, the alternative media may be 3rd party produced

   <janina_> rich: Summarizes, what's available? What's set

   <janina_> rich: Summarizes: Does the AT need the track?

   <janina_> jf: Depends on AT

   <janina_> jf: Currently, track reserved for track

   <janina_> jf: Reserved for caption, text description, subtitle, etc

   <janina_> jf: Problem is the binaries; the audio recorded video description; the sign language video

   <janina_> jf: No way to associate the alternative to the primary

   <janina_> rich: Does the AT need access to the track

   <janina_> rich: You do want to know what's available, and you want to choose the ones you want

   <janina_> rich: Based on AT, or platform selection

   <janina_> jf: Or, could be website specific--on this site always show me X if available

   <janina_> rich: Not going to parse the content

   <janina_> janina: AT may need the texted video description to speak it

   <JF> Current values for @kind: subtitles, captions, descriptions, chapters, metadata

   <janina_> rich: Can the environment do the mixing?

   <janina_> janina: Yes, I prefer my video to a second audio device to ensure the screen reader isn't speaking on top of it

   <janina_> rich: This is where we need a piece like AOM -- to select and activate on a platform

   <JF> missing: Transcript, sign-language video, described audio...

   <janina_> rich: Believe there are 3 tightly coupled AOM releases

   <janina_> rich: Believe we need to document the use cases

   <janina_> rich: We can certainly put some attribs into ARIA 1.2 -- walk available tracks, etc

   <janina_> rich: Knowing which one is currently set would definitely be an attribute

   <janina_> rich: Also timed text?

   <janina_> jf: Yes, in the @kinds it's either TTML or WebVTT

   <janina_> jf: Currently, we're looking at client scripted controls

   <janina_> jf: Believe our challenge is just labeling

   <janina_> rich: We'll also need capability info

   <janina_> jf: Can you explain?

   <janina_> rich: So if you have text description in Spanish, but no Spanish TTS

   <janina_> rich: Stuff like that

   <janina_> rich: How sync'd? These binaries have to be sync'd

   <janina_> jf: That's why much is delivered inband

   <janina_> jf: Wonder whether we need a video manifest -- Here's what's available? What do you need

   <janina_> janina: That would be familiar to the Dpub people -- They declare all that

   <janina_> rich: So, doing this in ARIA, we don't have to be limited to what HTML has

   <janina_> rich: This is why I'd like to see capabilities

   <janina_> rich: I believe Web Components want to use components themselves, not html. Is that correct

   <janina_> leonie: One use case, the other is extending HTML

   <janina_> leonie: Which is why I blieve this needs HTML people in the conversation

   <janina_> janina: And I think also i18n for many of the same reasons as a11y

   <janina_> rich: Let's assume different types of tracks, with different data about them

   <janina_> rich: We could facilitate decisions about how to use those -- We could prototype that and then circle back to Web Platforms, AOM, etc

   <janina_> rich: asking JF and Janina to boil down the MaUR to a short expoze of the use cases

   <janina_> jf: Additional wrinkle, currently browsers poduce basic controls if you don't serve up your own

   <janina_> jf: But the assumption was always that authors would script controls

   <janina_> jf: We're going to wnat to insure that native browser controls expose this stuff

   <janina_> rich: Anyone not agree about having an audio and video role?

   <janina_> [crickets]

   RESOLUTION: Create an audio and a video role for ARIA 1.2

   <janina_> mc: Clarifying issues

   <MichaelC> Audio and video: https://github.com/w3c/aria/issues/517

   <janina_> rich: Video/Audio role issue to Janina

   <janina_> mc: Issue to document use cases to JF

   <MichaelC> Audio and video use cases: https://github.com/w3c/aria/issues/518

Summary of Action Items

Summary of Resolutions

    1. Create an audio and a video role for ARIA 1.2

   [End of minutes]
     _________________________________________________________________________________________________________________________________________________________________

Scribes: matt_king, janina
Present: janina_ Rich_Schwerdtfeger MichaelC Stefan Léonie matt_king MichielBijl Joanmarie_Diggs Joseph_Scheuhammer jongund JF


-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Received on Thursday, 26 January 2017 19:08:01 UTC