Accessibility DPUB Task Force Weekly Meeting

27 Oct 2016

See also: IRC log


Charles_LaPierre, Avneesh, Deborah_Kaplan, George_Kerscher, Mia_Lipner, Tzviya


<scribe> ScribeNick: clapierre

Section 2.1.1 a11y focused and 5 braille use-cases

• As Nemeth Braille is commonly used as a means to access math tactually in education, BigBox Publisher has added Nemeth Braille examples to its publication, in addition to the MathML content.

• James, a musician, requires that the musical score within a publication come preformatted in braille music notation in order to read it, as he uses freely available assistive technology which does not have braille music translations built in.

• A class of students is reading a book in which poems are pictorially presented in different shapes. To have a comparable experience as her sighted classmates, Lisa, who is visually impaired, needs access to the material in braille. Because of the way the poems are presented, she actually needs the content in preformatted braille that provides an equivalent precision.

• Working with colleagues on some research issues Joos, who is visually impaired, needs an alternative access for the various articles the research work is based on. He chooses an audio rendition of the article content, because he does not master braille well enough.

• BigBox Publisher needs to add content such as a braille style sheet, image descriptions, or video captioning (text/descriptive audio) to a web publication.

deborah: we should figure out which of the braille ones is most important/least intuitive, to keep in there.

Mia: nemeth is important but Nemeth tables in certain area's in STEM gets a lot of attention where music does not. the poem thing if they have only a 20 cell braille display, AT specific poem one. is important one but alternative ways a tactile graphic as a hard copy braille won't get that hardware braille display.

G: Nemeth is north america only not use. UEM is more generally used outside USA.

Mia: can we merge the nemeth and music one?

Avneesh: preformatted, music is not important is is more pre-formatting.

Deborah: I like the music one.

Tzviya: we show a usecase or two.

Mia: so we include the last one and add short examples preformatted.

Tzviya: the music one is a good example, and not sure if Nemeth also is well know. the last one is very clear but need further examples.

Mia: we could explain what Nemeth is in a footnote, commonly used in North America

George: preformatted aspect such as music, and something else that uses braille codes.

Tzviya: we can keep the music one in.

Charles: Yes keep music.
... what about the braille tactile?

Deborah: not a bad example, but has too many a11y examples in one place. alternative modalities deserves 2 but maybe not a tactile. a lot of bias a11y is all about blindness and we should not .

George: is the musician about an additional modality?

Tzviya: yes preformatted braille, and the other example is audio for the mother at work.
... its not just about a11y,

Deborah: so we will stick with alternative modality, we will rewrite the music one as math?

Tzviya: keep music one.

Deborah: and remove the other a11y ones?

busy mother of 5 and james the musician.

Avneesh: what about video? we only have audio and tactile.

Tzviya: we talk about video in other sections. we need to slim it down.
... we don't need all use cases just a sampling.
... it reads like a document for a11y and a few other things sprinkled in.

Charles: so we did our job too good?


Tzviya: it needs to be ballenced?

Avneesh: how will this document be used? I am worried that the requirement gathering will need these other use cases.

Tzviya: I wish I knew but I am pretty sure all of us will be involved.

George: the chartered working group that works on the spec, we can expect good representation from the accessibility field.

Tzviya: the reason I wanted to make sure it is not blindness focused. the # of people who thing accessibility is screen readers, I want to make sure there is a mobility example somewhere in here.

George: I am glad there is an example of TTS or audio, for second languages etc. and certain disability groups.

<scribe> ACTION: charlesl to remove excess use cases from section 2.1.1 [recorded in http://www.w3.org/2016/10/27-DPUB-minutes.html#action01]

<trackbot> Error finding 'charlesl'. You can review and register nicknames at <http://www.w3.org/dpub/IG/track/users>.

<scribe> ACTION: clapierre to remove excess use cases from section 2.1.1 [recorded in http://www.w3.org/2016/10/27-DPUB-minutes.html#action02]

<trackbot> Created ACTION-66 - Remove excess use cases from section 2.1.1 [on Charles LaPierre - due 2016-11-03].

Tzviya: I think the entire DPUB should read this over and send questions to the group.

George: for the call on monday will we have a version that doesn't keep moving?

Tzviya: we are still working on github.io does that work?

George: I would just like to read the whole document without it changing on me.

Tzviya: what I send out later today or tomorrow should be static .

George: I will find a chunk of time over the weekend where I can digest it.

Tzviya: most of the questions are sections that need a little rewording.
... we do have that new accessibility appendix which is good.

Deborah: Tzviya, question on pagination, and before I bring it up just wanted to make sure i understand.

2.2.3 turn to page 123, both digital and phsical book to turn to the same page. the electronic edition with font size. pagination means two things. the physical (visual breaking) and it means this is an electronic version where the same page #137 needs to mean the version in the print and not the blowed up font page which would be different than in the print book.

Deborah: I personally have ended up in conversations because w3c pagination to mean both things so we don't define what we mean in this document.

Tzviya, if we change that last bullet, turn to page 137, that "regarless or layout, personalization font size etc…"

Deborah: yeah that could work. I can rewrite this.

Tzviya: I will be adding this to my list of topics

Avneesh: we use the term "Page-Marker" no matter what personalizations you have added.

Deborah: it is not clear what meaning of the terms.

Tzviya: this is in section 2.2.5
... I will add this to the list on monday but Deborah if you want to start please go ahead.

George: we need to harmonize the vocabulary between publishing and W3C

Tzviya: yes, like Versioning is one of those hot topics.

Avneesh: when do we need to update the DPUB group about the WCAG things in parallel.

Tzviya: we haven't done a Task force update on monday.

Charles; ok we can do that.

Summary of Action Items

[NEW] ACTION: charlesl to remove excess use cases from section 2.1.1 [recorded in http://www.w3.org/2016/10/27-DPUB-minutes.html#action01]
[NEW] ACTION: clapierre to remove excess use cases from section 2.1.1 [recorded in http://www.w3.org/2016/10/27-DPUB-minutes.html#action02]

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2016/10/27 15:37:57 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found ScribeNick: clapierre
Inferring Scribes: clapierre
Present: Charles_LaPierre Avneesh Deborah_Kaplan George_Kerscher Mia_Lipner Tzviya
Got date from IRC log name: 27 Oct 2016
Guessing minutes URL: http://www.w3.org/2016/10/27-DPUB-minutes.html
People with action items: charlesl clapierre

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

[End of scribe.perl diagnostic output]