W3C

- DRAFT -

Digital Publishing Interest Group Teleconference

30 Sep 2013

See also: IRC log

Attendees

Present
Frederick_Hirsch
Regrets
Peter_Linss, Bert_Bos, Vladimir_Levantovsky, Tom_DeNies
Chair
SV_MEETING_CHAIR
Scribe
azaroth

Contents


<trackbot> Date: 30 September 2013

madi: /me is Rob Sanderson :)

<ivan> Guest: Jean (JeanKaplanksky) Kaplansky, Aptara

scribe is azaroth

<fjh> ScribeNick: azaroth

Madi: Minutes of last week. Any questions from last week?
... Please register for TPAC meeting.

Ivan: Even sooner than as possible. Hotels are filling up and getting to China takes a long time to organize.

mgylling: My invitation was rejected by the embassy. Missing a physical street address and they haven't gotten back to me yet.
... last week we asked plinss to confirm if we can have a slot with CSS, but he isn't here this week. Need to confirm or not still.

<liam> [ CSS meets on Wednesdays ]

Madi: Shall we move on to new members.
... ??? is a new member.

SuzanneT: Primarily involved in accessibility.

<madi> Jan McSorely

Jan McSorely: Also from Pearson, asked to join

<ivan> Guest: Jan McSorely, Pearson

madi: Three new use cases on accessibility and personalization

<madi> http://www.w3.org/dpub/IG/wiki/ReadingDisorder_UC#Accessibility

madi: would like to walk through them. Pretty simple ones so far, just the tip of the iceberg

Jan: Suzanne has other use cases too. Would love guidance on how to make these ones better
... My role in pearson - just hired in june as accessibility specialist. More of assistive tech specialist.
... Use cases are about students with disabilities. written for computer based assessment.

madi: Accessibility in education is critical
... Need to make it a priority

Jan: Student with learning disability for reading. Does better with graphic support. Text highlighting etc improve comprehension
... Also likely to have difficulty with memory and learning new material. School would like text that student can hear and see at the same time
... Specific use cases to distinguish different features
... Hard to get access for free for kids to electronic texts. Bookshare and learning ally two services that are federally funded. Provide access to digitized text.
... One records audio and working on sync with highlight in text.
... Can read in logical order, rather than top/bottom left/right
... In schools, educator needs to know copyright restrictions
... accessible everything is the ideal solution
... Have to jump through hoops at the moment.

SuzanneT: Would student end up getting access?

<brady_duga> aagt is a bug in zakim - I queued up as aagg to figure out if was me, then queued down once I was duga, but duga wasn't on the queue

Jan: Majority of the time they don't. Good IT team can help. Library of Congress has strict interpretation of who can get access.
... Medical doctor has to say physical issue causing a learning disability

madi: Do we want to capture these use cases, or too complex?

mgylling: Very big field, with lots of new things coming up. eg APIP
... What we're doing in this group is to focus on w3c technologies

<ivan> Guest: Karen (karenm) Myers, W3C

mgylling: metadata important, accessibility as well. Need coordination moving forwards.

<alex> I am new to the group. Alexander Garcia, from the American Psychological Association

mgylling: APIP and PNP are good, attempting to address parts of the problem.

madi: Relations and dependencies
... ?

mgylling: We want another field to point outside the w3c
... External relevant groups/specifications. Template for use case in the side bar, where the fields are defined. Should clarify

<alex> which is the url for the template?

tzviya: This brings to mind other orgs, such as Benentech
... seems like there's more than one use case here. read aloud is one issue, direction is another, time is maybe not addressed in a spec

SuzanneT: Third party to adjust the time on testing for education

tzviya: Like the category education professional.

mgylling: Categories still open

<Pdanet> It's Benetech : http://benetech.org/

ivan: We have to work on these use cases to separate issues on w3c and not.
... Have a guest from benetech in the group, so may participate. More general question, already began to set up task forces into areas.
... wonder if accessibility in general should be a task force?
... Lots of things that are inter-related in use cases.

mgylling: Agree. What we've been missing so far is enough people to start thinking about it.
... know that Rich Schwerdtfeger with IBM, prominent figure in WAI, is hopefully going to join soon.
... To accelerate the creation of group we can announce and start marketing it to people interested

Ivan: If Benetech joins IG, they will be interested in area as well. So will have enough muscle

tzviya: Worked with accessbility orgs over the summer, will be follow up. happy to reach out to groups, several would be interested in joining

+1

mgylling: First use case, how does it relate to PnP?

jan: Specific information about the user needs. Lots of theoretical stuff in the IMS standard 1.0, so accommodations to say that students can have access according to their needs
... so some students allowed to have passages read aloud in a test, for example. Which can be controversial.
... Other issues about braille that don't have a good handle on. Would be beneficial for w3c folk to be involved so can bring issues to the table
... eg difference between right by law and technically possible

mgylling: Want listing of relevant specs. Turn acronyms into links to specs.

Jan: Put schema into a word doc to work through. Can post that.
... Maybe better understanding of where they're going

Ivan: Education group in W3C is clear. Accessbility metadata - what are you refering to there?
... Know there's one for schema.org. This one?

