Single Page
Accessibility Guidelines Related to a Single Web Page
On a page-by-page basis, the following guidelines should be validated for accessibility compliance:
Content
Use plain language.
Make sure the Web site's content is clear, and easy to read in order to to ensure the reader understands as quickly and completely as possible.
WCAG Guidelines referenced:
Use markup to structure content.
Properly nested heading (<h1>, <h2>, <h3>,...) and paragraph (<p>) tags enable the Web site's content to be easily read. Use tables (<table>) for tabular data, lists (<ol>, <ul>) for list data, etc.
WCAG Guidelines referenced:
- Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
- 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
- 1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)
- Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.
- 2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA)
Links
- Provide link text for links. Link text that clearly and simply describes the destination the link takes the user to facilitates site navigation.
- Use link text that makes sense when read out of context. (i.e. "Continue reading the Super Foods article" instead of "Continue reading...")
- Within a page, links with the same link text must have the same destination.
- Warn the user if clicking a link initiates a change in the application context (i.e. clicking a PDF link opens a PDF file or clicking a link opens the linked page in a new window).
WCAG Guidelines referenced:
- Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.
- 2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
- Guideline 3.1 Readable: Make text content readable and understandable.
- Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways.
- 3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A)
3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)
Page Titling
All Web pages should have identifying page titles.
12 point font is a recommended size for clear, legible content.
WCAG Guidelines referenced:
- Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.
- 2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A)
Text Styling
Use a minimum Font size, CSS 100%, 12 points.
12 point font is a recommended size for clear, legible content.
WCAG Guidelines referenced:
Use standard, widely available fonts.
Standard fonts such as Verdana, Arial, and Times New Roman are recommended to ensure all content is readable for as many users as possible.
WCAG Guidelines referenced:
Use scalable, relative sizing (%) for fonts.
Font size units in percentage (%) and ems (em) are scalable and will adjust as a page is zoomed. The pixel (px) and point (pt) font units are considered absolute and cannot scale in size.
WCAG Guidelines referenced:
- Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background.
- 1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)