pa11y
stylelint
pa11y | stylelint | |
---|---|---|
21 | 44 | |
3,958 | 10,822 | |
0.7% | 0.3% | |
5.8 | 9.6 | |
15 days ago | 6 days ago | |
JavaScript | JavaScript | |
GNU Lesser General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pa11y
-
🤯 150 Articles to Satisfy Your Curiosity
Pa11y is your automated accessibility testing pal (https://pa11y.org/) by Rowan Manning
-
Scrollbars Are Becoming a Problem
And educate himself just a tiny little bit? ;)
Then in his next web project, he just might use https://github.com/pa11y/pa11y and make the world a better place!
-
Building Accessible Web Experiences: A Checklist for Frontend Developers
Pages should have descriptive titles. Make use of tag. Not just for accessibility reasons, its one of the key tools to improve your SEO.
- iFrames should have descriptive titles. iFrame is basically a page within a page, same rule applies for it too.
tag should have
lang
attribute. It helps screen readers to use correct pronunciation. If parts of your website use different languages, addlang
attribute to respective elements as well.- Roles: ARIA roles define the type of element and its purpose. Roles can be used to indicate whether an element is a button, link, menu, dialog, or other interactive components. For example,
role="button"
can be added to aelement to convey that it functions as a button.
- Labels. Interactive elements should have accessible name inside
aria-label
- Element semantics should not be inappropriately suppressed with aria-hidden. Avoid hiding elements from accessibility tree; If required, use CSS styles to make element invisible by changing opacity or visibility.
- Images should have alt attribute. Have you ever been stuck with slow connection and faced a white square wonder what's that supposed to be? Add an
alt
attribute so the images could be easily identified by text readers.Useful tools
Going through all those checkpoints might be overwhelming, and indeed, the larger your webpage or application is, the more effort it will take to find and address them.
There are, luckily excellent tools that can jumpstart the process.
- WAVE: A free online tool that provides visual feedback about the accessibility of your web content, highlighting potential issues and offering suggestions for improvement.
- axe DevTools: An accessibility testing extension for Google Chrome and Firefox that can be used directly within the browser's developer tools.
- Pa11y: An open-source automated accessibility testing tool that you can run from the command line or integrate into your CI/CD pipeline.
- Lighthouse Accessibility Audit: Excellent for a quick accessibility insight, Lighthouse is available with Google Chrome dev tools and checks highlight opportunities to improve the accessibility of your web app.
Remember that automated tools are valuable for identifying many common accessibility issues, but manual testing is often necessary to fully understand and address the user experience for people with disabilities. A combination of automated and manual testing, along with a commitment to ongoing accessibility, is key to maintaining an accessible web presence.
Happy coding!
Original post
-
Creating an Accessible Web for Everyone with Anuradha on Girl Code Coffee Chat #9
Pa11y
- Como adicionar recursos de acessibilidade em um site?
- Code optimisation for accessibility
-
Automated Accessibility Part 3: Regression Tests
Automated libraries such as axe-core and pA11y have been a very seamless way to bring accessibility testing into development teams UI testing. It can get development teams to begin to learn and grow accessibility in their teams. However, one big problem has appeared since the rise in popularity of these libraries.
- Como vocês geram métricas de acessibilidade?
-
A Practical Approach to Automated Accessibility
PA11y - It runs accessibility tests on your pages via the command line or Node.js, so you can automate your testing process
-
About a11y in general
https://github.com/pa11y/pa11y - Tool for testing ally using node.js (it also has integration with Cypress).
stylelint
-
Why it is Important to Update Linters and How to Do it Right
Another common way to extend configs in linters is using the extends key in the configuration file. Let's take StyleLint as an example:
-
How to Improve Development Experience of your React Project
Stylelint is similar to ESLint, but its focus is on styling rather than JavaScript. It helps you find errors in style files, such as old syntax or empty classes. We will also incorporate stylelint-config-clean-order to sort your style rules and group them consistently across the entire codebase.
-
Speeding up the JavaScript ecosystem – The barrel file debacle
The “cost of loading modules” diagram shows non-linear behaviour (though you should largely ignore the curve visible in the diagram because the x axis is way off linear):
• 0.15s ÷ 500 = 0.3ms
• 0.31s ÷ 1000 = 0.31ms
• 3.12s ÷ 10000 = 0.312ms
• 16.81s ÷ 25000 = 0.6724ms
• 48.44s ÷ 50000 = 0.9688ms
My own observation on a Surface Book six years ago was that in Node.js under Windows, each module had about 1ms of overhead when there was warm file system cache—that is, simply bundling with Rollup saved 1ms per file. If this sort of thing interests you, quite a lot of useful stuff came out of https://github.com/stylelint/stylelint/issues/2454 which I filed because I was unhappy with stylelint taking over a second to import. And that must have been only in the order of one or two thousand modules, when the behaviour is still close enough to linear.
-
Don't sound like a robot: use CSS to Control Text-to-Speech
As the property is still experimental, stylelint does not recognize it yet at the time of writing this, so let's explicitly disable the property-no-unknown rule only where we use it by adding a stylelint-disable comment and re-enable it afterwards.
-
How to upskill my skills?
Document your build process in a blog, use eslint, stylelint and jsx-a11y lint. Run a lighthouse performance test, follow the optimisation reccomendations.
-
How to Effortlessly Improve a Legacy Codebase Using Robots
Run static analysis e.g. lint with lockfile-lint, Stylelint, ESLint, check for unimported files using unimported, and identify potential security vulnerabilities
-
10 CSS Tools AI Can Integrate With for Improved Website Design
Stylelint
-
How can I have CSS automatically formatted so that all of the properties are in order by length, as I type?
I use StyleLint (https://stylelint.io/) to lint my css/scss. I don't think that's a rule, but writing a custom rule isn't too tough. And you can use the vscode extension - https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint
-
Deno Fresh PostCSS: Future CSS with Deno
The complete code for this project is in the Rodney Lab GitHub repo. I do hope the post has either helped you with an existing project or provided some inspiration for a new one. As an extension, you can add all your favourite future CSS rules to the PostCSS config. Beyond PostCSS for linting your input CSS, consider trying stylelint.
- This missing comma ruined my day. Can I get VSCode to fix this mistake automatically?
What are some alternatives?
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
Next.js - The React Framework
axe-core - Accessibility engine for automated Web UI testing
lint-staged - 🚫💩 — Run linters on git staged files
cypress-audit - ⚡ Run Lighthouse and Pa11y audits directly in your E2E test suites
commitlint - 📓 Lint commit messages
pa11y-ci - Pa11y CI is a CI-centric accessibility test runner, built using Pa11y
Symfony Encore - A simple but powerful API for processing & compiling assets built around Webpack
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
Nuxt.js - Nuxt is an intuitive and extendable way to create type-safe, performant and production-grade full-stack web apps and websites with Vue 3. [Moved to: https://github.com/nuxt/nuxt]
cypress-fail-fast - A Cypress plugin to skip tests on first failure.
husky - Git hooks made easy 🐶 woof!