I always enjoy these "learn as you blog" kinds of posts 😃
Having used both of these tools on different occasions, I've personally found aXe to be my favorite under the right conditions. Ember actually has an aXe extension, and it highlights specific issues on the webpage as you view it locally. For example, anchor tags opening in new windows missing certain tags will appear with gray stripes over them and have the issue detailed in the console. However this may be specific to the Ember extension, so it may reflect other people's experiences too easily.
Also I'd be interested in a follow-up looking at how pally can test different screen interactions! I've used it before for basic "can you click this menu link," and the syntax is thankfully straightforward.
"actions": [
"click element .navbar__links > li:first-of-type > a",
"wait for element .navbar__links > li:first-of-type > a + .navbar__sublinks to be visible",
"click element .navbar__links > li:first-of-type > a + .navbar__sublinks > li:first-of-type > a",
"wait for url to be http://localhost:4000/another-page"
]
I'm unsure if it checks for accessibility needs beyond being immediately clickable and visible. At the very least it finds out if common user interactions on a page are busted. Personally I think it's one of pa11y's greatest strengths.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I always enjoy these "learn as you blog" kinds of posts 😃
Having used both of these tools on different occasions, I've personally found aXe to be my favorite under the right conditions. Ember actually has an aXe extension, and it highlights specific issues on the webpage as you view it locally. For example, anchor tags opening in new windows missing certain tags will appear with gray stripes over them and have the issue detailed in the console. However this may be specific to the Ember extension, so it may reflect other people's experiences too easily.
Also I'd be interested in a follow-up looking at how pally can test different screen interactions! I've used it before for basic "can you click this menu link," and the syntax is thankfully straightforward.
I'm unsure if it checks for accessibility needs beyond being immediately clickable and visible. At the very least it finds out if common user interactions on a page are busted. Personally I think it's one of pa11y's greatest strengths.