Accessible for all

Accessibility

Accessibility Statements

As stated earlier, accessibility statements are typically useless. Anyone can put an image or text claiming conformance to any level of the WAI WCAG1.0 that they wish.

In this section we will explain the reasons why we make the claim that we do.

Top of page

Statement of priority 1 conformance
1.1 Provide 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.

All images and other non-textual elements on this site that have meaning are backed up with useful alt and title tags. The image section of this requirement is a fairly easy check. Simply disable the images in your browser and you should still be able to see all important information and the site should still be 100% usable.

2.1 Ensure that all information conveyed with colour is also available without colour, for example from context or markup.

Anything on the site that uses a colour (for example the links are a different colour to the main text and when activated or the cursor is placed over them they change colour), also has added indicators that they have special meaning. Links (except for the main menu), become underlined, examples generally have a box surrounding them.

For the main menu not having the underline effect, it has a contrast change at the top of the link and there is a secondary, redundant menu with the same options at the bottom of the page which does have the underline.

4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).

The page headers include a command stating that the language used is British English. The main html tags that create the page also have the language specified. There are also meta information tags which specify the language being used.

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.

This is an extremely easy one to check. Simply turn off style sheet support in your browser. The page is designed and coded in a manner which reads perfectly well running down the page. We even include horizontal breaks to divide the information sections when the page is viewed in this manner.

6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.

Most of this site is completely dynamic. What this means is the information is not actually hard coded anywhere and the site accesses a database to pull information from, which is then used in various places.

Nothing on this site needs an alternate version (or equivalent) as the dynamic content runs the entire site and is always live.

7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.

The only animated image on the site is a loading image which is shown for the few seconds it takes the large site images to show, this neither blinks or flashes but fades in a rotating fashion. No content flashes, blinks or flickers. The only exception someone may make to this, is running through links quickly in which case we see that as the users choice and under their control.

14.1 Use the clearest and simplest language appropriate for a site's content.

The language used on this site is British English. In places where acronyms, abbreviations or code fragments are used, they are the simplest possible for the topic.

1.2 Provide redundant text links for each active region of a server-side image map.

No image maps of any sort are used on this site.

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.

No image maps of any sort are used on this site.

5.1 For data tables, identify row and column headers.

No tables are used on the site presently.

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.

No tables are used on the site presently.

12.1 Title each frame to facilitate frame identification and navigation.

We will never use frames on our site.

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.

The only thing falling under this category is the javascript that is used to show pictures of sites we have written, without changing the page. If javascript is turned off or not supported the images are simply loaded as if normally linked to.

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.

No multimedia presentations are used on this site.

1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.

No multimedia presentations are used on this site.

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.

This site meets all priority 1 checkpoints.

Top of page

Statement of priority 2 conformance
2.2 Ensure that foreground and background colour combinations provide sufficient contrast when viewed by someone having colour deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text].

All images and text meet (and in many cases exceed) this requirement. In fact we have chosen colours based on the WCAG2.0 contrast criteria.

An easy check for this one is to use the grey scale test at the GreyBit website (bare in mind this is not infallible as can be seen by the main link transparent backgrounds appearing gray instead of the black it actually is).

3.1 When an appropriate markup language exists, use markup rather than images to convey information.

Images are only used on this site for a few reasons. Aesthetic appeal (the curved corners and such set as background images through the style sheet), links (the folders and compliance icons), previous sites (so we can show how they looked when released) and a loading image for when the large versions of the previous site images are being displayed. No images are used for any other place where textual markup is more appropriate.

3.2 Create documents that validate to published formal grammars.

All pages on this site are written and validate to the XHTML1.1 standard as defined by the W3C. For user agents (browsers) that do not support this language specification properly (such as Internet Explorer), we drop this standard back to XHTML1.0 Strict.

The main style sheets used for layout and aesthetics validate at the W3C CSS3 level. The reason we went for this rather than CSS2.1 is the opacity instruction, allowing us to alter the transparency of the link icons and images, giving another visual aid for when these are being selected. If this level of support is not available, the standard falls back to CSS2.1 and the images become standard image links as seen on any other website.

The javascript code is clean and contains no errors.

3.3 Use style sheets to control layout and presentation.

External style sheets are the only method controlling layout and visual presentation.

3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.

All sizes that are not used for aesthetic spacing are given in em's. Although not an abbreviation or acronym, an em is actually the height of a capital 'M' in the font that is being used. This is what is known as a relative size because it equates to the current font, and font size as dictated by the user.

3.5 Use header elements to convey document structure and use them according to specification.

Header elements are the h1 through to h6 elements used in web pages. The headings used on this site are logical in document structure and are used as dictated by the specifications. This can be seen by using the W3C's Semantic Data Extractor and looking at the 'Outline of the document' near the bottom of the page.

3.6 Mark up lists and list items properly.

This site makes use of the following list types. ul lists are used for basic lists, ol are used for lists with a logical order and dl are used for lists of definitions or to define something where a list is the best way of presenting the information.

For example, the websites in the portfolio page use a dl list to specify the different pieces of the website details. The definition title being the company name, the definition descriptions being the image, the portfolio entry and the case study.

3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

Quotations are used on this site in their proper context. In the page headers will be quotations either of our tag lines or extracts from client testimonials. In other places, quotations are marked up as appropriate.

