jwithnell

p.sqsrte-large      works Thanks! I've been needing an alternate text and didn't want to us an h3-6 and mess up the header hierarchy. 

Thank you Tuanphan, I ended up getting help via Livechat -- it turned out to be a problem with  custom CSS I'd entered to try to create secondary navigation. Seems odd that non-script CSS could affect the interface.

Thank you for your willingness to help. The screenshot shows what I get when I try to click to add a title -- either new or an "existing" title because I've duplicated a template page I've previously created. Do you know if SS has made a change in blogging because of the new engine? This has only been a problem for a week or so.

Here's an example but I don't think you'll be able to access it. The only password I can share is "owner" for several websites. I've wanted to create a contributor low-access profile but SS blocks any email address that has already had access to any of my sites.

https://daffodil-wombat-eg7x.squarespace.com/config/pages/62a89a96bb7c6a3de9c098a2

For the last few business days I have not been able to edit the titles in a blog using SS 7.1  If I click anywhere in the title area it bring up a global styles dialog box. I've not previously had any problems simply entering a title where it goes at the top. I have a template that I duplicate when creating a  new post and change the template space-holder title for the real one.

Site URL: https://www.bethelpres.com/404

So many fixes begin with a block identifier that has  coding applied to that specific block. I absolutely cannot get this to work though I've copied and pasted others code (including from this forum) and have used the Chrome extension to identify the blocks. I've tried this is in 7.1 and 7.0 and on sites that have been made public and those that haven't. The attached screen grab is from a live 404 page that I was trying as an example. The hex code should have turned the "Oops" gold. There must be something incredibly simple that I am overlooking. Thanks for any insight.

Well, at least y'all are telling me that I'm not totally crazy. It's frustrating to have the problem and also to see how long it has taken SS to fix the problem. I must have a specific order for the photos to correspond to information on the rest of the page. 

I've worked with typefaces forever and had to meet ADA requirements for printed publications in a former job.

The "old" rule of thumb is that a body font with serifs is easier to read because it helps a reader follow a line. Major news organizations still use a serif body type on the web including ones associated with video such as ABC.

But When I read about accessible fonts, every one listed is sans serif. For the dyslexic reader, advisors are concerned about the consistency for font strokes which means their selected lettering also falls into the sans serif camp. 

I'm currently in redesign for a website to switch to Squarespace 7.1. It includes many long-read articles so the body text selection is critical. I'm also being consulted on a print project for an entity that is extremely concerned that it makes all of its resources accessible.

Thanks for any guidance you might have