01243 512225

Web Accessibility

Coaching 2 Inspire cares about accessibility which is why we have chosen a web company that has web accessibility at its heart, and have had accessibility training ourself to make sure all people who visit our website can enjoy our website.

This page explains the accessibility features on this website.

  • For more in-depth information please see the accessibility guide on our original designers site access-bydesign.com
  • Please note: area designed by ourselves or our original designers meet all WC3 web standards and validate to the document type. Unfortunately the “quote rotator” and “mailing list” widgets are by third parties and fail web standards. We have written to these developers asking them to adopt accessible design but apologise that this is beyond our control.

Checklist of Checkpoints for How Coaching 2 Imspire meets Web Content Accessibility Guidelines 1.0

(Priority 1 (a) Minimum legal requirement
Our website:

  • Provides a text equivalent for every non-text element (e.g., via “alt”, “longdesc”, or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
  • Ensures that all information conveyed with color is also available without color, for example from context or markup.
  • Clearly identifies changes in the natural language of a document’s text and any text equivalents (e.g., captions).
  • Organizesdocuments 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.
  • Ensures that equivalents for dynamic content are updated when the dynamic content changes.
  • Avoids causing the screen to flicker.
  • Uses the clearest and simplest language appropriate for a site’s content.
  • We do not use image maps
  • We never use tables for layout
  • We never use tables for layout
  • We never use Frames on our websites
  • We do not use applets
  • If our website use scripts (Priority 1) we;
    • 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.
  • We do not use multimedia

Priority 2 (AA) checkpoints – good practice

Our website;

  • ensures that foreground and background colour combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen by providing a separate CSS style.
  • When an appropriate markup language exists, use markup rather than images to convey information.
  • Creates documents that validate to published formal grammars  (not including third-party elements).
  • Uses style sheets to control layout and presentation.
  • Uses relative rather than absolute units in markup language attribute values and style sheet property values.
  • Usse header elements to convey document structure and use them according to specification.
  • Marks up lists and list items properly.
  • Marks up quotations. Do not use quotation markup for formatting effects such as indentation.
  • Ensures that dynamic content is accessible or provide an alternative presentation or page.
  • avoids causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).
  • does not create periodically auto-refreshing pages beyond the fron “splash” page (which only redirects, rather than auto refreshes)
  • We do  use markup to redirect one page automatically (splash page) but this is not used anywhere else and instead, we configure the server to perform redirects wherever necessary
  • don’t not cause pop-ups or other windows to appear and do not change the current window without informing the user.
  • Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
  • Avoids deprecated features of W3C technologies.
  • Divides large blocks of information into more manageable groups where natural and appropriate.
  • Does not clearly identify the target of each link as it written in strict xhtml which does not “allow” targets
  • Provides metadata to add semantic information to pages and sites.
  • Provides information about the general layout of a site (e.g., a site map or table of contents).
  • Use navigation mechanisms in a consistent manner
  • We never use tables for layout
  • We do not use frames (Priority 2)When we use forms (Priority 2) we:
    • ensure that the label is properly positioned*
    • Associate labels explicitly with their controls.
  • We do not use use applets
  • If we use scripts (Priority 2) we;
    • ensure that event handlers are input device-independent.
    • avoid movement in pages.
    • Make programmatic elements directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]
    • Ensure that any element that has its own interface can be operated in a device-independent manner.
    • specify logical event handlers rather than device-dependent event handlers.

Priority 3 (AAA) checkpoints – best practice

Our website;

  • Specify the expansion of each abbreviation or acronym in a document where it first occurs.
  • Identifies the primary natural language of a document.
  • Creates a logical tab order through links, form controls, and objects.
  • Do not Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. (please see the access-bydesign website for why we do not follow this priority)
  • Includes non-link, printable characters (surrounded by spaces) between adjacent links.
  • Provide sinformation so that users may receive documents according to their preferences (e.g., language, content type, etc.)
  • Provides navigation bars to highlight and give access to the navigation mechanism.
  • Groups related links, identify the group and provide a way to bypass the group.
  • We enable different types of searches for different skill levels and preferences.
  • Places distinguishing information at the beginning of headings, paragraphs, lists, etc.
  • Provides information about document collections (i.e., documents comprising multiple pages.).
  • Does not use multi-line ASCII art.
  • Supplements text with graphic or auditory presentations where they will facilitate comprehension of the page.
  • Create sa style of presentation that is consistent across pages.
  • Does not use image maps
  • We do not use tables for layou
  • We include default, place-holding characters in edit boxes and text areas.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Sign up for our mailing list.