The Modelmaking Company is committed to providing our visitors and clients with a fully accessible website. The following information shows how the WAI and WC3 and DDA advice and guidelines have been implemented on our website. For more details or help in using accessible features please refer to our web designer site.
(NB xhtml and css valid only applies to xhtml and css written by access-bydesign)
Priority 1 checkpoints
The only exceptions to the following are when site mechanisms (e.g. plug-ins) to provide dynamic content is delivered by third-parties and outside our control. Our designers are working with all third-party providers to petition them to use accessible practices.
• Provides a text equivalent for every non-text element (e.g., via “alt”, “longdesc”, or in element content). Many of these will be hidden (via CSS) to general users but available for those using screen readers or by disabling
• Ensures that all information conveyed with colour is also available without colour,
• Organises documents so they may be read without style sheets.
• Ensures that equivalents for dynamic content are updated when the dynamic content
• Avoids causing the screen to flicker.
• Uses the clearest and simplest language appropriate for a site’s content.
• Provides redundant text links for each any active region of a server-side image maps
• Does not use tables
• Does not use frames
• Provides alternative content for Flash
• Provides alternative content for java scripted effect/actions
• Ensures that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provides equivalent information on an alternative accessible page.
• Provides a text description for video using [d] tag
• If, after best efforts, we cannot create an accessible page (usually because of a reliance on third-party technology) this website provides a link to an alternative page/option that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
Priority 2 checkpoints
• Has a multiple CSS options that 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.
• When an appropriate markup language exists, use markup rather than images to convey information.
• Creates documents that validate to published formal grammars.
• Uses style sheets to control layout and presentation.
• Uses relative rather than absolute units in markup language attribute values and style sheet property values*
• Uses header elements to convey document structure and use them according to specification.
• Marks up lists and list items properly.
• Does 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
• Does not create periodically auto-refreshing pages.
• Does not use markup to redirect pages automatically.
• Does not cause pop-ups or other windows to appear and do not change the current window without informing the user.
• Uses W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
• Avoids deprecated features of W3C technologies*
• Provides large blocks of information into more manageable groups where natural and appropriate.
• Provides metadata to add semantic information to pages and sites.
• Provides information about the general layout of a site (e.g., a site map)
• Uses navigation mechanisms in a consistent manner.
• All form controls have implicitly associated labels, and ensure labels are properly positioned *
• Associates labels explicitly with their controls*.
• Avoids movement in pages and/or provides static alternative
• Makes programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies
• Ensures that any element that has its own interface can be operated in a device-independent manner.*
• For scripts, specifies logical event handlers rather than device-dependent event handlers.*
Priority 3 checkpoints
• Specifies 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.
• Includes non-link, printable characters (surrounded by spaces) between adjacent links. Provides information 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 provides a way to bypass the group.
• Searches allow 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.).
• Provide a means to skip over graphical elements/non-information elements
• Supplements text with graphic or auditory presentations where they will facilitate comprehension of the page.
• Creates a style of presentation that is consistent across pages.
• Provides a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns by allowing CSS to be deactivated.
• Forms include default, place-holding characters in edit boxes and text areas.
*Unless mechanism (e.g. plug-ins) are delivered by a third-party provider out of our company or original designers control