<mgylling> "Relevant W3C groups" should include IndieUI: http://www.w3.org/WAI/IndieUI/

Madi: Only reference that I had. so I added it.

<mgylling> … which has some overlap with PNP, possibly

Ivan: Work with the accessbility people to get the right specs, etc.
... Fear is that there isn't such a group
... No dedicated group for accessbility metadata directly

<tzviya> what about http://www.w3.org/TR/WCAG20/?

mgylling: Just posted one (IndieUI)

<tmichel> thierry rejoining ...

mgylling: Preferences if you will

azaroth: Could put EPUB back into this new field. So should go back to the previous "fixed" use cases

madi: Moving on...

<madi> http://www.w3.org/dpub/IG/wiki/Dyslexia_UC#Accessibility

madi: Accessibility has lots of unique use cases

Jan: Dyslexia have different types of needs, several related to visual perception
... Student uses assistive technology, can annotate, bookmark and navigate due to DAISY formatting
... Some need fonts, some not. Some fonts are weighted, eg Open Dyslexia font with differences in ascenders/descenders
... Need control over this. Adjusting whitespace necessary too.
... Colored overlay capabilities to change fore/background.
... Ability to bookmark, annotate.
... Text highlighting. Research shows that its beneficial for students to do this.

Ivan: Typical case where we combine use cases. Lots of use cases already on annotation.
... This is what we want.

<alex> sorry

mgylling: Agree, relations and dependences field. See the web of things being linked together

<alex> but which is the url for the use cases?

Jan: http://www.w3.org/dpub/IG/wiki/UseCase_Directory#Social_Reading_and_Annotations

azaroth: Will link to accessbilities cases

mgylling: We're collecting requirements on the open web platform for things it can't do for us yet

<ivan> directory of use cases

mgylling: most of them are things that can't be done in OWP. Eg customizing fonts and colors hard to get to work satisfactorily
... so all these bullets are great input for things we need to work on
... don't understand the first one

Jan: In terms of what they're using, have DAISY formatted books. Not familiar with EPUB3 capabilities.
... Not may be the right place for that bullet

mgylling: Requirements should be like the rest. Imperative functionality. Features.

Jan: Will take that out and talk about features. Navigation capabilities by chapter, page etc.

Madi: Go further down, revise EPUB/DAISY from relevant groups
... Third accessbility case

<madi> http://www.w3.org/dpub/IG/wiki/CerebralPalsy_UC#Accessibility

Jan: One thing important is that the students have access to different types of assistive technology. Would be good for the content to be compatible with the technology, tech compatible with guidelines
... Student has poor fine motor skills and speech. Switch interface for wheel chair and computer. Word prediction software.
... Can't use voice recognition software. Need to navigate easily.
... Full keyboard navigation, nothing mouse dependent
... Word prediction software needs contextual algorithm. very different from phone.
... based on word we're trying to type on the phone, not the sentence.
... Customized to student's vocab and context. In testing situation has to be turned off
... Not sure that it has relevance in DPUB?

Ivan: Not something I can attach to anything in W3C.

Jan: How would you document it? Important to know what assistive technology they might use?

Ivan: Important because outsiders need to know requirements. Whether realization hits some big problem when relying on W3C technology?
... Some sort of thought experiment about how they should be implemented, building blocks that must be around, in order to do that
... Should be able to answer eventually
... Features that we have to take care of.

Jan: How to document them in the use case? Part of Narrative?

Ivan: Narrative is fine with me. Kind of work task force will have to do is the thought experiment. What does implementation require

SuzanneT: These use cases help us think of the problems, can be parents of more specific ones

madi: Anyone want to add to this? (...) Okay. Thanks to new people.
... Eager to work on this sort of thing, so thanks for your work Jan. Thanks to Rob for scribing.

<madi> oops, I just left. Thanks everyone!

mgylling: Started pagination task force last week. Want to make sure there's a time line. Dave anything to say?

Dave Cramer: Started early work to describe pagination. Something concrete to respond to.

scribe: Plan is to share before next week's call.

mgylling: Will reserve time next week for pagination. Many people travelling next week to Frankfurt

<Pdanet> Absolutely ! on the way to FRKFRT

mgylling: accessibility task force - do we have a volunteer lead from Pearson?

SuzanneT: Happy to lead that task force

<madi> Thank you Suzanne!

mgylling: Suggest devote time next week to how to build the group and structure the work

<madi> Markus: call me at (44) 2-7 010 2335?

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2013/09/30 16:00:34 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/madi/SuzanneT/
Succeeded: s/???/tzviya/
Succeeded: s/???/SuzanneT/
Succeeded: s/Rich Sw???/Rich Schwerdtfeger/
Succeeded: s/???/Madi/
Succeeded: s/SuzanneT/Jan/
Succeeded: s/???/SuzanneT/
Found ScribeNick: azaroth
Inferring Scribes: azaroth

WARNING: No "Topic:" lines found.

Present: Frederick_Hirsch

WARNING: Fewer than 3 people found for Present list!

Regrets: Peter_Linss Bert_Bos Vladimir_Levantovsky Tom_DeNies

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 30 Sep 2013
Guessing minutes URL: http://www.w3.org/2013/09/30-dpub-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]