Accessibility

This website was recently updated for copy (from Ashley) and theme styles. I’ve gone through all the pages to clean up layer order. As well as do a test update with VoiceOver, TalkBack, VoiceAccess, and Voice Control.

VoiceOver on Chrome (Mac) Issue: Error navigating the header menu on desktop. Menu is skipped over after “Skip to Content”. You may need to go back for the navigation, visit the site map, or use the Safari browser.

This site was built on Squarespace 7.1 from a blank template. Each page was created using the grid, and tested for correct layout order. In order to make Squarespace more accessible, the following custom elements were involved:

Custom CSS

(1) That cookie banner was fixed to have larger button clickable areas, including the Skip to Content feature.

(2) Site-wide links have been styled to have distinct hover and focus states. We’ve made them more visible for sighted visiters/keyboard navigators to find.

(3) The mobile menu was changed to align the list at the top. As well as scale down, but still large enough to have a good clickable area.

(4) Form inputs, am I right? That standard template was so low in contrast. We spaced out the form fields, to give it some breathing room. As well as defined input states (static/hover/focus), and enlarged that submit button.

Code Injection

(1) For our Blind/low-vision, and assistive tech using visitors, we added some JQuery to hide decorative shapes and section dividers. Basically, it adds an “aria-hidden” feature to any background boxes, horizontal spacers, and section borders.

(2) We added a scroll up button at the bottom corner of the page, with a fixed positioning. So our visitors with fatigue (like myself) can stop the endless scrolling.

The Basics

AshleyGregoryTherapy.com was made to include alt text, proper contrast, larger and spaced out text, and a site map with a site-wide search function.

During the development, I tested the website with multiple devices and techniques. Some methods I use as a disabled person myself, others I help test for. The development above was created based on this testing.

First, I used desktops. Keyboard only navigation, so there were no traps! As well as using assistive technologies. I tested with VoiceOver on Safari (Apple iMac Ventura and MacBook), as well as Narrator on Microsoft Edge (Windows).

Then I checked mobile accessibility. Using TalkBack and VoiceAccess features on my Samsung Galaxy S20 Pro (Android), I tested for screen reader and voice command functionality.

It should be noted, I am no expert with screen readers. Please read the community feedback section below for further detail.