- From: Erich Manser <emanser@us.ibm.com>
- Date: Thu, 23 Feb 2017 12:23:35 -0500
- To: "LVTF - low-vision-a11y" <public-low-vision-a11y-tf@w3.org>
- Message-Id: <OF1148C2C4.74905B69-ON852580D0.005F5AE5-852580D0.005F8B12@notes.na.collabserv.c>
Minutes pasted below and at link; http://www.w3.org/2017/02/23-lvtf-minutes.html Low Vision Accessibility Task Force Teleconference 23 Feb 2017 See also: IRC log Attendees Present allanj, Shawn, Erich, Glenda, Marla, StephenR, steverep Regrets Laura Chair Jim Scribe Erich Contents Topics CSUN User Agent Switcher - select mobile browser for single column page (i.e. github) WCAG 2.1 FPWD https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html "Essential" in SC Summary of Action Items Summary of Resolutions <scribe> Scribe: Erich sure thing!! :) CSUN <shawn> Shawn will be at CSUN CSUN first timer! <shawn> Erich, Glenda, Jim, Wayne all will be at CSUN LVTF panel discussion happening on Thursday of CSUN, can talk about our 7 SC's <shawn> which session is that? GS: will be Jim, Wayne and Glenda as moderator ... Topics could include proposed SC, Wayne horizontal scroll information ... Would love to have Shawn up front if interested, valuable perspective Panel is Thurs 1:20pm at CSUN - LVTF 1:20pm (Seaport F-Deque, 2nd FL) GS: Does anyone know if Alastair expects to be at CSUN? ... Concept of a CSS pixel would be interesting to discuss, but perhaps too much in a panel discussion? JA: Yeah, perhaps if it comes up ... CSS pixel can get in to the weeds pretty fast WD: It's important that the physical pixels measure what we can see, and we don't need to worry about those conversions ... Also, every person with low vision has tunnel vision, whether medically or by magnifying on the screen, which is where linearization becomes important. Already getting pushback on it. User Agent Switcher - select mobile browser for single column page (i.e. github) <allanj> FF /Chrome - http://mybrowseraddon.com/useragent-switcher.html <allanj> Chrome - http://useragentswitcher.org JA: This is important for when it comes to implementations, pasted two links ... Gave a linearized, reflowed view on single screen, less need to scroll around looking for things ... With agent switchers, you can specify things like 'give me the iphone 3 view' WD: When I read Gmail now, I can make it a cell phone, but delete it with a style sheet, like having a toggle ... Much easier reading my email now JA: Wayne mentioned something like text drifter WD: Drifting text is a nice feature, helps measure reading speed GS: So the text is moving? JA: Yes, it gives you a single line and the text moves across, and always moves at a constant rate Erich suggests checking out www.spotlighttext.com eBook reader, if interested WCAG 2.1 FPWD https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html <shawn> [ Shawn has EOWG Mon & Tue ] Erich arriving 11am Monday, departing 10pm Friday (CSUN first-timer!) JA: There was a scramble to get FPWD out before CSUN, should be coming by tomorrow ... LVTF got all of our 7 proposed SC in <allanj> If content can printed, the following are true: <allanj> Resized: <allanj> Content can be resized up to 200% without loss of content or functionality; <allanj> Changes Reflected: <allanj> User changes to letter spacing, line spacing, font family, and color are reflected in the printed content. <steverep> My apologies for being so late (significant computer issues) <allanj> above is 1.4.13 <allanj> SC 1.4.16 Popup Interference <allanj> For informational content that appears on hover or focus, one of the following is true: <allanj> Turn Off <allanj> The informational content can be turned off <allanj> Not obscure <allanj> The informational content does not obscure the triggering content <allanj> Note <allanj> This does not apply to user agent rendering of the title attribute. <allanj> https://alastairc.ac/2017/02/four-levels-of-accessibility-customisation/ JA: Whenever any of us is browsing day-to-day, it behooves us to capture screenshot pictures of particularly heinous low-vision infractions MR: I collect many examples every day, how do we share? JA: Just send it forward, and we can figure out where it fits MR: Does it need to be specific to 2.1? JA: Likely best at this point if it is <Zakim> shawn, you wanted to say consider "public" and anon and to say add to wiki? SH: I think it would be best to keep in mind whatever you share might be publicly consumed, so may be fine to anonymize or block out certain words. Can share to the wiki WD: There are enthusiastic clients who may be willing to share early mistakes, to demonstrate how they were fixed JA: Noticing Steve has joined, wondering if you will be at CSUN SR: Unfortunately not "Essential" in SC <Glenda> Normative definition of Essential from WCAG 2.0 = essential <Glenda> if removed, would fundamentally change the information or functionality of the content, and information and functionality cannot be achieved in another way that would conform SR: The term "essential" gets murky, have a number of examples - easier for me to describe verbally GS: Have been feeling comfortable with "Essential" and love the definition <Zakim> steverep, you wanted to say the second clause is what bothers me <allanj> lvtf sc with "essential: <allanj> 1.4.10 A mechanism is available to view content as a single column, except for parts of the content where the spatial layout is essential to the function and understanding of the content. <allanj> 1.4.12 Graphics Contrast The visual presentation of graphical objects that are essential for understanding the content or functionality have a contrast ratio of at least 4.5:1 against the adjacent color(s), except for the following: <allanj> 1.4.14 User Interface Component Contrast (Minimum)...The visual presentation of essential graphical objects for user interface component(s) <allanj> glenda: if you take the graphic or part of the graphic off of the page and it no longer makes sense then that part of the graphic is "essential" <Wayne> essential <Wayne> if removed, would fundamentally change the information or functionality of the content, and information and functionality cannot be achieved in another way that would conform <allanj> essential <allanj> Proposed <allanj> if removed, would fundamentally change the information or functionality of the content, and information and functionality cannot be achieved in another way that would conform <allanj> Examples of a particular presentation of content being essential to the information being conveyed: <allanj> banking site where a check deposit has to be in a certain orientation <allanj> piano app in landscape mode <allanj> Next Meeting March 9 JA: Next LVTF call will be March 9th, after CSUN <Wayne> mechanism- process or technique for achieving a result <Glenda> I will not be available at the March 9th time. Will be onsite at a client. <allanj> WCAG2.1 comments will go to public-comments-wcag20@w3.org <allanj> to receive all of the comments, subscribe to public-comments-wcag20-request@w3.org Summary of Action Items Summary of Resolutions [End of minutes] Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log) $Date: 2017/02/23 17:20:37 $ 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 Scribe: Erich Inferring ScribeNick: erich WARNING: Replacing previous Present list. (Old list: (no, one), allanj) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ allanj WARNING: Replacing previous Present list. (Old list: allanj, Shawn, Erich, Glenda, erich, Marla) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ allanj, Shawn, Erich, Glenda, Marla Present: allanj Shawn Erich Glenda Marla StephenR steverep Regrets: Laura Found Date: 23 Feb 2017 Guessing minutes URL: http://www.w3.org/2017/02/23-lvtf-minutes.html People with action items: WARNING: Possible internal error: join/leave lines remaining: <scribe> JA: Noticing Steve has joined, wondering if you will be at CSUN WARNING: Possible internal error: join/leave lines remaining: <scribe> JA: Noticing Steve has joined, wondering if you will be at CSUN WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. [End of scribe.perl diagnostic output] Erich Manser IBM Accessibility, IBM Research Littleton, MA / tel: 978-696-1810 Search for accessibility answers You don't need eyesight to have vision.
Attachments
- image/jpeg attachment: 5C568482.jpg
- image/jpeg attachment: 5C829326.jpg
- image/gif attachment: ecblank.gif
- image/gif attachment: 5C688619.gif
Received on Thursday, 23 February 2017 17:24:42 UTC