Accessibility for Differently-Abled Clients

Everyone has different challenges as they traverse this life, as they seek to learn about their patterns and evolve. Out of respect for the challenges faced by some of my clients, I created WholeSpirit.com to meet the WAI Web Content Accessibility Guidelines, and in my view it meets the criteria for Triple-A Conformance. However, it is possible there are areas where this website does not meet an individual's particular challenges. If you have any accessibility issues, or you find a particular feature difficult or impossible to use, please do contact me. In addition, I do offer an offsite office space that allows enhanced access for those of you who face mobility challenges.

Guideline 1 — Provide equivalent alternatives to auditory and visual content

Provide content that, when presented to the user, conveys essentially the same function or purpose as auditory or visual content. Skip table  

Checkpoint

How the Checkpoint is addressed

1.1 Provide a text equivalent for every non-text element. This includes: images, graphical representations of text, image map regions, animations, applets and programmatic objects, ASCII art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds, stand-alone audio files, audio tracks of video, and video.

Accomplished. All informational and navigational elements fully functional as html when scripting disabled.

1.2 Provide redundant text links for each active region of a server-side image map. Not applicable.
1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. Not applicable.
1.4 For any time-based multimedia presentation, synchronize equivalent alternatives with the presentation. Not applicable.
1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. Not applicable.

Guideline 2 — Don't rely on color alone

Ensure that text and graphics are understandable when viewed without color. Skip table  

Checkpoint

How the Checkpoint is addressed

2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. Color is used to convey link hover, visited, and unvisited states. These link color differences are based on differences in color intensity, and are easily apparent using the Vischeck color deficit simulator.
2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. All website page content is easily readable when tested using the Vischeck color deficit simulator.

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 presentation elements and attributes. Skip table  

Checkpoint

How the Checkpoint is addressed

3.1 When an appropriate markup language exists, use markup rather than images to convey information. All information is textual. Where an image conveys meaning, alt and title tags ensure continued functionality when images are not displayed. Website menus are based on HTML unordered lists, and retain their full hierarchical sense with images and scripting disabled.
3.2 Create documents that validate to published formal grammars. All pages on this website validate to XHTML 1.0 Strict.
3.3 Use style sheets to control layout and presentation. All pages and elements use CSS for styling, and the use of non-semantic elements is strictly minimized. The one minor exception is the occasional use of break tags. No presentational attributes are used.
3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.

Relative units such as percentage or "em" are used wherever possible, subject to the limits of cross-browser compatibility. Where other units are used, the pages have been evaluated across all common browsers.

3.5 Use header elements to convey document structure and use them according to specification. Headings are used semantically to organize each web page. Headings are also used within the navigation menus to convey top-level sections on the navbar, as distinct from the navigation links on submenus.
3.6 Mark up lists and list items properly. Accomplished.
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. Accomplished.

Guideline 4 — Clarify natural language usage

Use markup that facilitates pronunciation or interpretation of abbreviated or foreign text. Skip table  

Checkpoint

How the Checkpoint is addressed

4.1 Clearly identify changes in the natural language of a document's text and any text equivalents. Not applicable.
4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. Accomplished.
4.3 Identify the primary natural language of a document. Accomplished.

Guideline 5 — Create tables that transform gracefully

Ensure that tables have necessary markup to be transformed by accessible browsers and other user agents. Skip table  

Checkpoint

How the Checkpoint is addressed

5.1 For data tables, identify row and column headers. Accomplished where applicable.
5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. Accomplished where applicable.
5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). Accomplished.
5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. Accomplished.
5.5 Provide summaries for tables. Accomplished.
5.6 Provide abbreviations for header labels. Not applicable.

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. Skip table  

Checkpoint

How the Checkpoint is addressed

6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. Accomplished.
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. Accomplished.
6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. Accomplished with the exception of the Twitter and LinkedIn widgets on the Channels page.
6.4 For scripts and applets, ensure that event handlers are input device-independent.

Not possible at this time. However, the main navbar is keyboard accessible.

6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. Accomplished where possible. See 6.3.

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. Skip table  

Checkpoint

How the Checkpoint is addressed

