See also: IRC log
<scribe> scribe: clapierre
title: Accessibility DPUB Task Force Weekly Meeting
Deborah: I am fine with this.
George: we were focused on W3C stuff, not ePub
Deborah: we should be clear
analysis of Digital Publishing Accessibility needs in W3C
... analysis of W3C documents with respect to Digital
Publishing.
... Digital Publishing and Accessibility in W3C Documents.
George: what about "Analysis"?
Deborah: does adding Analysis give more information
Charles: we will go with this for now, and see what DPUB says.
George: we should use W3C words here for Public Draft/Editors draft etc…
Deborah: we could look at mobile note or ask Ivan.
Charles: ACTION ask Ivan regarding #22
Deborah: I agree we should have PDF in the appendix.
Jean: I was at JATS conference and I asked a platform guys about accessibility, everyone was asking how to get their data into PDF.
Deborah: PDF is a huge part of
digital publishing, its difficult to make it accessible
depending on how they are made.
... , the important thing would be how to make accessible
PDF.
George: do you have a recomendation for us Lenard? maybe for printing but for a11y should we have a different view?
Leonard: WCAG itself is the standard. There are two key issues, WCAG has a section on how to make a11y PDF's .
Deborah: I knew that existed but forgot about it.
Leonard: PDF/UF is a open standard and it gets its guidance from W3C. If we start with those two things as guidance, we could do lots more, and asked people to draft content, but will leave it to you all on how much you need.
Deborah: PDF is a very well used
technology, here is some W3C specs, FDF is not a W3C standard
although it is a ISO standard.
... , these are important for people to know about just like
Diagrammar.
George: I know PDF/UA is a standard.
Leonard: UA universal access its goal is to starting with WCAG and how to make PDF accessible, and builds on things you would expect. PDF headers here is how WCAG understands headers and here is how PDF does headers and how to make those things accessible.
Deborah: one of the things in our gap analysis, sometimes WCAG has everything we need, why is there is a gap because the reading systems or production tools have a gap, not in the spec itself.
Jean: education needs to happen, just not sure how to make it happen.
Deborah: I though you can just
use acrobat and click make it accessible, but there is more to
that and it is an education thing.
... , thats a gap but it may not be a w3c gap
George: I am happy to add it to the appendix, authoring tools and reading systems are lacking in implementation.
Jean: thats a good way to put it.
Deborah: is PDF/UA and PDFA compatible?
Leonard: Yes.
George: do we have a decision.
Deborah: yes we will add it to the appendix, with links to the various standards and that there is a gap in reading systems/authoring tools.
George: I am on the PDF/UA so maybe I should draft this. I will put it together next week and send it out to Leonard and Charles for review and publishing to the note.
section 2.7 says
"The Gap: Current W3C WAI Specifications and Guidelines have poor implementation, probably due to lack of authoring tools, reading system support, and implementation guidance."
This is a general statement which may not be justified. It should specifically say which part of the guidelines (I suspect related to phonetic spelling) have a poor implementation.
Jean: didn't we go out of out way to let them deal with this?
George: we are not aware of implentations, w3c process requires 2 implementations, but we don't know of any
Deborah: this TF are unaware of the implementations
George: we do have 2 but are not in main stream publishing… but that is DAISY implementations… although now that ePub we may have it but whats the point we need to make here? we are not aware of comment implementations.
Deborah: sure thats right
Charles: will add we are not aware of any well known implementations within the publishing community.
Leonard: I am in the process of rewriting that.
Charles: Peter has agreed to write something up on this topic.
<lrosenth> changes for #30 are posted
Deborah: its a preference matter, and he has a better sense of style issues..
Charles: ACTION to bring in the table of contents of gap analysis into our note directly linking out to the various wiki pages directly.
Deborah: I do agree we should help where we can and maybe just decide how to do that.
Leonard: there is one small section on fonts, but there are others. user facing style sheets are deprecated but are required for accessible content.
Deborah: we assume there is personalization
George: Diagrammar, simplified language for cognitive, tactile images, and personalization automation of that content is huge.
Deborah: what we need to do is
provide more use cases… for PWP there is a lot of use cases,
common one never written down, which is if a control is a
visible button and screen reader accessible word that it show
me that for voice control.
... , diagrammar / 3D printing is a use case.
George: we had in diagrammar and on website, we went through 70 use cases we document, and built requirements from the use cases and linked back. you changed the website… where are those use cases from the first year of the DIAGRAM project from 6 years ago. If you don't have them I may have them.
Deborah: Leonard, do you have the use cases from PDF/UA.
Leonard: Yes I should be able to get you that.
George: we should be able to find existing use cases.
Deobrah: here are the action items. we need to ask Markus/Tzviya when the deadlines are for these. Charles will dig up DIAGRAMMAR use cases and Lenard will dig up the PDF/UA use cases. We will need to go through them to see what is relavent and do word smithing etc...
George: we should not delay the Note for this though.
Deborah: we will finish the note then work on the use cases….
Charles: Yes I will go ask Amaya where they are,
George: they were in a wiki at some point.
Charles: ok
... , see you all on the DPUB call to discuss this on
Monday.
George: is there a dial in option?
Charles: its the same # you called in here George
George: Oh it wasn't in the announcement of the meeting agenda
Charles: oversite, I will let
Markus know so that it is included from now on.
... thanks everyone.
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: clapierre Inferring ScribeNick: clapierre Present: Charles_LaPierre George_Kerscher Jean Deborah Leonard Regrets: Tzviya Mia WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Got date from IRC log name: 22 Apr 2016 Guessing minutes URL: http://www.w3.org/2016/04/22-DPUB-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]