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

estimtest-core

v1.1.1

Published

Manually experiment most websites under a variety of conditions. Easily correct accessibility issues by simulating common disorders.

Downloads

372

Readme

Estimtest, experiment your website accessibility


Estimtest Core

Estimtest is an experimentation tool that simulates accessibility concerns. Accessibility is crucial, but unexpectedly, difficult to test.

Usage

Feel free to checkout the examples, or open an issue for support.

  • Apply the component as a sibling or child of a container. For example, as a child of <body></body>.
  • The estimtest-core element should cover up the entire screen in absolute position.

Load the component by importing it

<script type="module">
  import { defineCustomElements } from 'https://cdn.jsdelivr.net/npm/estimtest-core/loader/index.es2017.js';
  defineCustomElements();
</script>

Add the component

<estimtest-core
  active='true'
  move-selector='body'
  experiments='[{"name": "Hello World", "description": "hello", "fontSize": 32}]'
></estimtest-core>

Configuration

Use HTML attributes to modify props.

active boolean - Whether to activate the Estimtest prompt. Having this as false still imports the library but does not use it. Look at the examples for sloppy implementations of fully removing Estimtest in production.

experiments { name: string, description: string, fontSize?: number, colorBlind?: ColorBlind, keyboardOnly?: boolean }[] - The experiments to be performed on the app. This is set by default to perform multiple standard tests of common accessibility problems. This field accepts an array of objects each with the properties:

  • name A quick ~15 letters title summarizing the test.
  • description A description explaining the test and why it's important. Supports Markdown (Commonmark-compliant).
  • fontSize The font size to set the page. Many users have difficulty reading text at the default font size, users fix this by increasing the default font size.
  • colorBlind A change of colors on the page reflecting what colorblind users may see.
  • keyboardOnly Many users may use keyboard navigation for a variety of reasons such as: Motor impairment, saving time, and more.

moveSelector string - An element selector containing the parent of where the element should be at. You could use this property in the event that your code does not permit you to place the element there.