7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. Accomplished where possible.
7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). Accomplished.
7.3 Until user agents allow users to freeze moving content, avoid movement in pages. Accomplished with the exception of the Twitter widget, which displays scrolling text.
7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. Accomplished.
7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. Accomplished.

Guideline 8 — Ensure direct accessibility of embedded user interfaces

Ensure that the user interface follows principles of accessible design: device-independent access to functionality, keyboard operability, self-voicing, etc. Skip table  

Checkpoint

How the Checkpoint is addressed

8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.

The main navbar is accessible to all browsers using the keyboard — normally Tab, Shift+Tab and Enter — but if a different device is used for equivalent commands, they'll work just the same as they normally would.

For graphical browsers which support focus-event handling, and also for serial and legacy browsers, the whole navbar and menu structure is accessible using the keyboard.

The existing keyboard functionality of screenreaders and other assistive devices will not, according to the provider, be affected by the menu script's keyboard handlers — an external device will take precedence and override the script.

Guideline 9 — Design for device-independence.

Use features that enable activation of page elements via a variety of input devices. Skip table  

Checkpoint

How the Checkpoint is addressed

9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Not applicable.
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. This is the same as 8.1.
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. This is the same as 6.4.
9.4 Create a logical tab order through links, form controls, and objects. Accomplished.
9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. Accomplished where applicable.

Guideline 10 — Use interim solutions

Use interim accessibility solutions so that assistive technologies and older browsers will operate correctly. Skip table  

Checkpoint

How the Checkpoint is addressed

10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. Accomplished. The only exception is outside the control of web programming, and has to do with the handling of the PDF and Microsoft Word files.
10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly is properly positioned. Accomplished.
10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. Not applicable.
10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. Not applicable.
10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. Accomplished where applicable.

Guideline 11 — Use W3C technologies and guidelines

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. Skip table  

Checkpoint

How the Checkpoint is addressed

11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. All pages on this website validate to XHTML 1.0 Strict, and work within XHTML served as XML, and uses the latest DOM scripting techniques in browsers that support them.
11.2 Avoid deprecated features of W3C technologies. Accomplished.
11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) Not applicable.
11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. Not applicable.

Guideline 12 — Provide context and orientation information

Provide context and orientation information to help users understand complex pages or elements. Skip table  

Checkpoint

How the Checkpoint is addressed

12.1 Title each frame to facilitate frame identification and navigation. Not applicable.
12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. Not applicable.
12.3 Divide large blocks of information into more manageable groups where natural and appropriate. Accomplished.
12.4 Associate labels explicitly with their controls. Accomplished where applicable.

Guideline 13 — Provide clear navigation mechanisms

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. Skip table  

Checkpoint

How the Checkpoint is addressed

13.1 Clearly identify the target of each link. Accomplished.
13.2 Provide metadata to add semantic information to pages and sites. Accomplished.
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). Accomplished.
13.4 Use navigation mechanisms in a consistent manner. Accomplished.
13.5 Provide navigation bars to highlight and give access to the navigation mechanism. Accomplished.
13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. Accomplished.
13.7 If search functions are provided, enable different types of searches for different skill levels and preferences. Not applicable.
13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc. Accomplished.
13.9 Provide information about document collections (i.e., documents comprising multiple pages). Not applicable.
13.10 Provide a means to skip over multi-line ASCII art. Not applicable.

Guideline 14 — Ensure that documents are clear and simple

Ensure that documents are clear and simple so they may be more easily understood. Skip table  

Checkpoint

How the Checkpoint is addressed

14.1 Use the clearest and simplest language appropriate for a site's content. Accomplished.
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. Accomplished where applicable.
14.3 Create a style of presentation that is consistent across pages. Accomplished.

Inner Divinity:

Crafting Your Life
With Sacred Intelligence

Testimonials

  • Spirit really shines through you. You're luminous.

    — W.C., Durham NC —

Mara Bishop

M.S. Energy Medicine
Master of Theology, C.S.C.

 

Copyright © 1996-2017 WholeSpirit. All Rights Reserved. | Valid XHTML 1.0 Strict | Valid CSS 3


        WholeSpirit on Facebook   WholeSpirit on Twitter