Difference between revisions of "User talk:Cynthia"
m |
m |
||
| Line 1: | Line 1: | ||
==Proposed Schedule== | ==Proposed Schedule== | ||
* Call for Proposals: Mon Oct 1 | * Call for Proposals: Mon Oct 1 | ||
| − | * Close Proposals: Fri Nov 2 | + | * Close Proposals: Fri Nov 2 - extend to Nov 9 |
| − | * Voting Open: | + | * Voting Open: Nov 14? |
| − | * Voting Close: | + | * Voting Close: Nov 23? |
==Preconference Proposal Page Preamble== | ==Preconference Proposal Page Preamble== | ||
Revision as of 22:22, 31 October 2012
Contents
Proposed Schedule
- Call for Proposals: Mon Oct 1
- Close Proposals: Fri Nov 2 - extend to Nov 9
- Voting Open: Nov 14?
- Voting Close: Nov 23?
Preconference Proposal Page Preamble
Proposals close Friday, November 2 at 5pm PT.
Spaces available: 4+ Rooms
Please include a lead "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.
=== Talk Title === * Presenter/Leader, affiliation, and email address * Second Presenter/Leader, affiliation, email address, if applicable Description.
Proposal Page Preamble
Deadline for talk submission is Friday, November 2 at 5pm PT.
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:
- tools (some cool new software, software library or integration platform)
- specs (how to get the most out of some protocols, or proposals for new ones)
- challenges (one or more big problems we should collectively address)
The community will vote on proposals using the criteria of:
- usefulness
- newness
- geekiness
- uniqueness
- awesomeness
Please follow the formatting guidelines:
== Talk Title == * Speaker's name, affiliation, and email address * Second speaker's name, affiliation, email address, if applicable Abstract of no more than 500 words.
Proposal Call Out
Post to
- code4lib website
- code4lib mailing list - Cyn
- web4lib list - Cyn
- LITA-L - Peter
- AUTOCAT - Peter
- NGC4lib
- Voyager-L
- vufind-general
- ELUNA-announce-L
- xml4lib
- WC-devnet-L
- lotico-list
--
Subject: Code4lib 2013 Call for Proposals
We are now accepting proposals for Code4lib 2013.
Code4lib 2013 is a loosely-structured conference for library technologists to commune, gather/create/share ideas and software, be inspired, and forge collaborations. The conference will be held Monday February 11th (Preconference Day) - Thursday February 14th, 2013 in Chicago, IL. More information can be found at http://tigger.uic.edu/~kayiwa/code4lib.html
Prepared Talks
Head over to the call for proposals page at http://wiki.code4lib.org/index.php/2013_talks_proposals and submit your idea for a prepared talk for this year's conference! Proposals should be no longer than 500 words, and preferably many less.
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:
- tools (some cool new software, software library or integration platform)
- specs (how to get the most out of some protocols, or proposals for new ones)
- challenges (one or more big problems we should collectively address)
The community will vote on proposals using the criteria of:
- usefulness
- newness
- geekiness
- uniqueness
- awesomeness
Proposals can be submitted through Friday, November 2nd, 5pm PT. Voting will commence soon thereafter. The submitter (and if necessary a second presenter) will be guaranteed an opportunity to register for the conference.
Proposals for preconferences are also open until November 2nd, 5pm PT. http://wiki.code4lib.org/index.php/2013_preconference_proposals
We cannot accept every prepared talk proposal, but multiple lightning talk and breakout sessions will provide everyone who wishes to present with an opportunity to do so.
Drafts of other stuff
Making the Web Accessible through Solid Design
- Cynthia Ng from Ryerson University Library & Archives
In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.
While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.
