We have worked to make sayyeah.com accessible to folks by introducing an accessibility statement.
Visual Web Design
We’ve followed design best practices for:
Text sizes beginning with a larger than standard default type size for titles and body copy across various screen sizes including desktop, tablet, and smartphones.
Line width and line spacing with columns of text that do not exceed 100 characters to help improve readability.
Contrast checking for background/foreground element colour contrast to help ensure legibility.
We’ve used the following tool for contrast checking: WebAIM Wave.
State changes with distinguishing shapes to identify location or user actions. For example, the selected main menu item is underlined, not just colour shifted.
We’ve used the following tools to review colour blindness scenarios: Wickline Colour Filter Tool.
The site has been coded to have a responsive design in consideration of being legible across desktop, tablet, and smartphone screen sizes with little user effort.
In addition, with a responsive design in place, increasing font sizes helps content reflow to accommodate larger text sizes across any screen.
Screen Reader Support
The site has been structured to help assist screen readers using Accessible Rich Internet Applications (ARIA) Landmark Roles. This allows users to more easily jump to the appropriate content area of each page.
In addition to the ARIA Landmark Roles, we have used header tags throughout the site to identify titles, subtitles, and other content headers to help users navigate content sections.
A skip-navigation link has been included that is hidden until brought into focus by a screen reader.
We have predominantly tested using VoiceOver for Safari, Firefox, and Chrome on OSX and Safari on iOS.
We’ve been as thorough as possible in making our content accessible by taking the following measures.
Clear, descriptive text is used throughout the site, including menu items, buttons, and other elements. Wherever possible, text was chosen over images.
Where images have been used to enhance the content on the site, we’ve included descriptive alt attributes to help anyone who doesn’t have access to them understand how the images play into the content. Being a design agency, of course our case studies do include many images, but those case studies still include text which details our process and problem solving, and is just as rich a story as the images themselves.
We have also taken the effort to write out abbreviations, certainly with their first use, before introducing the abbreviations in parenthesis if we use the abbreviation repeatedly on the same page.
Links as well are descriptive in nature by default, but where we’ve included less descriptive links such as a “Read more” links on an article teaser, we’ve included descriptive ARIA labels.
By first following standards based code guidelines, we took the initial step towards an accessible website.
This site uses Cascading Style Sheets (CSS) for visual layout. If your browser or browsing device does not support stylesheets at all, the content of each page is still readable.
The layout accommodates resizing text and, as relative units have been used, text can even be re-sized in Internet Explorer for Windows.
Site pages use structured semantic markup. For example, content sections within in each page are identified and header tags are used for body copy content titles. In particular, this enables users of screen readers to jump to the content that’s most relevant to them, without hearing every single standard element of a page over and over again (such as a menu list).
In addition, we have worked to comply with World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) 2.0 and Accessibility for Ontarians Disabilities Act (AODA) Guidelines.
Our Product Insights site at http://productinsights.ca is managed by Tumblr, which greatly limits our accessibility options, as we have little control over the content steps noted above.
There are potentially some visual contrast issues that site impaired users may face should they not by default have adjusted their OS screen contrast or enlarged their type and/or web browser by default. If there are issues that you’re experiencing with your standard use of the site, please contact us (see Contact for Support below).
We have not considered specific cognitive disabilities.
We have not tested with Job Access With Speech (JAWS) or directly with any users of a specific disability. If you have feedback about the site or would like to do a walkthrough together, please contact us (see Contact for Support below).
We have not tested screen reading on Android, Windows, or any other platforms and browsers not noted above. If you’re having a specific issue, please contact us (see Contact for Support below).
Contact for Support
If you’re looking for help accessing any aspect of the site or the information on the site, please feel free to contact us via email at firstname.lastname@example.org or phone at 416.642.9694.