See also: IRC log
http://w3c.github.io/dpub-pwp-ucr/
<tzviya> https://www.w3.org/annotation/wiki/Use_Cases
Tzviya: we need to add more robustness to these
<tzviya> you can edit here: https://github.com/w3c/dpub-pwp-ucr/blob/gh-pages/index.html
9.1 Personalized Experience
Alice, a dyslexic student, downloads a textbook and proceeds to personalize the material with larger font and different contrast.
Tzviya: A user wants to adjust a
textbook to her specific needs
... , example 1 a dyslexic user wants to use Dyslexic
font
... , example 2 a user with low vision wants to increase the
font size
... , example 3 a blind user wants the material read to
them.
... , maybe these are separate use cases?
Deborah: I think these are all separate use cases.
George: for dyslexic user wants to use a a different font, but separation between words or between lines. then AT auditorially they would want the words highlighted as they are read. They may not just to have a single word but my want to highlight separate sentences or lines, chapters etc..
Tzviya: we dont want to make this an accessible document but more general in nature
Deborah: this use case is for a user with dyslexia. But this use case could also work for … a user with low vision, a user with seizures issues etc… this use case could be used for these other host of specific users needs.
Tzviya: a new Research Questions group and one area is personalization
George: is that Jason White's new group?
<dkaplan3> Each separate use cases: a dyslexic user; a low vision user; a user with seizures; a user with color blindness; a user with migraines; ... etc. All the user stories. We certainly don't need to write them all, but we can write narrowly, and reference broadly.
Tzviya: Yes
George: trying to extract the uniqueness for portability is hard to do, without repeating all of WCAG
Deborah: what are we saying which is DPUB has something to add to, or something to say that gives a new light or adds richness to the conversation. A user with dyslexia wants to change the font. but sometimes users are using web browsers and are using e-readers. and EPUB uses web standards but using your kindle and there you want your personalization where is where DPUB has something to add.
tzviya: personalized reading, even with these are already defined in WCAG, but defining these here is worth doing. adjustable fonts, contrast, color, size etc….
Deborah: HTML falls down because they haven't defined them and is re-implemented a thousand times in various JS implementations.
Tzviya: what we have now is a
personalization use case
... , pick a disability and then we can clarify that this also
applies to a host of others.
... , so deborah pick a disability.
... , Alice, a dyslexic student, downloads a textbook and
proceeds to personalize the material with larger font and
different contrast.
<George> A low vision user needs a black background with white text. This provides to the low vision person best view of the text. This also benefits people who want to read in a dark room.
Tzviya: , we may want to say that she wants to use a font that serves the dyslexic community
George: Not sure if this is what you want but could then expand on how this could be. Night mode,
Tzviya, good in a dark room not to disrupt the person sleeping beside you.
Deborah: so stick with the dyslexic user and expand this. I can write this up and add the PS onto this for other disabilities including but not limited too.
Tzviya: we need this a draft by
sometime in August.
... we need something by July 7th.
... we should use this as a guide on how to write the
use-cases
<scribe> scribe: clapierre1
Next Use Case
9.2 Adding Alternative Media
As a publisher of accessible content, I need to add content such as a braille style sheet, image descriptions, or video captioning (text / descriptive audio) to a PWP previously published by a third party.
Tzviya: I dont think we need the last phrase
Charles: is this media overlays?
Tzviya: no, ie Bookshare making
content available
... , multiple versions like braille as well as HTML
... , that is one use case
... , is Braille added to a PWP the same way it would be added
to the web?
George: the only time if it is
preformatted Braille, 99.9% of time is that it is done on the
fly.
... , you could use 64bit unicode that show the dot patterns.
APH might, or library of congress. No one else will read them
but they are optimized for a particular group of people.
6dot/8dot / computer braille
charles: wouldn't we do the same in a pwp with a web.
Tzviya: is the use case we need to sync with braille? I am trying to see where this fits the Portable or Publication. or does the web not really support Braille. Maybe we need to ask someone else
George: Lloyd, Jason, or
Keith
... , the publication can be transformed into Braille by the
user but that is just taking the text and sending to the device
which does the transformation. If someone wanted to publish in
a Braille performed braile then it would be a separate
rendition
Tzviya: a PWP must be transformed
into Braille.
... , since Braille is not a web format.
Deborah: Braille is not a web format in the same way that letters are not
George: its a font.
... you can't deliver it as an image.
Deborah: its not just that… do cleaver things with unicode, or transpose things . it must be content meaningful in Braille.
George: with 64 char. you are
limited and there are escape codes that you have infront of it.
where abcde are the same as 12345 but has an additional escape
char ahead of it.
... , Publisher of braille must be able to have a complete
braille rendition
... , same requirement for Braille as TextToSpeech both are
translating it and putting it into something else.
Tzviya: PWP must be translatable into Braille, and the two statements it must be real text that is translated, and the same real text is used by a Text to Speech engine.
George if we can get 1 model down like we want the rest will be easier.
Tzviya: Charles can you add this to the use case then?
Charles: Yes
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) Succeeded: s/…,/Deborah:/ Found Scribe: clapierre1 Inferring ScribeNick: clapierre1 Present: Charles_LaPierre George_Kerscher WARNING: Fewer than 3 people found for Present list! 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: 24 Jun 2016 Guessing minutes URL: http://www.w3.org/2016/06/24-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]