My website [www.jungledragon.com](http://www.jungledragon.com) makes heavy use of the icon font "FontAwesome". This week I upgraded my system to Windows 8.1, which comes with IE11 installed. I noticed that the FontAwesome font fails to load completely, and the browser console shows these errors:

```
CSS3117: @font-face failed cross-origin request. Resource access is restricted.
File: fontawesome-webfont.eot
CSS3117: @font-face failed cross-origin request. Resource access is restricted.
File: fontawesome-webfont.woff
CSS3114: @font-face failed OpenType embedding permission check. Permission must be Installable. File: fontawesome-webfont.ttf

```

I know what these errors mean, they are related to cross origin permissions, due to the actual font files being hosted on Amazon S3 in my case.

However, here is the weird thing: I do have a CORS policy applied to the bucket in question, and this has always worked. To do some more research, I tried putting IE11 into different document modes, being IE10, IE9, and IE8. The font fails to load in all cases. This is strange, since when I was on Windows 8, it would work on IE8, 9 and 10 just fine. 

It looks like those document modes are really useless though, since I then continued to do some real testing using browserstack, making use of real native browser versions instead of document modes. On both Windows 7 and 8, the font loads fine in IE8, 9, 10, and also in the IE11 preview.

I'm now a bit lost on where the problem is. Is the problem a result of Windows 8.1 specifically (it seems for me, but I can't test that in browserstack, it's not available)? Or is it perhaps a problem only in the final version of IE11? And if so, why is it a problem in every document mode?

Note: should you be wanting to help in testing, on the website it is very easy to see whether the font loads or not: the global navigation bar will have no icons, as well as several other areas of the site.