- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 21 Nov 2013 12:53:42 -0600
- To: WAI-ua <w3c-wai-ua@w3.org>
from: http://www.w3.org/2013/11/21-ua-minutes.html DRAFT - User Agent Accessibility Guidelines Working Group Teleconference 21 Nov 2013 See also: IRC log http://www.w3.org/2013/11/21-ua-irc Attendees Presentkford, Jim_Allan, Kim_Patch, Jan, Jeanne, Greg_LowneyRegretsEricChairJimAllan, KellyFordScribeallanj Contents Topics TPAC Shenzhen recap implementations (developing rules) Summary of Action Items ________________________________ <trackbot> Date: 21 November 2013 minutes - Nov 11 http://www.w3.org/2013/11/11-ua-minutes.html minutes - Nov 12 http://www.w3.org/2013/11/12-ua-minutes.html http://lists.w3.org/Archives/Public/w3c-wai-ua/2013OctDec/0046.html http://lists.w3.org/Archives/Public/w3c-wai-ua/2013OctDec/0047.html International Day of Persons with Disabilities, 3 December 2013 http://www.un.org/disabilities/default.asp?id=1607 FCC Revises Complaint Procedures for Resolving Accessibility Issues http://www.wirelessrerc.gatech.edu/content/newsroom/fcc-revises-complaint-procedures-resolving-accessibility-issues?goback=%2Egde_1854667_member_5808944761934983169#%21 <scribe> scribe: allanj TPAC Shenzhen recap js: good stuff happened UAWG welcomes Takeshi Kurosawa for to the working group Mitsue-Links Co in Japan Use of Skype during TPAC useful? kp: was useful. implementations (developing rules) -- discussion of how to keep track of implementations -- html table was usable for ATAG <Greg> I see various spreadsheet to Wiki converters, such as http://excel2wiki.net/, but I haven't tried any. http://lists.w3.org/Archives/Public/w3c-wai-ua/2013OctDec/0046.html allanj http://lists.w3.org/Archives/Public/w3c-wai-ua/2013OctDec/0047.html we will work from spreadsheet and create html table snapshots <Greg> https://www.mediawiki.org/wiki/Extension:Data_Transfer might be worth looking into as well. Jim reviews messages js: should gather implementations, then sort them out ... see what we have, then define exit criteria kf: JS make sense. interesting cases - some SC could use the same rendering engine and create vastly different views of the same content. ... both ja and js are right. we will sort out rules later gl: implementations have implications for testing. for content testing - focus on rendering engines. js: that's right. for now we need to cast a wide net to get all implementations we can, then pick the best representations for an SC kf: order of action - how to collect info - what details js: most detail will come in the testing phase. ... need to just get browser name ja: want more detail - what i did in which menu or extension kp: some notes, or path to a file, for path to settings gl: need basic info OS, version of UA, kp: path - click this this this to make it happen ... notes are different (this is what I thought about it) kf: configuration field - UAs have different modes for rendering that might impact a11y. kp: +1 ... different versions without numbers for different users... js: version numbers are good. capture that make sense but not get everything needs: os + version UA + version if need add device type (iPad, iPhone, android x) mobile version vs desktop version may have different renderings who tested and date special settings Resolution: No meeting on 28 Nov because of USA Thanksgiving Jim will create spreadsheet and html and desiminate rrsagent make minutes Summary of Action Items [End of minutes] -- Jim Allan, Accessibility Coordinator & Webmaster 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 Thursday, 21 November 2013 18:54:11 UTC