Wittmeier Auto Center
Chico, California USA | (530) 895-8181

Our Commitment to Accessibility

Wittmeier Auto Center strives to make its products and services accessible to all users, including people with disabilities.

Web Standards

Web Standards are technologies, established by the World Wide Web Consortium and other standards bodies, that are used to create, interpret and display Web content. These technologies are designed to future-proof documents published on the Web and to make those documents accessible to as many people and devices as possible.

Wittmeier Auto Center embraces Web Standards and has built this website on a foundation of HTML driven by specialized Cascading Style Sheets (CSS) and JavaScript. These powerful tools deliver fully styled Web pages to a wide variety of browsers without the excessive markup typically required only a few short years ago.

The proper design and layout of this site is only visible in a graphical browser that supports these technologies. The content, however, is accessible to any modern browser or Internet device with JavaScript capability enabled.

Website Features

Current accessibility elements include:

  1. Alternative text detail for appropriate images and other non-text elements.
  2. Title attributes for additional information about critical links and images.
  3. Standard notation and style indicating all PDF files and their size.
  4. Structural markup to indicate headings and lists to aid in page comprehension and search engine optimization.
  5. Association of form fields with labels to improve usability for people using assistive devices such as screen readers.
  6. The association of Cascading Style Sheets (CSS) with the correct media type to enhance appearance and usability.
  7. If CSS technology is not available, proper structural markup ensures that the content will still be easily understood.

Usable, Scalable, Subtle and Fast

This website uses four strategies that ensure that those visitors with current Web browsers and broadband connections can enjoy the latest Web technologies, while those who prefer simpler software or slower connections can still have a pleasant, though less elegant, browsing experience.

1. Graceful Degradation

Graceful degradation begins with the principle that some parts of complex systems will fail, and then seeks to build in alternate paths that "degrade" to a lesser but still functional experience. The principles of graceful degradation, also known as "fault tolerance," long precede Web design. In fact, many early examples reference complex infrastructures such as the load balancing of electrical grids. A common Web example of graceful degradation is the <noscript> tag, an HTML element intended as a way to deliver content only to users without JavaScript support – it's a fallback alternative to the intended experience.

2. Progressive Enhancement

The core development principles of progressive enhancement are fundamentally different from graceful degradation. This approach assumes that all web-based systems can be reduced to a simple, functional experience captured in a single codebase that will "work" anywhere – that is, it will deliver a usable, functional and satisfying experience to the widest range of devices, browsers and platforms. Once the needs of the majority have been met in the simplest way, the robust enhancements that modern compliant browsers can handle are layered on "progressively" to build up to the complete experience.

3. Unobtrusive Scripting

Unobtrusive scripting (also known as unobtrusive JavaScript and unobtrusive DOM scripting) is a best practice in standards-based website development. The idea is simple: separate behavior from the other two layers of Web development (structure and presentation).

Unlike advertising pop-up windows and other in-your-face JavaScript gimmicks, unobtrusive scripting is subtle and user-focused. It is designed to enhance an already semantic and accessible markup structure, and to offer fallback alternatives if the browser or device does not support JavaScript.

An unobtrusive behavior, as defined by The Web Standards Project, draws as little attention to itself as possible. In doing so, it provides a number of benefits:

Usability
An effect created by an unobtrusive DOM (document object model) script does not draw the attention of the user. It is so obviously a good addition to the site that visitors just use it without thinking about it.
Graceful Degradation
Unobtrusive JavaScript does not draw the attention of its users when it fails. It never generates error messages, not even in old browsers. An unobtrusive script first asks "Does the browser support the objects I want to use?" If the answer is "No," the script silently quits.
Accessibility
The basic functionality of the page does not depend on the unobtrusive script. If the script doesn't work, the page still delivers its core functionality and content via HTML markup, CSS (cascading style sheets) and server-side scripting. The user rarely notices that something is not there.
Separation
An unobtrusive script does not draw the attention of Web developers working on other aspects of the site. All core JavaScript code is maintained separately, without littering files dedicated to XHTML, PHP, JSP, or other languages.

Source: The Web Standards Project
Source: Designing with Web Standards (3rd Edition) by Jeffrey Zeldman

4. Page Speed Optimization

The Wittmeier Auto Center website uses the following best practices to help Web pages load as fast as possible:

  1. Minimal HTTP requests
  2. Use of a content delivery network (CDN) when available
  3. Addition of an Expires header to the server's HTTP response
  4. Use of Gzip compression to reduce server response times
  5. Reference to external stylesheets (CSS) in the document head of each page
  6. Reference to external JavaScript files (at bottom of page when practical)
  7. Avoidance of CSS expressions
  8. Reduction of DNS lookups
  9. Use of minified JavaScript when practical
  10. Removal of ETags as a method of cache control
  11. Minimal use of the HTML <iframe> element
  12. Use of <link> instead of @import to load stylesheets
  13. Use of maximum image optimization when practical

For a discussion of these performance techniques and more see:

Compliance

This website is monitored and tested regularly to identify any usability issues as well as improve accessibility according to the following guidelines:

Recommended Web Browsers

If you are having problems viewing this site, or suspect that it is not displaying properly, you may want to upgrade to the latest version of a compliant Web browser:

† Recommended for an enhanced browsing experience.

Your Opinion Counts
As we continue to improve our website, any updates will be included on this page. If you have comments or questions, you can contact us directly.

Revised: 2012-03-07

Tools

Services

Resources »

Contact Us »

View current offers