Springshare: A-Z list descriptions: linked text not working

[lauraedwardseku]

No description provided.

[jensarneson]

Springshare Ticket # 334950

They got back and said it was likely due to "smart quotes" which apparently come from Word and the like. seems unlikely to me

[lauraedwardseku]

i guess i can understand why they would say that since this is problem behavior libguides editors engage in.

[lauraedwardseku]

it seems like some entries look fine now, but others are still weird. I was able to update the NY TImes Online linked text to remove the extra quotes (smartquotes ?), and it appears to have stuck this time around.

A couple other entries still have the smartquotes displaying though. Leaving those alone so you can troubleshoot with springshare as needed. @jensarneson

[jensarneson]

Springshare regarding smartquotes

It looks like the link in the New York Times Online database asset's description is having issues because the code that was added used smart quotes / curly quotes. These can come along when copied from other webpages or documents like Microsoft Word docs (it's a bit difficult to tell where exactly these originated).
Likely what happened was that the link was added with smart quotes in the legacy A-Z view, then it was opened in the new A-Z editor and re-saved. Then the new interface would have tried to adjust itself to work with those quotes.
If you ever see this, I'd recommend deleting both sets of quotation marks in the new interface, then retype them. That should default to the regular un-styled quotation marks. Alternatively, you could unlink then relink the text.
If doing that still doesn't solve the problem please let us know!

[jensarneson]

Springshare regarding em tags being converted to i tags

I'll let our Accessibility team know about your concern so they can investigate further. We know how critical accessibility is and we strive for full accessibility across all of our products.
As far as our testing to date has indicated, LibGuides is fully accessible according to VPAT guidelines. (see attached January 2023 VPAT for LibGuides)
If/when you need to check for updated documents in the future, you can always download the current copy of our VPATs from the VPATs category in the Springshare Lounge. This version of the VPAT also covers Section 508, WCAG 2.1.
If you're not a member of the Lounge, we highly encourage you to become a member so you have access to resources like this and can chat with fellow Springshare users!

All of this said we are constantly adding new features and improving our back-end code. The task of ensuring that a page or tool is accessible is an ongoing process. Accessibility testing itself is also an ongoing process, and we rely on our clients to provide any feedback that comes as a result of their own in-house accessibility testing to inform our own accessibility improvements. If you ever run accessibility checks and find issues/errors, please submit those reports to us. We will review them and do our best to address issues!

[lauraedwardseku]

@jensarneson thanks for adding Springshare comments. do you have the ticket/case# for the report?