pa11y
Monitorian
pa11y | Monitorian | |
---|---|---|
21 | 38 | |
3,958 | 2,971 | |
0.7% | - | |
5.8 | 8.9 | |
14 days ago | 3 months ago | |
JavaScript | C# | |
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).
Monitorian
- Monitorian: Windows desktop tool to adjust monitor brightness
-
18-year-old built a better computer monitor that doesn't strain your eyes
Most modern displays support DDC/CI or whatever it is that lets your PC talk to the monitor and adjust brightness (and other settings).
Monitorian and other apps let you adjust those settings from your PC.
https://github.com/emoacht/Monitorian
- Scrollbars Are Becoming a Problem
- Recomandare de ochelari pentru prevenirea oboselii
- Untuk parent apakah kalian membatasi anak kalian akses aplikasi atau situs tertentu?
-
What kind of applications are missing from the Linux ecosystem?
I feel like this is much simpler than many things called out so far, but I haven't found a great replacement coming from Windows for Monitorian. It's a small app that sits in your tray and lets you adjust your monitors' brightness levels. That way you don't have to press physical buttons on your monitors. It's also very nice to be able to lock multiple monitors' brightness levels together so you can change them at the same time.
-
not adjustable brightness (srry if its my 2nd post on this sub in 2 day)
I don't have a solution but Monitorian might tide you over. Works on external displays too
-
Brightness got stuck to low setting.
Monitorian is a nice alternative to the native brightness slider because it also works with external displays.
-
any way to remap the brightness fn keys to use custom increment steps instead of +10% or -10% steps?
Releases · emoacht/Monitorian (github.com)
-
KDE Plasma Widget for external monitor brightness adjustment
> there's TwinkleTray for Windows
There is also Monitorian for Windows:
https://github.com/emoacht/Monitorian
What are some alternatives?
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
Lunar - Intelligent adaptive brightness for your external monitors
axe-core - Accessibility engine for automated Web UI testing
DisplayMagician - DisplayMagician is an open source tool for automatically configuring your displays and sound for a game or application from a single Windows Shortcut.
cypress-audit - âš¡ Run Lighthouse and Pa11y audits directly in your E2E test suites
NvAPIWrapper - NvAPIWrapper is a .Net wrapper for NVIDIA public API, capable of managing all aspects of a display setup using NVIDIA GPUs
pa11y-ci - Pa11y CI is a CI-centric accessibility test runner, built using Pa11y
HeliosDisplayManagement - An open source display profile management program for Windows with support for NVIDIA Surround
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
screen_brightness_control - A Python tool for controlling the brightness of your monitor
cypress-fail-fast - A Cypress plugin to skip tests on first failure.
ModernFlyouts - A modern Fluent Design replacement for the old Metro themed flyouts present in Windows. [Moved to: https://github.com/ModernFlyouts-Community/ModernFlyouts]