About Accessibility and
Structure.
All of the content, except for the third party generated content of the
Machine Validation Audit, has passed machine validation for a Priority
3 classification. Most of the content is still under development and is
in various stages of human review to meet the Priority 3 classification.
Obviously, during construction phase, content will fluctuate between a
Priority 2 and a Priority 3 classification. Even after human review of
a completed content page that technically meets a Priority 3 classification
should never be interpreted that improvements cannot or should not be
made. This site, along with my working knowledge of effective and efficient
accessibility use is constantly being re–evaluated, updated and
improved upon.
A few of the issues that are in varied stages of process are improvements
in site navigation that include sidebar block navigation of categorical
content and bread–crumb navigation, better use of micro–formats
such as the hCard, integration of shortcut key values directly into the
various ASP.NET
site–map files, improvements achievable with migration to the
version 3.5 NET Framework, user ability to change layout and design
through use of selectable style sheets, etc.
The abbreviation of [ND], Non-Developed, are links that are not yet
currently active.
This is the policy that describes the purpose and mission of the Web
site's commitment to accessibility standards.
top of page
The Addendum lists any apparent discrepancies and issues that exist
within machine validation for accessibility and the standards. Explanations
and reasons are presented.
top of page
A full graphical presentation of the results of the Web site's
machine validation for accessibility compliance is available.
This site includes external links to accessibility compliance validation
Web sites. Cynthia Says has recently been updated so that it can
validate content that uses a custom Document Type Definition [DTD].
The majority of this Web site uses a custom DTD. For a more thorough
compliance machine validation of this content and one that can check
accessibility regardless of any custom DTD, use of the Watchfire WebXact
Web software application is recommended. However, the Watchfire online
service has been discontinued as of 01 February 2008. Watchfire was
recently purchased by International Business Machines.
NOTE: The Web pages that present the graphical and validation data were developed
by the validation software and are not standards compliant. I have not,
yet, taken the time to write the code that meets compliance for those
specific content pages.
top of page
The is a discussion of the hows, the methodologies and the methods
used within the Web site's internal structure and how it is presented to
the Web visitor.
top of page
Shortcut key navigation is listed within a table format.
top of page
The Web site uses a strict standard. Its use and benefits of its use
are discussed.
top of page
CSS validation and usefulness is described and how it is used within
the Web site.
top of page
A brief description of the major accessibility applications is
presented. Various accessibility resources are listed along with
links to assistive technology software for those in need.
top of page
Long description content pages are provided for images, multi-media,
graphs or any content that requires further text description or alternate
resources for interpretation.
Long description content is, also, provided for any table layout that
has been used. This type of content has been implemented to support
older assistive technologies that cannot efficiently render accessible
table design and layout.
top of page
If you have any questions regarding any issues or questions
concerning accessibility, please
e-Mail that boinkin guy.
End of the Accessibility and Structure Main Content.
.
If You Don't Own the Cattle, Don't Wear
the Damn Hat.
Yeah, but exceptions should always be allowed.
Keyboard Navigation and Web Content Usability.
Keyboard navigation of Web content is becoming of greater importance
as more content is accessed by mobile devices. It is not, solely, an
accessibility solution for those with disabilities. Proper structure of
content should allow for site navigation that is not limited to any
specific hardware or device, for example, mouse technologies.
Part of successful keyboard navigation is dependent upon the tab key
and being able to tab through links, form controls and, even, content
segments. Successful implementation of tab control through content cannot
depend upon any browser or user agent to successfully and automatically
assign proper tab order throughout any rendered content.
Designers and developers should assign tabindex values to
all necessary elements. Tab key values should follow the linear order of
the content. Linear order of the value should only be superceded by the
logical order of tab order, when necessary.
Keyboard Shortcuts and Navigation.
Another critical function of keyboard navigation is the use of
shortcut keys for important links and for major content segments. This
requires effective use of the accesskey value. This site
uses a modified version of the United Kingdom Standard of Keyboard
Shortcuts.
More thorough information about the use of the United Kingdom
Standard is available on this Web site's Keyboard
Shortcut
content page.
Keyboard Shortcut List.
- Shortcut Key, s.
- Skip to the Main Content.
- Shortcut Key, One.
- The Home Page.
- Shortcut Key, Two.
- The General Page Menu.
- Shortcut Key, Three.
- The Site Map.
- Shortcut Key, Four.
- The Accessibility Policy.
- Shortcut Key, Five.
- The Copyright Notice.
- Shortcut Key, Six.
- The Safety Policy.
- Shortcut Key, Seven.
- The Privacy Policy.
- Shortcut Key, Eight.
- The Terms of Use.
- Shortcut Key, Nine.
- The Contact Page.
- Shortcut Key, Zero.
- The Keyboard Shortcut Links Table.
- Shortcut Key, t.
- The Top of the Page.
- Shortcut Key, c.
- The Main Content Column.
- Shortcut Key, r.
- The Right Sidebar Column.