See also: IRC log
<trackbot> Date: 04 November 2015
<AWK> +AWK
<allanj> close item 1
<laura> Scribe: Laura
<allanj> open next item
<AWK> LVTF wiki: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page
Jim: Wants to discuss purpose of
our documents.
... Some are internal docs some may be useful for others.
<shawn> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/LVTF_Documents#Deliverables
Shawn: We may want to polish some
docs.
... Some wiki pages may be background.
<Wayne> wayne+
Jim: Some may be useful for an appendix.
Shawn: Want to be careful of referencing Wiki pages.
<Wayne> scribe: wayne
Jim: Shawn, maybe we can refer to the following documents:
<allanj> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/LVTF_Documents
<laura> scribe: Laura
AWK: Requirement doc would be in TR space.
Jim: Requirements Doc has 2 primaries and a secondary purpose.
AWK: Change it to a Low vision user requirements doc.
Shawn: Need to decide where to point designers and developers.
AWK: How much front matter is needed in ta TR doc? We can try to minimize?
…Should have document as a note.
Shawn: Can we have something else more interesting?
<allanj> laura: user stories would help with informing developers and others about reading the web with low vision
<allanj> ja: link back to requirements doc
Laura: Maybe go back to having user stories. Scenarios.
AWK: Need clear set of requirements for different groups.
…not sure how to differentiate.
Wayne: Likes the arrangement.
<allanj> perhaps in the requirements, we can say this requirement is a content requirement, or this is a user agent requirement, or both
[discussion on where to point people]
AWK: Need to be sure to have something that talks about delta.
Jim: Some may be hardware or software. Shouldn’t limit scope.
Wayne: May have to mention older tech.
AWK: If X is a requirement make it clear that content authors don’t have to worry about it and user agent will handle it.
Wayne: We want an end result not worried about how we get there.
Jim: Focus on general needs and specific problems can fit into that.
…Need to quantify.
Jim: Do we want to set priorities?
Wayne: just put them out there.
Shawn: Hesitation - if we have to set levels later, maybe good to indicate some priority now?
Wayne: Limit ourselves to what impacts reading and usage.
Shawn: There is a priory to some of these.
Wayne: Maybe we don’t need to list them in this doc.
Jim: Have that debate later?
Wayne: Yes.
Shawn: We can decide that later.
AWK: Leave the research section to later.
<allanj> +1
Shawn: Perhaps include them but
use them as examples.
... Be careful what we are including are broader issues and not
get lost in details.
Jim: Maybe have general user story for each section?
…could go either way.
Shawn: People always want a checklist. Can have a filter.
<allanj> +1 Low Vision User Requirements
<allanj> +1 Low Vision Users Accessibility Requirements
Wayne: Maybe “Wayne: Low Vision User Accessibility Requirements”
Laura: +1
trackbot, end meeting
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Hesitation if we have to set levels./Hesitation - if we have to set levels later, maybe good to indicate some priority now?/ Found Scribe: Laura Inferring ScribeNick: laura Found Scribe: wayne Inferring ScribeNick: Wayne Found Scribe: Laura Inferring ScribeNick: laura Scribes: Laura, wayne ScribeNicks: laura, Wayne Default Present: jim, Shawn, AWK, Wayne, Laura Present: jim Shawn AWK Wayne Laura Regrets: bruce Erich Srinivasu Alan_Smith Bruce Found Date: 04 Nov 2015 Guessing minutes URL: http://www.w3.org/2015/11/04-lvtf-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]