pa11y
mouse-scroll-wheel-acceleration-userspace
pa11y | mouse-scroll-wheel-acceleration-userspace | |
---|---|---|
21 | 13 | |
3,958 | 129 | |
0.7% | - | |
5.8 | 4.3 | |
14 days ago | about 1 month ago | |
JavaScript | Python | |
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).
mouse-scroll-wheel-acceleration-userspace
-
Linux Touchpad Like MacBook Update: 2023 Progress on Smooth Scrolling
If you want to have mouse scroll wheel acceleration, you might be interested in a small project of mine: https://github.com/albertz/mouse-scroll-wheel-acceleration-u...
I'm using this all the time on non-Mac platforms. Once you get used to this, it's hard to get back.
But I'm still waiting that such a feature gets more built into the core, e.g. libinput or so.
-
Scrollbars Are Becoming a Problem
Regarding quickly scrolling around in a large document, there is also scroll wheel acceleration, i.e. the users finger scroll speed is not just a linear function mapped onto the software scroll speed but rather it can accelerate.
MacOS, iOS and Android have this anyway, and a few custom software as well.
I implemented a cross platform user-space variant of this, to get mouse scroll wheel acceleration. You can even use this in addition to the native scroll wheel acceleration on MacOS.
https://github.com/albertz/mouse-scroll-wheel-acceleration-u...
-
how do i make the touchpad not garbage on a macbook pro running ubuntu
Turn on adaptive acceleration. Enable gestures. Look into this project that ports macOS-style scrolling acceleration to X11 and Wayland: https://github.com/albertz/mouse-scroll-wheel-acceleration-userspace
- Mouse scroll wheel acceleration, implemented in user space
-
Show HN: iPod Clickwheel.js
I never had an iPod, but I wonder, did it use some acceleration scheme? I.e. your physical scroll speed was not just linearly mapped to the virtual scroll speed but some quadratic or even exponential scheme?
Because I know that they do the same on OSX for scrolling, i.e. scrolling has an acceleration scheme, which I very much enjoy, and always miss when I'm on other operating systems.
For that reason, I implemented such scroll acceleration in user space. Some further details and references are in the README. https://github.com/albertz/mouse-scroll-wheel-acceleration-u...
-
Having a really hard time switching to Linux...
Workaround: https://github.com/albertz/mouse-scroll-wheel-acceleration-userspace. Enables inertia in Chromium and Qt apps, but breaks it in GTK apps (fun!).
-
So as I was browsing Google and KDE's Reddit community, I found out that lots of users having problems with annoyingly slow scrolling speed in KDE, or other Linux-Based OS. So I decided to make a quick guide on how to fix that:D Hope you will find this guide helpful!
Good video, but I find https://github.com/albertz/mouse-scroll-wheel-acceleration-userspace a much better solution.
What are some alternatives?
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
touchegg - Linux multi-touch gesture recognizer
axe-core - Accessibility engine for automated Web UI testing
egl-wayland - The EGLStream-based Wayland external platform
cypress-audit - âš¡ Run Lighthouse and Pa11y audits directly in your E2E test suites
ibus-typing-booster - ibus-typing-booster is a completion input method for faster typing
pa11y-ci - Pa11y CI is a CI-centric accessibility test runner, built using Pa11y
clickwheel-js
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
Joplin - Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS.
cypress-fail-fast - A Cypress plugin to skip tests on first failure.
ipod-classic-js - An iPod Classic emulator that connects to Apple Music and Spotify. Built with React & Styled Components