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

waccess

v1.0.2

Published

Improving web accessibility.

Downloads

1

Readme

WACCESS

A small script to improve web accessibilty for blind people. Initial idea is to place hidden HTML elements inside the HTML code, that just forward the focus to other elements once they are focused.

Sources here:

https://github.com/rogerjfx/waccess

Usage:

Waccess is designed to nearly everything handle within HTML. The main tag is

  <waccess></waccess>

Main child nodes are buttons. They should have two attributes, "from" and "to". The values should point to other containers using document.querySelectorAll().

  <waccess>
    <button from="#myContainer" to="#myOtherContainer">Foo</button>
  </waccess>

So once the nested button is focused, it either forwards to node with id "myContainer" or "myOtherContainer", if the SHIFT key is down.

If there are more than one button inside the Waccess container, the user might select one of those options by pressing ENTER. If all buttons have the same target for one direction, auto forwarding again will be performed in this direction.

Initially Waccess should be activated. This is done by asking the user first.

  <waccess>
  	<a class="welcome" href="javascript:$waccess.activateWaccess();">Activate?</a>
    <a class="activated" href="javascript:;">Ok, activated.</a>
  </waccess>

Once Waccess is activated, it will be stored to session storage and the user won't be asked again within this session.

Note: the module really searches for the anchors with the mentioned classes.

API

Waccess is all over static. Just import it, and it is alive. You should think of it as of a very eager singleton, if you are in doubt. Me too, I am in doubt as well. :D

However you might fetch and hold a (yet useless) reference.

E.g. (TypeScript)

  private waccess: IWaccess = Waccess.init();

All the following methods are "static". So you may call e.g. Wacess.scanAgain() directly.

  • init(): IWaccess
    Normally completely useless. Returns a reference to the singleton Waccess instance. Should become deprecated soon. Very soon...
  • activateWaccess(): Void
    Activates Waccess for the UI.
  • scanAgain(): Void
    If you have dynamical content, you should force Waccess to scan again.
  • focusElement(query: string, force?: boolean): Void
    Declaratively focus an HTML element. Usefull, for events like "load" or any related promises
    => query: the query for querySelectorAll()
    => force: if true, action will be performed even with inactive Waccess.

Notes

  1. If dealing with Angular 2++, don't forget to put NO_ERRORS_SCHEMA to schemas in app.module.ts. Otherwise Angular will complain unknown tags.