From c72d3c6e3f9d096ec3ab5457be2a9d2c6fb65bd5 Mon Sep 17 00:00:00 2001 From: Jen Weber Date: Sun, 10 Dec 2017 15:13:20 -0500 Subject: [PATCH] more detailed README, including div use #14 --- README.md | 68 +++++++++++++++++++++++++++++++++++++------------------ 1 file changed, 46 insertions(+), 22 deletions(-) diff --git a/README.md b/README.md index 3cd86f0..73268b1 100644 --- a/README.md +++ b/README.md @@ -2,20 +2,23 @@ [![Latest NPM release](https://img.shields.io/npm/v/ember-a11y-landmarks.svg)](https://www.npmjs.com/package/ember-a11y-landmarks) [![TravisCI Build Status](https://img.shields.io/travis/ember-a11y/ember-a11y-landmarks/master.svg?label=TravisCI)](https://travis-ci.org/ember-a11y/ember-a11y-landmarks) -## Context -Assistive technology(AT) requires the correct HTML semantic elements and/or roles to be used, in order to parse the page correctly. If the "landmark" elements are the direct descendant of the `body` element, then the role declaration is not needed. However, since Ember wraps each app in a div, and that div is the direct descendant of the `body` element, role declaration on these elements are required. +The `ember-a11y-landmarks` addon helps you assign the `role` attribute that should go on landmark tags like `
` and `