Security News
The Push to Ban Ransom Payments Is Gaining Momentum
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
@double-great/stylelint-a11y
Advanced tools
Readme
npm i --save-dev stylelint @double-great/stylelint-a11y
Create the .stylelintrc.json
config file (or open the existing one), add stylelint-a11y
to the plugins array and the rules you need to the rules list. All rules from stylelint-a11y need to be namespaced with a11y
.
Please refer to stylelint docs for the detailed info on using this linter.
Rule ID | Description | |
---|---|---|
content-property-no-static-value | Disallow unaccessible CSS generated content in pseudo-elements | |
font-size-is-readable | Disallow font sizes less than 15px | |
line-height-is-vertical-rhythmed | Disallow not vertical rhythmed line-height | |
media-prefers-reduced-motion | Require certain styles if the animation or transition in media features | Recommended, Fixable |
media-prefers-color-scheme | Require implementation of certain styles for selectors with colors. | |
no-display-none | Disallow content hiding with display: none property | |
no-obsolete-attribute | Disallow obsolete attribute using | |
no-obsolete-element | Disallow obsolete selectors using | |
no-spread-text | Require width of text in a comfortable range | |
no-outline-none | Disallow outline clearing | Recommended |
no-text-align-justify | Disallow content with text-align: justify | |
selector-pseudo-class-focus | Require or disallow a pseudo-element to the selectors with :hover | Recommended, Fixable |
Add recommended configuration by adding the following to extends
in your stylelint configuration:
@double-great/stylelint-a11y/recommended
This shareable config contains the following:
{
"plugins": ["@double-great/stylelint-a11y"],
"rules": {
"a11y/media-prefers-reduced-motion": true,
"a11y/no-outline-none": true,
"a11y/selector-pseudo-class-focus": true
}
}
Since it adds stylelint-a11y to plugins
, you don't have to do this yourself when extending this config.
There work on the plugin's rules is still in progress, so if you feel like it, you're welcome to help out in any of these (the plugin follows stylelint guidelines so most part of this is based on its docs):
We communicate via issues and pull requests.
There is also stackoverflow, which would be the preferred QA forum.
FAQs
Plugin for stylelint with a11y rules
We found that @double-great/stylelint-a11y demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
Application Security
New SEC disclosure rules aim to enforce timely cyber incident reporting, but fear of job loss and inadequate resources lead to significant underreporting.
Security News
The Python Software Foundation has secured a 5-year sponsorship from Fastly that supports PSF's activities and events, most notably the security and reliability of the Python Package Index (PyPI).