Community @ The Turning Gate

So i've redirected traffic from that other thread to here, to keep the topic consolidated and easy to follow.

As I've said above, not a big deal for me to change the ALT attribute on images to take caption or title, using file name as ultimate fallback. But I will need invested parties (i.e. you all) to come to some consensus on your preference for sequence of possible sources.

Like ...

Title => Caption => Filename?
Caption => Title => Filename?

Or ... let's not go bananas, but I'm open to other suggestions as well.

Uh ... if you're going to mess with that, just be careful to ensure that your changes don't complete mess things up on phones. By default, the pallet has a fixed width to a point, and then just takes up I think 85% of the width, which allows it to not be busted on iPhones 320px wide or whatever.

I've put a lot of thought and safety measures into this aspect of the page layout, so just be careful not to hang yourself with all the rope you're taking. ;-)

Backlight is set up in such a way that if you're doing the work for good SEO, then you should be pretty damn near where you want to be for ADA as well. We've always encouraged users to adopt good file-naming practices, as well as captioning and titling of images. A lot of this stuff is less about the platform, and more about the content.

Alt tags for images are using file name, but it wouldn't be that big of a thing for us to switch that out for titles or captions, and fall back on file names when those are empty.

In HTML, the ALT attribute is -- insofar as I am aware -- only available for IMG tags, and INPUT tags with type="image". Therefore, putting this on our icons -- which are font-based -- would be invalid. If we were to make any changes in this regard, we would probably need to rely on the TITLE attribute where valid, else land on an appropriate aria attribute.

I am happy to see that the gist of this discussion seems to be that Backlight is already doing most of the things you'd want it to be doing.

I try. ;-)

I'm not seeing any problem using the latest Chrome. What browser are you using? Are you seeing the same behavior in multiple browsers?

CSS

.grid-button.crg-select {
  top: auto;
  right: auto;
  bottom: 0;
  left: 0;
}

I lost track of this thread, sorry. Thanks, Daniel!

No problem. I'm glad things are working well for you now.

Backlight 2 runs on PHP 7 without issue, receives updates for evolving compatibility, and will continue to receive such updates until either there's a Backlight 3 or we declare end-of-life, whichever comes first.

Should be fixed now.

Oh, I see what you mean. Unfortunately, that's probably not possible without rewriting the Fancybox implementation. You'd need to tie into the lifecycle callbacks for each slide, so that the button gets moved every time the image changes. Not really practical to do for either of us.

Instead, I would reevaluate the value of having or not having items in the Image menu, and I would either put more things in there, or remove it entirely.

Link?