State of Connecticut Web Site Accessibility Committee ConneCT - Your Key to Accessibility

Home | Policy | About | Status Reports | Meetings | Membership | Listserv | Resources | Tools | Tutorials | Forms | News | Search | Site Map


Proposal developed by the Accessibility Working Group

In addition to complying with the policy, the Accessibility Working Group also recommends that the following requirements be addressed as time and resources permit:

Design Requirement: 3.3 Use style sheets to control layout and presentation.

WCAG Guideline: 3

WCAG Checkpoint: 3.3

WCAG Priority: 2

WCAG Category: In General

Section 508 Standard: N/A

Suggested Language: 3.3 Use style sheets to control layout and presentation.

Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-style-sheets


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

WCAG Guideline: 3

WCAG Checkpoint: 3.4

WCAG Priority: 2

WCAG Category: In General

Section 508 Standard: N/A

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

Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-relative-units


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

WCAG Guideline: 3

WCAG Checkpoint: 3.7

WCAG Priority: 2

WCAG Category: In General

Section 508 Standard: N/A

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

Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-quotes


Design Requirement: 13. Avoid the use of HTML tags or extensions which are supported by only one browser.

WCAG Guideline: 11

WCAG Checkpoint: 11.1

WCAG Priority: 2

WCAG Category: In General

Section 508 Standard: N/A

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

Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-latest-w3c-specs


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

WCAG Guideline: 11

WCAG Checkpoint: 11.1

WCAG Priority: 2

WCAG Category: In General

Section 508 Standard: N/A

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

Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-latest-w3c-specs


Design Requirement: 13. Avoid the use of HTML tags or extensions which are supported by only one browser.

WCAG Guideline: 11

WCAG Checkpoint: 11.2

WCAG Priority: 2

WCAG Category: In General

Section 508 Standard: N/A

Suggested Language: 11.2 Avoid deprecated features of W3C technologies.

Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-avoid-deprecated


Design Requirement: 11.2 Avoid deprecated features of W3C technologies.

WCAG Guideline: 11

WCAG Checkpoint: 11.2

WCAG Priority: 2

WCAG Category: In General

Section 508 Standard: N/A

Suggested Language: 11.2 Avoid deprecated features of W3C technologies.

Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-avoid-deprecated


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

WCAG Guideline: 12

WCAG Checkpoint: 12.3

WCAG Priority: 2

WCAG Category: In General

Section 508 Standard: N/A

Suggested Language: 11.2 Avoid deprecated features of W3C technologies.

Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-group-information


 


HTML 4.01 - Follow this link to view the page validation results|Valid CSS - Follow this link to view the page validation results