<AWK> https://addons.mozilla.org/en-US/firefox/addon/nosquint/
<ChuckOp> +chuckop
<laura> + Laura
<Srini> +Srini
<AWK> Scribe: Regrets+ Jim
<AWK> Scribe: Wayne
<laura> https://www.w3.org/WAI/GL/wiki/Scribing_Commands_and_Related_Info
<AWK> Wayne offered to scribe
AWK: We should be careful sources we want to attribute source. If you heard without a source note that you need a source.
... The charter for WCAG WG appears to be approved. It is not public yet. We can create an extension.
Srini: I have created the sites.
<AWK> LVTF Wiki: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page
Srini: for Accessible Features for Users With low Vision, Assistive technologies for low vision
Chuck: I would apreciat pointers to tools and resources being referenced
<AWK> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/User_stories_-_use_cases
AWK: User stories and use cases. This will be built into a note.
<Ryladog_> +Katie Haritos-Shea
AWK: Today we will look at the use case stories and see if we agree, determine what we need , determine what we want to move forard
<AWK> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Overview_of_Low_Vision
<Srini> Wouldn't field loss and size limitations go in similar bucket?
<AWK> That page contains the list of categories I used
AWK: Fatigue looks like a factor for all of the above.
* Fatigue is a side effect
<laura> +1
<AWK> Wayne: There are different factors around fatigue
<AWK> ... sometimes it is from sitting in one position
<AWK> ... ppl with outer field loss need to move their head a lot and are fatigued by that
<AWK> ... common effect is that people often don't finish books or long resources
AWK: Go through the list and see what is need. Do some areas have too much, too little, ...
<Alan_Smith> + Alan_Smith
Case 1: Field Loss Peripheral
Srini: Field loss and size limitations may be grouped.
... People with field limitation can find it difficult if the font is too big.
<Srini> Yes, that's exactly what I meant.
<AWK> Wayne: if you need larger text you are also losing field area
<Srini> How about we call as Field loss and Size limitations? as a single category?
<AWK> Wayne: We need to talk about how field loss runs through other categories
AWK: Should we have size limitation under field loss?
... Field is the users behavior engaged in reading, Fatigue impact on the end user that effects their ability. Field loss what happens now, Fatigue happens over time.
... Fatigue happens to everyone. How do we quantify too much fatigue. Field loss happens when we talk about mobile devices. This is compounded with low vision
... Large size exceeds the box.
... Proximity of error alerts to enlarged focus.
... At what point where the lose enough vision to become a keyboard.
Chuck: That doesn't seem right. I doesn't seem correct.
AWK: Is there a point where it becomes more practical to use keyboard over mouse.
<AWK> Wayne: There is a lot to learn about the line between user agent and AT coming up
Allen: I still have interview them in this category. Document their work around.
AWK: That will be helpful.
... We will see a variety of strategies and be able to assess efficiency and determine what works
... Attempts to return using the browser back button. Is this a valid use case. Could a manufacturer claim that keyboard access is enough, or should the mouse available
laura: All her cases come from user case studies.
... These cases came from a teaching tool.
... The browser was turned off.
AWK: User needs to know how to get back.
... There is difference between the button beeing out of view from magnified screen vs. not there at all.
... Do we need break these up into groups of three the we pass around
... we need to add more content.
<Srini> agreed.
<laura> bye
trackbot, end meeting
<Alan_Smith> Thank you.