- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Tue, 29 Sep 2015 14:28:02 -0500
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- Cc: public-low-vision-a11y-tf@w3.org
- Message-ID: <CA+=z1WmJT8_OwQo014nqfqvfhfN02m9HeAr4Zue9oWjXM6oCHA@mail.gmail.com>
Ah, Clarity. I would call this (#6) a field issue. Also, #3, 4, and 5 On Tue, Sep 29, 2015 at 1:25 PM, Laura Carlson <laura.lee.carlson@gmail.com> wrote: > Hi Jim, > > We discussed this a bit at lat weeks meeting and I have subsequently > attempted to make this clearer: > > "A student is using zoom magnification software in an e-learning Web > based product. He attempts to return to a landing Web page from an > interior Web page by using the browser back button but it is disabled > in the product. Moreover, the e-learning tool's back button (and > navigation) is outside the zoomed-in field of view. This makes it > difficult to locate previous content. The problem could be solved if > the browser back button functionality was available, or if back button > functionality in the product was provide from within the zoomed > viewport, or if some other method of navigation within the set of Web > pages was provided. " > > Does that help? > > Thanks, > Laura > > On 9/29/15, Jim Allan <jimallan@tsbvi.edu> wrote: > > Hi Laura, > > reading #6 > > A person with albinism > > < > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Types_of_Low_Vision#Albinism > > > > attempts to return to a landing Web page from an interior Web page by > using > > the browser back button but it is hidden due to screen magnifier being > > zoomed in. This makes it difficult to locate previous content. The > problem > > could be solved if browser back button functionality was available from > > within the zoomed viewport or if some other method of navigation within > the > > set of Web pages was provided. > > > > I don't understand how this is a problem. Using a screen magnifier does > not > > prevent the standard browser keyboard controls (backspace or > ALT-leftArrow > > or the Mac equivalent) from working. So, the functionality is already > > provided. Or, am I missing something in this scenario? > > Jim > > > > On Mon, Sep 28, 2015 at 2:52 PM, Laura Carlson > > <laura.lee.carlson@gmail.com> > > wrote: > > > >> Hi Jim and all, > >> > >> > Agenda+ review of updates to user needs and categorization NEED MORE > (5 > >> per > >> > category) > >> > >> I wonder if some of the use cases under "Size Limitations" would fit > >> under "Field Loss"? I was going to move a few of the ones I wrote > >> there (#3, #4, perhaps #5) but am not sure. Would #6 perchance be a > >> candidate? > >> > >> Thanks. > >> > >> Best Regards, > >> Laura > >> > >> -- > >> Laura L. Carlson > >> > > > > > > > > -- > > [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>Jim Allan, > > Accessibility Coordinator > > Texas School for the Blind and Visually Impaired > > 1100 W. 45th St., Austin, Texas 78756 > > voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ > > "We shape our tools and thereafter our tools shape us." McLuhan, 1964 > > > > > -- > Laura L. Carlson > -- [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>Jim Allan, Accessibility Coordinator Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Tuesday, 29 September 2015 19:28:31 UTC