Skip to content

Commit

Permalink
Further removing of ’ based on #128
Browse files Browse the repository at this point in the history
Ok, this is the last one i promise. :)
  • Loading branch information
Milos Gavrilovic committed Feb 8, 2012
1 parent 9567622 commit 18c69d1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion posts/html5-sectioningelements.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 arent 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:

Expand Down

0 comments on commit 18c69d1

Please sign in to comment.