1. Custom Font Usage/Fallback
   When the user is behind a protected network that doesn't allow use of our specified fonts, we'd request that the Arial family be used in it's place, while keeping the weight, italics, etc.
   For example, if Roboto Bold it used, the client would see Arial Bold.
   
   
2. Prohibited Usage of Icon Fonts/SVG/Icomoon
   Since the client's internal network does not allow font downloads, it creates issues when your teams create icomoon type font sets out of icons. Client has been consistently reporting that they cannot see a lot of icons that were in the signed off comps. We'd request the use of traditional methods (PNG sprite sheets, etc).
   
   
3. IE 8 Compatibility
   Project must support IE8 for Desktop,knowing that rounded corners, shadows and gradients will degrade gracefully in IE8. We understand that anti-alias text effects (smooth, sharp, crisp) used in design can’t be preserved in markup because HTML/CSS doesn’t render it. Items that are drawn via CSS, especially circular items degrade into squares at that point (pagination dots, etc). At this point, please make the item a png asset.
   
   
4. Footer Carousel animations
   (Desktop) Footer Carousel transitions between images should animate left/right and load the next group of images.
   (Mobile) All images in a Footer Carousel should crossfade to the next group of images.