About This Site
Every attempt was made to create these pages using valid XHTML. There is more information on the guidelines we used below.
Logo Styles
You may require a copy of our logo for publication. It is available in the following non-editible, non-enlargable formats.
- SCREEN USE ONLY (email, html): GIF Format
- For print with brown bar: Tiff Format
- For print without brown bar: Tiff Format
Code Validation
We tried to create a site that is simultaneously forward and backward compatible. If you are viewing these pages with an older browser or through your PDA then the site may "render" differently - although the content should still be fully accessible.
Test our claim of validity: Click the W3C XHTML or CSS buttons on the bottom of the pages of this site than the page you are viewing will be automatically assessed with a validator.
Due to the limitation of the validators, some pages on this site will not validate. For example, if the page contains a hyper link with a database query - the code is considered invalid. This is an unavoidable limitation of the validator. If a page doesn't validate and you think it should, please contact us.
We were asked to structure and code this website to maximize accessibility. With that in mind, we have used IBM's web accessibility checklist v3.1 and we have tried to conform to Level A of the W3C Web Content Accessibility Guidelines 1.0, including all Priority 1 checkpoints defined in the Guidelines. These are listed below. If you think we could be doing better, please contact us with your suggestion.
W3C Web Content Accessiblity Guidelines 1.0 - Level A (WCAG 1.0)
Guideline 1
Provide equivalent alternatives to auditory and visual content.
Action Taken:
Included "alt" tags on all images and provided a description to all images used. Some images have explanations omitted because the images will not add to the understanding of the links or navigation.
Guideline 2
Don't rely on color alone. Ensure that text and graphics are understandable when viewed without color.
Action Taken:
In-line links are underlined and bold. Top links are in expected areas. Side links have arrows in front of them. Shape, color and underlining define links. We've included a list of identical links at the bottom for convenience.
Guideline 3
Use markup and style sheets and do so properly. Mark up documents with the proper structural elements. Control presentation with style sheets rather than with presentation elements and attributes.
Action Taken:
We've separated content from style (for the most part). That means we used Cascading Style Sheets to present this site. You can see what we mean if you look at this site in an older, non-compliant, non-accessible browser such as Netscape 4.
Guideline 4
Clarify natural language usage
Action Taken:
We've tried to make our writing clear and straightforward.
Guideline 5
Create tables that transform gracefully. Ensure that tables have necessary markup to be transformed by accessible browsers and other user agents. Tables should be used to mark up truly tabular information ("data tables"). Content developers should avoid using them to lay out pages ("layout tables"). Tables for any use also present special problems to users of screen readers.
Action Taken:
We are not using tables. Not only does this aid in accessiblity but it reduces maintenance costs.
Guideline 6
Ensure that pages featuring new technologies transform gracefully. Ensure that pages are accessible even when newer technologies are not supported or are turned off.
Action Taken:
You can read the content of this site and navigate through it even if you are using an older, non-compliant, non-accessible browser such as Netscape 4. What you won't see is the layout. Layout is very important, but it's not critical to see the layout to get the information. We feel it's worse to leave someone out because they can't understand the way your content is structured. Did we succeed or fail? Let us know.
Guideline 7
Ensure user control of time-sensitive content changes. Ensure that moving, blinking, scrolling, or auto-updating objects or pages may be paused or stopped.
Action Taken:
We used a small amount of animation on the home page. We made sure that it moves pretty slowly, turned on all accessibility features in Flash MX and made it possible to repeat the animation.
Guideline 8
Ensure direct accessibility of embedded user interfaces.
Action Taken:
We have made the "replay" button on the home page animation accessible. We didn't make it too obvious because viewing the animation is not critical as we have made the text of the animation available.
Guideline 9
Design for device-independence. Providing text equivalents for image maps or images used as links makes it possible for users to interact with them without a pointing device. Refer also to guideline 1.
Action Taken:
We put text equivalents beside images as necessary and provided redundant links at the bottom of each page.
Guideline 10
Use interim accessibility solutions so that assistive technologies and older browsers will operate correctly. For example, older browsers do not allow users to navigate to empty edit boxes. Older screen readers read lists of consecutive links as one link. These active elements are therefore difficult or impossible to access. Also, changing the current window or popping up new windows can be very disorienting to users who cannot see that this has happened.
Action Taken:
We did not use new window links. We didn't use any pop-up windows. We put most of our links in unordered lists.
Guideline 11
Use W3C technologies (according to specification) and follow accessibility guidelines. Where it is not possible to use a W3C technology, or doing so results in material that does not transform gracefully, provide an alternative version of the content that is accessible.
Action Taken:
We haven't provided any alternative content, we are trying to make sure that this site comnforms "as-is". If you are using an assistive technology and are having difficulty, we want to know right now. Contact us at webmaster@cathexisconsulting.ca!
Guideline 12
Provide context and orientation information to help users understand complex pages or elements. Grouping elements and providing contextual information about the relationships between elements can be useful for all users. Complex relationships between parts of a page may be difficult for people with cognitive disabilities and people with visual disabilities to interpret.
Action Taken:
We have tried to use header elements and tags the way in which they were originally intended, but we also tried to make them appear beautiful (which wasn't absolutely necessary, but what the heck).
Guideline 13
Provide clear and consistent navigation mechanisms -- orientation information, navigation bars, a site map, etc. -- to increase the likelihood that a person will find what they are looking for at a site. Clear and consistent navigation mechanisms are important to people with cognitive disabilities or blindness, and benefit all users.
Action Taken:
We have grouped the main navigational elements across the top of the page because this is where people expect them to be. We've been as consistent as possible with all our links. For those accessing the page with assistive technologies, we organized grouped links as unordered lists. We didn't do this just for people using alternative ways to surf the web, we included this scheme for everyone!
Guideline 14
Ensure that documents are clear and simple so they may be more easily understood. Consistent page layout, recognizable graphics, and easy to understand language benefit all users. In particular, they help people with cognitive disabilities or who have difficulty reading. (However, ensure that images have text equivalents for people who are blind, have low vision, or for any user who cannot or has chosen not to view graphics. Refer also to guideline 1.)
Action Taken:
We have tried to be consistent throughout the site. We have also adhered to Guidelines 12 and 13 which relate to this guideline.
Home
