Jump to content

Search the Community

Showing results for tags 'wcag'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Forum
    • Welcome to the Forum
    • Customize with code
    • Commerce
    • Feedback on Your Site
    • Images & Videos
    • Pages & Content
    • SEO
    • Products
    • Resources
  • Colorado Designers's Topics
  • Squarespace Forum Club Guidelines's Topics
  • Austin, TX Designers's Club Discussion
  • New York City Designers's Club Discussion
  • Berlin Designers's Club Discussion
  • SEO Experts's Club Discussion
  • Photographers's Club Discussion
  • Graphic Designers's Topics
  • London Designers's Topics
  • Podcasters's Club Discussion
  • Custom Coding Help's Club Discussion
  • Atlanta, GA Designers's Topics
  • Seattle, WA Designers's Topics
  • San Diego, CA Designers's Topics
  • Dallas, TX Designers's Topics
  • Australia Designers's Club Discussion
  • Minnesota Designers's Topics
  • Minnesota Designers's Topics
  • Copywriters's Topics
  • France Designers 🇫🇷's Topics
  • France Designers 🇫🇷's Topics
  • Portland, OR Designers's Topics
  • Canadian Website Designers's Club Discussion
  • Los Angeles Designers & Devs's Club Discussion
  • South African Designers's Club Discussion
  • Brazil Designers's Club Discussion
  • Developers's Club Discussion
  • German Circle Members's Topics

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me




Expert ID

Found 2 results

  1. There are far too many basic accessibility issues with Squarespace, that need to be corrected with injecting custom code. Their new "integrations" for auto-focus and skip to content, is far from enough. After building a site for a client, here are some basic things I've had to implement to make it SEMI W.C.A.G. 2.1 compliant [and who are we kidding, compliance is the bare minimum for accessibility]: Links & Hover States: CSS for hover states on interactive elements. Inline and button links edited for padding and legibility. Header & Navigation: Site tagline within a content property for screen readers. Navigation link styling, Mobile fixes for better spacing and alignment. Footer Social Links: Original block was not screen-reader accessible using VoiceOver and TalkBack. Custom HTML block replacement for better descriptions, and sizing. Newsletter, Search & Forms: Field style edits for better visibility. Error box edited for better contrast. Replacing red with the redwood brown and ivory moon text. Squarespace Pages: Custom CSS and coding to fix internal pages. Including search results, 301 password protected pages, and blog and shop features. (As much as possible.) And that's just a brief overview. The fact that we can't even add a compliant hover state, is ridiculous. I had to build out an entirely custom social footer link block just because it doesn't read out the social platform the icon goes to. For example, Patreon doesn't have an icon, so it uses the link icon. Which screen readers call out "link". That's it. Adding custom CSS/development code is not best practice, and causes clunky loading. Who can we get in touch with to improve Squarespace accessibility?
  2. Site URL: https://enclaveatbaristo.com/ My client is a developer whose development has sold out... so the website is no longer necessary. We don't want to take it down because it will be a useful marketing tool for his next development. My client is baulking at the $490 fee to continue website accessibility with AccessiBe (a solution I use for most of my clients). What are our options? Downloading the site to a PDF that looks good doesn't seem to work... Thanks in advance for any advice or creative thinking!
  • Create New...

Squarespace Webinars

Free online sessions where you’ll learn the basics and refine your Squarespace skills.

Hire a Designer

Stand out online with the help of an experienced designer or developer.