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

uaag-as-json

v0.1.4

Published

The Usage Agent Accessibility Guidelines (UAAG) in JSON format.

Downloads

2

Readme

UAAG as JSON

This is meant to be like WCAG as JSON and ATAG as JSON but for UAAG.

Relevant Links

Structure

The structure of the JSON file closely mirrors the UAAG Standard itself:

  • There are 5 Principles of UAAG (Perceivable, Operable, Understandable, Programmatic access, and Specifications and conventions)
  • Each Principle has Guidelines
  • Each Guideline has Success Criteria

In this JSON format the Success Criteria have been broken down further:

  • Special Cases - additional considerations on the applicability of the SC. There are 3 types of special cases
    • exception - the special case, if satisfied, creates an exception whereby the SC does not apply
    • at_least_one - at least one of the special cases must apply
    • all_true - all of the special cases must apply
  • Notes - any other notes that accompany the Success Criterion
  • The Level of a Success Criterion is either A, AA, AA, or A,AA,AAA meaning the SC corresponds to the desired level of WCAG conformance.

A full UAAG SC Entry looks like this:

{
	"ref_id" : "sc_114",
	"title" : "Facilitate Clear Display of Alternative Content for Time-based Media",
	"description" : "For recognized on-screen alternative content for time-based media (e.g. captions, sign language video), the following are all true",
	"level" : "A",
	"url_fragment" : "sc_114",
	"notes" : [
		{ "content" : "Depending on the screen area available, the display of the primary time-based media can need to be reduced in size to meet this requirement. " }
	],
	"special_cases" : [
		{
			"type": "all_true",
			"title": "Don't obscure controls",
			"description": "Displaying time-based media alternatives doesn't obscure recognized controls for the primary time-based media."
		},
		{
			"type": "all_true",
			"title": "Don't obscure primary media",
			"description": "The user can specify that displaying time-based media alternatives doesn't obscure the primary time-based media. "
		}
	]
},

License

The JSON formatted document has an MIT license.

This software or document includes material copied from or derived from User Agent Accessibility Guidelines (UAAG) 2.0 https://www.w3.org/TR/UAAG20/. Copyright © 2015 W3C® (MIT, ERCIM, Keio, Beihang).