1 point by webdev_newb 7 months ago flag hide 18 comments
accessible_coder 7 months ago next
Great question! I've been using Axe by Deque for accessibility testing. It's fast, accurate and supports various integration options like plugins, browser extensions, API, and CLI.
a11y_advocate 7 months ago next
@accessible_coder Agree! Axe is my favorite tool too! In addition to the above integrations, it offers great reporting capabilities as well.
devops_guru 7 months ago prev next
For automated accessibility testing, I recommend Tenon.io or SiteImprove. Both tools integrate very well into CI/CD workflows and offer rich APIs for developers.
qa_engineer 7 months ago next
@DevOps_Guru I recently started using Pa11y as well, it works pretty well with Docker, allowing easy spinning of containers for testing.
accessibility_expert 7 months ago prev next
One must-have manual testing tool in your accessibility toolbox is the W3C's Web Accessibility Evaluation Tool and Wave by WebAIM. These help you quickly identify the wide variety of accessibility issues.
designer_gal 7 months ago next
@accessibility_expert I have found the WAVE extension for Chrome and Firefox to be incredibly useful to pinpoint accessibility issues while designing interfaces.
color_coder 7 months ago prev next
Don't forget color contrast validators while dealing with accessibility testing. Check out WebAIM's Color Contrast Checker and the following Stark plugin, which enable you to check color contrast in real-time.
javascriptninja 7 months ago prev next
Accessibility Insights for Web is now my go-to tool when doing browser-level testing. It's a Chrome extension with powerful features to help you discover, diagnose, and fix issues related to accessibility.
frontendlad 7 months ago next
@JavascriptNinja Would you recommend that I start with an automated accessibility test using the said tool or start manual testing?
javascriptninja 7 months ago next
@FrontEndLad I'd suggest you do both. Start automated testing followed by manual testing since manual testing helps you uncover accessibility issues that may have been overlooked in the automated testing phase.
uxguru 7 months ago prev next
To add to previous answers, review your website on a variety of devices/browsers, and use Assistive Technology like screen readers (JAWS, NVDA and VoiceOver), speech recognition software (Dragon NaturallySpeaking), and text-to-speech conversion tools. More details on @w3c_wai resources on using assistive technology.
keyboard_champ 7 months ago next
@UXGuru I want to specifically highlight keyboard navigation testing which is imperative. Test your website's functionality using only the keyboard to identify shortcomings.
aria_user 7 months ago prev next
To test ARIA attributes, you may use the WebAIM's screen reader simulation mode in the WAVE extension or the ARC Toolkit. Friends, don't forget to test your custom ARIA implementations for assistive technology compatibility.
inclusivedesigner 7 months ago next
@ARIA_user I have a question while testing ARIA attributes using ARC Toolkit, is ARC capable of recognizing aria label implementation for SVG elements?
aria_user 7 months ago next
@InclusiveDesigner Yes, ARC Toolkit supports recognition of aria labels attached to SVG elements; however, you'll want to ensure it functions correctly using assistive technology.
frontend_dev 7 months ago prev next
Apart from tools, another tip I'd like to offer is education and adopting an inclusive mindset. Encouraging your team to learn and adopt good accessibility practices throughout development is essential.
interaction_designer 7 months ago next
@frontend_dev You're right - having in-house knowledge and the ability to understand how people with disabilities interact with your website significantly contributes to its overall accessibility.
marketing_master 7 months ago prev next
@frontend_dev As you prioritize #accessibility education, don't forget to explore resources such as webinars, blogs, and podcasts to stay up-to-date and share with your entire company.