Results for accessibility-setup

Project to promote digital accessibility and facilitate its implementation

Implements https://w3c.github.io/accname/

Accessibility engine for automated Web UI testing

Storybook Addon A11y: Test UI component compliance with WCAG web accessibility standards

A generic toolkit to help with accessibility

Accessibility (a11y) utilities for WordPress.

ESLint plugin for Angular Templates

An eslint plugin for checking Vue.js files for accessibility

Static AST checker for accessibility rules on JSX elements.

Accessibility Checker for Cypress

Accessibility testing matcher for Jest

React Native specific accessibility linting rules.

JavaScript charting framework

Accessibility Plugin for visually impaired users

Test runner for Storybook stories

Watcher automatically:

[](https://github.com/marksandspencer/nx-plugins/blob/main/LICENSE.md)  [![npm v

Manipulate colors like a boss

A Cypress plugin for configurable accessibility analysis supporting WCAG 2.2 (A-AAA). It provides a detailed list of violations in the Cypress log, visual feedback directly in the Cypress runner as well as voice feedback, and generates a comprehensive, se

This package contains compatibility with Dragon NaturallySpeaking accessibility tools.

ESLint configuration used by Create React App

Let agents run disposable VMs

A set of opinionated helpers built on top of the Constraint Validation API

Conform helpers for integrating with Zod

ConTeXt setup library is a helper library to use the cont-??.xml files for ConTeXt.

Provides setup information, including environment variables and certificates, required to access services provided by ADB/CDK.

A Wholesale framework for web, mobile, api, load, accessibility testing. Get you going in a minute. An instant setup of Ruby, Cucumber, Capybara, selenium, REST API Appium, Docker, Gatling and Axe Engine

Easy to use API consumer - Setup your API connection in a yaml file, and use the helper methods to make easy access APIs calls

Easy to use API consumer - Setup your API connection in a yaml file, and use the helper methods to make easy access APIs calls

A console utility to get information from your ThoughtWorks' Go Continuous Integration Server. Run '$ ci-go-nfo setup' to configure your access from console utility.

RabbitMQ's access control capabilities are rather limited. RabbitCage enables fine-grained permission setups, you define which user can perform which AMQP method on which class.

Bobby is all about guarding the access to actions on controllers and model instances on your Rails projects, and requires you to setup some authentication regime in advance - like Devise, Authlogic et al - with a User model, and preferably a GroupUser and GroupUsersUsers models too.

Authentication / Authorization library for Watermark apps

log_sense is a log analysis tool which analyzes Ruby on Rails and Apache/Nginx logs and provides detailed data about accesses, performances, and errors. It is a one-stop shop solution for analyzing your Rails application in production. Simple to use and working from the command line, it does not require any modification to your app (e.g., no need to change the log format, no cookies, no JavaScript code, no infrastructure to setup). We use it to monitor our applications in production, using a cron job which pulls the logs and calls log_sense to generate HTML reports. Compatible with Ruby on Rails default logs up to version 8.0.2 and with the combined Apache/Nginx format.

All the Pokémon data you'll ever need in one place, easily accessible through a modern free open-source RESTful API. ## What is this? This is a full RESTful API linked to an extensive database detailing everything about the Pokémon main game series. We've covered everything from Pokémon to Berry Flavors. ## Where do I start? We have awesome [documentation](https://pokeapi.co/docs/v2) on how to use this API. It takes minutes to get started. This API will always be publicly available and will never require any extensive setup process to consume. Created by [**Paul Hallett**(]https://github.com/phalt) and other [**PokéAPI contributors***](https://github.com/PokeAPI/pokeapi#contributing) around the world. Pokémon and Pokémon character names are trademarks of Nintendo.

ALPHA Alert -- just uploaded initial release. Linux inotify is a means to receive events describing file system activity (create, modify, delete, close, etc). Sinotify was derived from aredridel's package (http://raa.ruby-lang.org/project/ruby-inotify/), with the addition of Paul Boon's tweak for making the event_check thread more polite (see http://www.mindbucket.com/2009/02/24/ruby-daemons-verifying-good-behavior/) In sinotify, the classes Sinotify::PrimNotifier and Sinotify::PrimEvent provide a low level wrapper to inotify, with the ability to establish 'watches' and then listen for inotify events using one of inotify's synchronous event loops, and providing access to the events' masks (see 'man inotify' for details). Sinotify::PrimEvent class adds a little semantic sugar to the event in to the form of 'etypes', which are just ruby symbols that describe the event mask. If the event has a raw mask of (DELETE_SELF & IS_DIR), then the etypes array would be [:delete_self, :is_dir]. In addition to the 'straight' wrapper in inotify, sinotify provides an asynchronous implementation of the 'observer pattern' for notification. In other words, Sinotify::Notifier listens in the background for inotify events, adapting them into instances of Sinotify::Event as they come in and immediately placing them in a concurrent queue, from which they are 'announced' to 'subscribers' of the event. [Sinotify uses the 'cosell' implementation of the Announcements event notification framework, hence the terminology 'subscribe' and 'announce' rather then 'listen' and 'trigger' used in the standard event observer pattern. See the 'cosell' package on github for details.] A variety of 'knobs' are provided for controlling the behavior of the notifier: whether a watch should apply to a single directory or should recurse into subdirectores, how fast it should broadcast queued events, etc (see Sinotify::Notifier, and the example in the synopsis section below). An event 'spy' can also be setup to log all Sinotify::PrimEvents and Sinotify::Events. Sinotify::Event simplifies inotify's muddled event model, sending events only for those files/directories that have changed. That's not to say you can't setup a notifier that recurses into subdirectories, just that any individual event will apply to a single file, and not to its children. Also, event types are identified using words (in the form of ruby :symbols) instead of inotify's event masks. See Sinotify::Event for more explanation. The README for inotify: http://www.kernel.org/pub/linux/kernel/people/rml/inotify/README Selected quotes from the README for inotify: * "Rumor is that the 'd' in 'dnotify' does not stand for 'directory' but for 'suck.'" * "The 'i' in inotify does not stand for 'suck' but for 'inode' -- the logical choice since inotify is inode-based." (The 's' in 'sinotify' does in fact stand for 'suck.')