HTML5 introduces several new structural elements that will be very beneficial for accessibility:<\/p>\n
These can also be used to enhance keyboard navigation (a user could press the “N” key to jump to the page navigation, for example). Many HTML5 structural elements mirror or map to ARIA landmark roles:<\/p>\n If transitioning to HTML5, you will want to use both the HTML5 native element and the ARIA role (e.g., <nav><\/code> (for identifying navigational elements),<\/p>\n<header><\/code> (a group of introductory or navigational aids),<\/p>\n<article><\/code> <aside><\/code> (tangentially related content, such as a sidebar), and <\/code><\/p>\n<footer><\/code> provide meaning to major page structural areas.<\/p>\n<article><\/code> \u2014 role=\"article\"<\/code><\/p>\n<footer><\/code> \u2014 role=\"contentinfo\"<\/code> (only one per page)<\/p>\n<header><\/code> \u2014 role=\"banner\"<\/code><\/p>\n<nav><\/code> \u2014 role=\"navigation\"<\/code><\/p>\n<aside><\/code> \u2014 role=\"complementary\"<\/code><\/p>\n<nav role=\"navigation\"><\/code>) until assistive technology support for HTML5 improves. Of note is that ARIA provides very useful role=\"search\"<\/code> and role=\"main\"<\/code> that do not have HTML5 counterparts. The accessibility of nearly all web pages would be increased if these roles are implemented.<\/p>\n