March Meta Matters Challenge, Check-in 2

[yourlibrarian]

Hello everyone! It's check-in time to see how we're all getting along with our meta importing.

Comment below with any of the following:

1) How do you motivate yourself when you're facing something daunting or overwhelming?

2) How many works have you identified for future transfers, or have you now moved to AO3?

3) Are you having any problems moving your meta?

Remember, this account accepts anonymous comments, so if you don't have a Dreamwidth account we still want to hear from you and have you take part.

Also, if you've got tips you've developed during this process, do share them with the group! And if you can help someone out with a problem they're having, share a solution.

Comments

[alexseanchai]

It just occurred to me I forgot something.

What I put in as the image source URL in the failed images above is a legit URL. You can view the image just fine by clicking the link. It's just not the URL to the image itself.

Now, if I want the image to be the clickable thing for a hyperlink, like the words 'a legit URL' are above, I could do <a href="LINK"><img src="IMAGE URL" /></a> and it would work fine—for people who can view the image. Not so helpful for screenreader users or when the image doesn't load.

Here's such an image-as-hyperlink where the image fails as above and there isn't alt text:



And one where there is:



Also, if for whatever reason one wants an image to be present (as a decorative element or whatever) for people who can view images, but not to trouble people who don't, doing like <img src="IMAGE URL" alt="" /> means the screenreader will simply skip it. This is preferable to <img src="IMAGE URL" /> because the screenreader will read the file name, which is most likely unhelpful, and (as you see with my example image) sometimes total gibberish.