Permalink
Browse files

Further removing of ’ based on #128

Ok, this is the last one i promise. :)
  • Loading branch information...
1 parent 9567622 commit 18c69d127e8c05cb5c6904cd8b908d92d6012bbf Milos Gavrilovic committed Feb 8, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 posts/html5-sectioningelements.md
View
2 posts/html5-sectioningelements.md
@@ -4,7 +4,7 @@ tags: gtie8 polyfill
kind: html
polyfillurls: [html5shiv](http://code.google.com/p/html5shiv/), [html5shiv (github)](https://github.com/aFarkas/html5shiv/), [accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js)
-All current browsers, except Internet Explorer 8 and below, support the use of the new HTML5 elements (e.g., `<header>`, `<footer>`, `<nav>`, `<article>`, `<section>`, etc.). However, they aren’t always mapped to accessibility APIs as the [HTML5 spec](http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria) requires. Currently [only Firefox does this](http://html5accessibility.com/), but other browsers are implementing the accessibility APIs quickly. In the meantime, [Accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js) maps them correctly.
+All current browsers, except Internet Explorer 8 and below, support the use of the new HTML5 elements (e.g., `<header>`, `<footer>`, `<nav>`, `<article>`, `<section>`, etc.). However, they aren't always mapped to accessibility APIs as the [HTML5 spec](http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria) requires. Currently [only Firefox does this](http://html5accessibility.com/), but other browsers are implementing the accessibility APIs quickly. In the meantime, [Accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js) maps them correctly.
The notes below only apply to Internet Explorer 8 and below:

0 comments on commit 18c69d1

Please sign in to comment.