-
Notifications
You must be signed in to change notification settings - Fork 8
Research
I want my users to be able to zoom on their devices. Therefore, I do not define the minimum or maximum-scale meta. Yuck! WAI-ARIA (Web Accessibility Initiative - Accessible Rich Internet Applications)
These are some of the articles I referenced to help make the coding decisions for how to implement responsive web.
Techniques for Gracefully Degrading Media Queries
Why Google might just be right about responsive design in Africa
Best Practices for Speeding up the Web
The EMs have it: Proportional Media Queries
There are several approaches:
-
Have it all client side. This ia pretty heavy and requires bandwidth. Also, do we approach this with HTML media queries to load css, or do we use CSS media queries? What happens when a feature phone cannot understand a query?
-
Let the server decide. When a device makes a request, it sends a user-agent tag, the server can then serve the files accordingly.
-
I am loading all responsive additions via Modernzr.load (which is essentially yepnope.js). This allows the site to be more lightweight and only use things that it needs. Why load additional files you never use?
-
I am working under the assumption that all desktop browsers understand media queries.
-
I decided on jQuery 1.9.1 because 2.0 does NOT support IE 7 or 8 which is what many of our users are still using.
-
I want all additional files (.css and .js) to execute in parallel so the site isn't bogged down waiting for certain aspects to load.
-
I like the side menus so that's what were going to do. I'm using sidr. Nate wrote his own.