npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ember-a11y-landmarks

v2.0.0

Published

An ember addon for easier creation of correct landmark regions for better accessibility.

Downloads

30

Readme

ember-a11y-landmarks

Latest NPM release TravisCI Build Status

The ember-a11y-landmarks addon helps you assign the role attribute that should go on landmark tags like <header> and <nav>, without needing to learn the intricacies of when to add roles or what they should be. A landmark is a special kind of semantic HTML tag that Assistive technology(AT) uses to parse a page correctly.

When is this addon needed? In a typical Ember app, almost everything gets wrapped in a <div>, but this can be confusing to tools like screen readers. The Assistive Technology expects that either landmark elements are direct descendants of the <body> element or that they have a particular role attribute. ember-a11y-landmarks handles this problem for you.

How this addon works

This addon helps add the correct roles to the following elements:

| tagName | role | | ------- | ------------- | | header | banner | | nav | navigation | | aside | complementary | | main | main | | form | form | | footer | contentinfo |

While semantic landmark tags are best for accessibility, some developers may be faced with working on an app that uses div tags instead. For those cases, this addon provides a way to add roles to a div element until they can be refactored (see Div Usage).

ember install ember-a11y-landmarks

Landmark Tag Usage

This addon is used like a block component. Just set the tagName attribute to header, nav, aside, main, form, or footer, and put your content inside the block. For example, here's a header:

<A11yLandmark @tagName="header">
    This is my header content
</A11yLandmark>

The resulting markup in the DOM will have the correct tag type and the role that should be used for that tag:

<header id="ember337" role="banner" class="ember-view">
    This is my header content
</header>

Div Usage

If a developer must use a div instead of a semantic tag like <header>, define landmarkRole instead of tagname. You can look up the correct landmark role in the How this addon works table. Here's a header example:

  <A11yLandmark @landmarkRole="banner">
      This is my header content (that should be refactored later to go inside a real header tag)
  </A11yLandmark>

In the DOM markup, this will result in a div with the specified role:

<div id="ember337" role="banner" class="ember-view">
     This is my header content (that should be refactored later to go inside a real header tag)
</div>

Form/Search Usage

If defining a form, no additional landmarkRole is required. However, if the form will be used as a search, then the landmarkRole value should be set to search.

Form:

<A11yLandmark @tagName="form">
    ...
</A11yLandmark>

Search:

<A11yLandmark @tagName="form" @landmarkRole="search">
    ...
</A11yLandmark>

Contributions

Contributions to this project are encouraged.

Compatibility

  • Ember.js v3.12 or above
  • Ember CLI v2.13 or above
  • Node.js v10 or above