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

@qualweb/best-practices

v0.6.19

Published

QualWeb best practices

Downloads

1,109

Readme

QualWeb best practices

Implementation of accessibility best practices for web pages.

How to use

This is an internal module of QualWeb. To use it check either @qualweb/cli or @qualweb/core.

Implemented best practices

| QualWeb best practice ID | Related to | Best practice Name | |---|---|---| | QW-BP1 | HTML | Using h1-h6 to identify headings | | QW-BP2 | HTML | Concise images alt text | | QW-BP3 | HTML | Link element with text content equal to the content of the title attribute | | QW-BP4 | HTML | Grouped links not within a nav element | | QW-BP5 | HTML | Using table elements inside other table elements | | QW-BP6 | HTML | title element is not too long (64 characters) | | QW-BP7 | HTML | Title element contains ASCII-art | | QW-BP8 | HTML | Headings with images should have an accessible name | | QW-BP9 | HTML | Table element without header cells has a caption | | QW-BP10 | HTML | HTML elements are used to control visual presentation of content | | QW-BP11 | HTML | Using br to make a list | | QW-BP12 | HTML | Using scope col and row | | QW-BP13 | HTML | Using consecutive links with the same href and one contains an image | | QW-BP14 | CSS | At least one container's width has been specified using values expressed in px | | QW-BP15 | CSS | At least one width attribute of an HTML element is expressed in absolute values | | QW-BP17 | HTML | Adding a link at the beginning of a block of repeated content to go to the end of the block | | QW-BP18 | CSS | Using percentage values in CSS for container sizes | | QW-BP19 | HTML | Landmark banner is top level | | QW-BP20 | HTML | Landmark no duplicate banner | | QW-BP21 | HTML | Landmark no duplicate contentinfo | | QW-BP22 | HTML | Landmark has one main | | QW-BP23 | HTML | Listitems are used semantically | | QW-BP24 | HTML | Lists are used correctly | | QW-BP25 | HTML | Landmark complementary is top level | | QW-BP26 | HTML | Landmark contentinfo is top level | | QW-BP27 | HTML | Landmark main is top level | | QW-BP28 | HTML | H1 element is used and unique | | QW-BP29 | HTML | HTML page lang and xml:lang attributes have matching values |

License

ISC