Live data from Hacker News

Show HN: MAWD – Simple web accessibility testing for developers

myaccessible.website

11–14 of 14 posts

Re: Show HN: MAWD – Simple web accessibility testing for developers

#11
post #9

This is a very spammy comment, but if anyone is interested but it's not a good time to sign up, you can sign up to my (totally not spammy) mailing list and get an accessibility poster as a bonus: https://myaccessible.website/subscribe

This link should be somewhere on the page - I didn't want to sign up to a beta but wanted to be notified about updates and couldn't see where to.

Thank you - I will add this in.

Re: Show HN: MAWD – Simple web accessibility testing for developers

#12
Thumbs up for making the web more accessible! I was fortunate to work on a project with a WCAG AA requirement for the last 1.5 years, so I can only imagine how overwhelming is must be for people outside this area to make their sites accessible.

> MAWD is designed to pick up 100% of the issues with a site, but she needs your help to do it.

> 4 WCAG criteria fully tested. 22 different tests

There are 4 WCAG principles with 12-13 guidlines, each having at least one success criteria. There are about 60 success criteria, so 22 different tests are far from 100%. I've also encountered many subjective decisions and screen reader quirks. It's probably much better than fully-automated tools (like pa11y or axe), but it still takes a lot of experience to find and fix all accessibility issues. I suggest lowering the "100%" claim.

Re: Show HN: MAWD – Simple web accessibility testing for developers

#13
I just received this email from you:

>I’m going to send you a few emails over the next couple of weeks to give you some hints and tips.

Yeah, so I just marked your email address as spam. I never subscribed for any newsletter and there isn't any unsubscribe button either in your mail nor your website. Just stop.

Re: Show HN: MAWD – Simple web accessibility testing for developers

#14
post #5
post #2

The robot image on the home page doesn't have any alt text. Not a good start for an accessibility checking service.

The image is basically there to be decorative. In that scenario, an empty alt attribute is used to inform assistive technology that yes, there is an image here, but it isn't adding any further information. It's actually one of the main things that MAWD helps with right now. Putting alt text on all the images of random cats on a website only adds value to people if the cats are at all relevant to the content :) https:…

Wouldn't adding role="presentation" be good for an image that is purely for decoration?
Post reply on HN