ooccoo

are you gonna eat that

I am the new reckoning of society I am also some lady that likes to make loud noises with technology


posts from @ooccoo tagged #disclaimer i dont use a screenreader i read about this on a mozilla accessability guide.

also:

lunarfox22
@lunarfox22

this is just occurring to me but one thing i'm going to tell everyone who is thinking of moving to a personal site.

If you put an img tag on your website, and it doesn't display correctly because you forgot the quotes around the src field when you were writing the tag, you would see that right away and go "Oh, that's not right, I wanted an image there, I need to fix that," because you want people to be able to see the content in the image, that's why you put it on your site. Similarly, if you type 5,000 instead of 500 on the width and the image stretches out way too wide, you would go "Oh, lol, that's wrong, lemmie take care of that." Because you want the image to make sense.

You should have the same mindset about alt text fields on img tags. If it's missing or doesn't do a good job making the image make sense to someone, then it's a thing on your website that isn't working the way you meant it to. If you don't use screen readers, however, this is not as easy to notice as a missing or badly scaled image, so it might get missed. Just remember to check that it's there, and make sure it makes the image make sense if you can't see it.

If you wanna write really good alt text descriptions there's lots of resources out there to learn to do that, just like with learning html, but just make a sincere attempt.


ooccoo
@ooccoo

One other little bit of accessibility that i always remember for some reason is to put links on words thaf describe the destination. So, like, if I was going to link to wikipedia, i wouldnt do:

Read about it on wikipedia here.

I would do:

Read about it on wikipedia.

This is bc many screenreaders allow you to quickly navigate between links on a page, and this helps people identify the link.