Criteria for proposing sessions: You must be a practising web designer/developer, and must be able to show how your own work has advanced the state of the web in the past year. You are expected to present original work that your peers — this event’s audience — recognise as being notable enough to deserve a stage.
About Meta Refresh: Meta Refresh is a conference where Design and UI development converge. A beautiful experience on the web is a result of a deep understanding of your user and the nuances of the medium. Meta Refresh aims to be the platform where designers and UI developers exchange ideas and skills and learn from each other.
Format: This year’s edition spans four days, with two days of workshops and two days of conference. All days feature a single track.
We are accepting talks on:
- Front-end implementations, mainly workflow, processes, tools and automation,
- CSS, animation, UX, trends, and typography, and
- Short, crisp talks on front-end tricks.
Talks on implementation have to be about original work. While covering scalability and productivity aspects to explain implementation details, proposers must also explain who is the user and what is the context in which their product is being used. Therefore, how content and design were tailored in each specific instance.
We also invite workshop proposals on:
- Build systems such as Grunt
- CSS frameworks such as Bootstrap 3 and Foundation
- MVC/JS frameworks such as Angular
Workshops will be held on 12th and 13th February at the TERI auditorium in Domlur, Bangalore.
If you are excited about someone’s work and believe it deserves wider recognition, we recommend you contact them and ask them to submit a proposal.
Last date for submissions: 12 January 2014.
Confirmations: 15 January 2014 onwards.
There is only one speaker per session. Attendance is free for selected speakers. HasGeek will offer a grant to cover your travel to and accommodation in Bangalore from anywhere in the world for speakers delivering full sessions (30 minutes or longer). As our budget is limited, we will prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. If you are able to raise support for your trip, we will count that as a speaker travel sponsorship.
Travel grants are reimbursed at the end of the conference. You are expected to make your own travel and stay arrangements. We will assist with hotel recommendations, visa letters and general advice on travel.
Commitment to open source #
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like it to be available under a permissive open source license. If your software is commercially licensed or available under a combination of commercial and restrictive open source licenses (such as the various forms of the GPL), please consider picking up a sponsorship. We recognize that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.
Non Accepted Proposals #
If your proposal is accepted for a session > 30 minutes long, we will cover your event ticket. If your proposal is not accepted, you can buy a ticket at the same rate as was available on the day you proposed. We’ll send you a code.
For queries about proposals / submissions, write to email@example.com
Form accessibility demystified
Web is open platform, thus any application developed for this open platform should be accessible for any users, irrespective of their disabilities. Accessibility must be treated as the core feature of the user experience. Quite often, a web application that is keyboard accessible is considered to be accessible compliant. How ever which is partially true. For example, ‘hasgeek login’ form. There are visual indication of the error in the page, however for visually challenged user there is no indication for error and teh experience is more like an infinite loop. Using aria-invalid and aria-described by solves the problem.
Developers mainly focus on the ‘look and feel’ along with performance. Is the awesome looking UI accessible via keyboard completely, accessible for a visually challenged user?
If not, how to achieve it? How to make visually challenged users aware of all the dynamic changes/updates the UI is going through?
Many a times we use custom elements instead of native. For example, using a custom drop down menu instead of native select/options. It is quite easy to visually implement a custom drop down menus using div(s), ul(s) and li(s). But, is it completely accessible, via keyboard, by a user who is visually challenged?
This presentation will mainly focus on ‘HOW’ rather than ‘WHAT’ with respect to web accessibility and real life use cases of accessibility.
Speaker bio #