pa11y
SwiftLint
pa11y | SwiftLint | |
---|---|---|
21 | 23 | |
3,958 | 18,322 | |
0.7% | 0.4% | |
5.8 | 9.4 | |
14 days ago | 4 days ago | |
JavaScript | Swift | |
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).
SwiftLint
- A problem when adding Swiftlint as a dependency on my won package?
- I need some answers on something very beginner unfriendly
-
Your favourite Xcode programming tools.
SwiftLint is a big one.
-
Just looking for advice on formatting code for clarity - [SwiftUI Shape]
I actually don't see anything worth changing. It looks good to me. I think the most important thing is just to maintain the constructive attitude you already have about future-you dealing with the code, because only future-you will really know where you could have done better. One personal-preference thing I carried over from working on Go code is to look for a tool like gofmt [1,2] for Swift. I've been using swift-format [3] for about 2 years and haven't been dissatisfied enough to reach for something more fully featured like SwiftLint [4]. I didn't like the idea at first of delegating most formatting control over to a tool designed with someone else's subjective idea of formatting. But my feeling afterward was that it was freeing: it was no longer (completely) my job/burden/responsibility. An "assistant" would clean up the formatting of my code every time I saved the file. That's a nightmare if you can't configure the tool as much as you need, but if you're lucky and find a configuration you can live with, it lets you focus more on naming and other conventions that aren't so easily automated (yet). [1] https://go.dev/blog/gofmt [2] https://twitter.com/bitfield/status/953395343353315329 [3] https://github.com/apple/swift-format [4] https://github.com/realm/SwiftLint
-
A Practical Approach to Automated Accessibility
iOS SwiftLint
-
Ask HN: Xcode users – how do you make it more usable?
1) Here are some tips & tricks for refactoring: https://developer.apple.com/documentation/xcode/finding-and-...
The “rename in project” or “rename in scope” functions are quite neat.
2) Check out SwiftLint: https://github.com/realm/SwiftLint
I have not used it in a while, but it comes with good defaults and is highly customizable to your own preferred Swift style.
-
How do you enforce that everyone in your team and your CI pipeline all use the same SwiftLint version?
Check this as well https://github.com/realm/SwiftLint
-
I am applying for jobs. Feedback and suggestions welcome.
Try SwiftLint. https://realm.github.io/SwiftLint/
-
Enforce Swift style and conventions with SwiftLint
if which swiftlint >/dev/null; then swiftlint else echo "warning: SwiftLint not installed, download from https://github.com/realm/SwiftLint" fi
-
Awesome macOS Libraries List
SwiftLint - A tool to enforce Swift style and conventions. Language: Swift.
What are some alternatives?
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
SwiftFormat - A command-line tool and Xcode Extension for formatting Swift code
axe-core - Accessibility engine for automated Web UI testing
Tailor - Cross-platform static analyzer and linter for Swift.
cypress-audit - ⚡ Run Lighthouse and Pa11y audits directly in your E2E test suites
OCLint - A static source code analysis tool to improve quality and reduce defects for C, C++ and Objective-C
pa11y-ci - Pa11y CI is a CI-centric accessibility test runner, built using Pa11y
Swimat - An Xcode formatter plug-in to format your swift code.
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
Flex - An in-app debugging and exploration tool for iOS
cypress-fail-fast - A Cypress plugin to skip tests on first failure.
FBMemoryProfiler - iOS tool that helps with profiling iOS Memory usage.