6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.

As stated in the priority 1 checkpoints, this site is comprised of completely dynamic content. It is all accessible.

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).

As stated in the priority 1 checkpoints, this site contains no blinking elements or content that is not user controlled.

7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.

No pages on this site refresh themselves. The user is in complete control.

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.

No pages redirect through html methods. In places where a redirect is necessary (the thank you page after submitting the contact form for example), the redirect happens transparently on the server.

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.

This site does not spawn any windows. Any links followed will open within the same window as is currently being used to view the site.

11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.

As stated in the priority 1 checkpoints, this site uses XHTML1.1 as a default and XHTML1.0 Strict for non-supporting user agents (browsers). The style sheets are CSS3 for the opacity instruction but otherwise are CSS2.1.

11.2 Avoid deprecated features of W3C technologies.

No code or technologies used on the site have been deprecated.

12.3 Divide large blocks of information into more manageable groups where natural and appropriate.

Large pieces of information on this site (for example this page), are broken up into the smallest logical natural blocks with links back to the top of the page placed between them.

13.1 Clearly identify the target of each link.

Every link on the site is clearly identified as to the subject matter of the link. Also the site makes use of link title's to further explain where the link is going.

13.2 Provide metadata to add semantic information to pages and sites.

Meta data is supplied in the header section of all pages in the form of meta and other tags. This information conveys author, descriptions, language, content type, instructions for robots and placement in collections of documents if applicable.

13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).

The site map is linked to at the top of the main content area (the second link in the tab sequence), on every page of the site.

13.4 Use navigation mechanisms in a consistent manner.

The navigation methods employed by the site are the same for every page. The content/help and main navigation menus are always in the same place on the screen. The redundant backup main navigation is always at the bottom of the page and are the first found when navigating backwards through the tab order. The secondary navigation options are always at the top of the main content area and the third level navigation is in a separated section below the secondary (this is referring to the default style sheet being used).

5.3 Do not use tables for layout unless the table makes sense when linearised. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearised version).

Tables are not currently used on this site and never will be for layout purposes.

5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.

Tables are not currently used on this site and never will be for layout purposes.

12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.

As stated in the priority 1 checkpoints, frames are not and never will be used on this site.

10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.

Form controls are positioned immediately adjacent to their respective labels.

12.4 Associate labels explicitly with their controls.

Form labels are always explicitly associated with their controls by way of the for attribute.

6.4 For scripts and applets, ensure that event handlers are input device-independent.

The script used to show enlarged images of sites from the portfolio is controllable (can be exited) by way of a click, key press or changing focus.

7.3 Until user agents allow users to freeze moving content, avoid movement in pages.

Nothing moves on any page on the site once it is loaded.

8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]

The script used to show enlarged images of sites from the portfolio is controllable (can be exited) by way of pressing any key or changing focus.

9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.

No elements have interfaces outside that of the html and user agent (browser) itself.

9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.

The script used to show enlarged images of sites from the portfolio is controlled (can be exited) with, onclick and onkeypress event handlers, and using the onblur event handler. Moving focus from the image link closes the enlarged image overlay.

Top of page

Statement of priority 3 conformance
4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs.

abbr tags are used for all abbreviations and acronyms on the site. The reason for using just the one is the difficulty in deciding whether something is in fact an abbreviation or an acronym.

4.3 Identify the primary natural language of a document.

As stated in the priority 1 checkpoints, the language is identified in the page header details, the html element and the header meta information.

9.4 Create a logical tab order through links, form controls, and objects.

The tab order is logical without needing to define it. The page is written exactly as it is used in a natural English, top to bottom, left to right order.

9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.

Main navigation and accessibility navigation options have numeric accesskeys set. This site does not employ alphabetical accesskeys as the majority of these will conflict with other programs including the actual user agent (browser) being used to access the site.

10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.

All adjacent links are in lists.

11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)

The language, content-type and other document identifying information are provided in both the page headers and the head area of each page.

13.5 Provide navigation bars to highlight and give access to the navigation mechanism.

The three main navigation areas (the help navigation, the main navigation and the redundant main navigation), are all in the same places and clear to see and use.

13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.

The three main navigation areas (the help navigation, the main navigation and the redundant main navigation), are all in the same places and marked up as lists. There is also a skip to content as the very first link on every page.

The content itself sometimes has further navigation lists and these can be skipped over by way of the first link in each of the navigation lists that goes to the section immediately following.

13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.

Currently there is no search functionality for the site.

13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.

Distinguishing headers are used throughout the site.

13.9 Provide information about document collections (i.e., documents comprising multiple pages.).

Multiple pages which follow on from each other have prev and next, link elements in the page head section.

13.10 Provide a means to skip over multi-line ASCII art.

There is no ASCII art present on the site.

14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.

Portfolio entries contain images of past sites as well as descriptions of what technologies were used and descriptions of actions taken.

14.3 Create a style of presentation that is consistent across pages.

Site presentation is the same throughout the entire site. An external style sheet maintains the design.

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.

There are no image maps present on the site.

5.5 Provide summaries for tables.

No tables are used on the site presently.

5.6 Provide abbreviations for header labels.

No tables are used on the site presently.

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.

No tables are used on the site presently.

10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.

All forms on the site use place holding hint text.

Top of page