Search the Community
Showing results for tags 'accessibility'.
Found 9 results
-
Make Brine Folder Navigation Keyboard Accessible
SJSchaidt posted a question in Coding and Customization
I am working with the Brine Template and want to make the navigation elements within the Header-nav-folder accessible via keyboard. Today, I am able to tab through these links; however, because the menu only expands upon hover of the parent folder, a user is unable to see that they are navigating through a sub-menu. This causes a huge accessibility problem for keyboard-only users. I couldn't find anything in the CSS that triggers this onHover for me to add an onFocus event handler, so I'm a bit stuck as to how to make this appear without the use of a mouse. Any help is appreciated! URL: www.lftphi.com -
Hello I need to add a a pixel tag on my website. But I need access to "orderTaxTotal" and "orderShippingTotal" to track orders on the confirmation page (code injection). Can you help me ? thank you
-
I am trying to set the alt text on an image to be blank. So far I have tried ... leaving the caption empty and turning the caption off (This leads to the image name as the alt text) setting the caption to a bunch of spaces and then turned the caption off. (this leads to the image name as the alt text) Anyone have other ideas?
-
Hi, I'm trying to improve my accessibility scores, and my audit is flagging up the following issues (see images 1 & 2). The "links do not have a discernible name" is point to the images in image 3, attached below. My website is johnbristoltherapy.co.uk. I have tried to change the name of the images in the content box, but it's not having an impact. And I can't find a way to edit the mobile menu button. Any help greatly appreciated! -
Can I modify the dropdown menu code for accessibility?
kgrahamsb posted a question in Coding and Customization
Hi there, Our business has been threatened with a lawsuit unless we upgrade our website to W3C standards for ADA compliance. I have managed to make all of the fixes required thus far via my limited coding skills or work arounds. I also downloaded a great (and free!) accessibility widget that seems to offer a lot of nice functionality. However, the dropdown menus in my product pages still can not be read by an e-reader and I can not figure out how or where to add custom code to modify them. I have found the code required but despite having gone into developer mode, I don't see where to inject this code in order to modify the drop downs and make them compliant. Has anyone else done this or can they point me to the right place? Or is this simply not doable on the Squarespace platform? Any thoughts or advice are welcome. -
Does anyone know how to add "title" attribute to the inline images on the Squarespace template? Seems these attributes are completely missing and are needed to improve image accessibility,
-
How can I modify the page header to remove the search icon and make the navigation menu accessible to WCAG 2.0 standards? I'm building a website for a research lab associated with a University and we need to make sure the site meets WCAG 2.0 standards. These two elements of the page are not compliant but I'm not seeing any way to modify them. Are these issues known to squarespace and are they on your development plan to address? If so, what is the expected timeline for that? Thanks! Jill
-
Making search icon (magnifying glass) accessible?
Jessica_C posted a question in Coding and Customization
There's no alt text or other label associated with the search icon, so screen reader software (I tested with NVDA) announces it as 'button'. Can anyone please help me figure out how to add in alt text - or similar, I'm open to other options - so that screen reader users can find and use the search tool on my site? (I want to avoid using one of the search style options that adds the word search on the screen - it not only dwarfs the rest of our navigation, but search appears to be placeholder text, so that wouldn't really resolve the screen reader issue.) -
Buttons do not have an accessible name When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers
