I'm speaking at Smashing Conf Amsterdam in about two weeks. In my talk I'm sharing accessibility tips, but not the typical "use alt" or "use a button" stuff. I'm trying to share useful but uncommon advice.

What's something you would share, that I can steal and use in my talk? 😁

@matuzo I read somewhere on Mastodon (but cannot find it) that someone said some people advice to convince stakeholders to implement better accessibility by telling them it helps with SEO (the typical „the largest group of blind website visitors are google’s crawlers), or these days, AI agents. However, that is dehumanizing since we wish to care about humans, not bots. I found that really interesting, dunno if it helps : )
@matuzo use Lynx or another text based browser to see how easy it is to navigate by keyboard (and check alt text etc).
CSS saturation to greyscale to see how important colour is to your navigation.
@matuzo specific domains like security, accessibility and maintainability of software products are like investments or insurances. The earlier you invest in them the more you gain from them. If you don’t have any of them you will have to pay the price sometimes in the future. Be it via horrendous costs in an emergency or for further development or because you are obliged by law to deliver specific requirements in that domain.

@matuzo Okay, this one will blow. Your. MIND!:

.

.

.

.

.

A button is not a div.

.

.

Bonus:

.

.

.

Put underlines on links.

@matuzo In NL some webshops were fined recently because of poor a11y. One could argue this is unfair because they already missed a significant amount of turnover. 🤔

Specify language.

On the <html> element, but also anywhere you use or link to another language.

@matuzo

@matuzo if you have an image in a link, then the alt text of the image serves the dual purpose of describing the image and being the accessible text of the link, so should make it clear where the link goes.

This is in response to all the header logos that go the homepage with the accessible name "Logo of $company"

@matuzo Accessibility is not the same as usability. And according to european law websites must not only be accessible, they must also be usable.
@vasilis @matuzo we need a WCUG.
@Kilian @matuzo … which would probably end every guideline with “test with real people”
@matuzo A lot of folks know they should use alternative text but aren’t sure what to write. This post by my colleague @spaceninja wrote seems to alleviate the pressure, I’ve shared it a zillion times (and not because I drew the feature image): https://cloudfour.com/thinks/write-alt-text-like-youre-talking-to-a-friend/
Write Alt Text Like You’re Talking To A Friend

“There was this dog wearing safety glasses, surrounded by chemistry equipment, saying ‘I have no idea what I’m doing.’”

Cloud Four

@matuzo Design for people with short attention spans who easily get confused. That's a lot of us these days, but the strategies also help with people who literally cannot see the whole page at once (screen reader users, screen magnifier users).

So, break forms into short steps, but also make sure there is always enough context about what has already been filled out & what will be asked in a next step. Same with information content: keep it structured, with table of contents or breadcrumb links.

@matuzo - more of a don’t:

Lay off the aria if you don’t know what it is for realz because I’m seeing a lot of bad things compliments of aria-label, aria-hidden and improperly using menu/menu item … and my favorite find was role=app because …. it “made all the automated accessibility errors go away.”🫠