Accessibility Statement
Accessibility Guidelines for Web Content Editors
The following guidelines help ensure that web content remains accessible and compliant.
Headings provide structure for screen readers and improve usability for all users.
- Use one H1 for the page title.
- Do not skip heading levels. For example, do not go from H1 directly to H4.
- Follow a logical structure:
- H1 followed by a paragraph
- H2 followed by a paragraph
- H3 followed by a paragraph
- Always include content within a paragraph tag immediately after a heading.
- Do not use bold text in place of a heading.
Proper formatting improves accessibility and readability.
- Use the CMS list tools to create ordered and unordered lists.
- Do not manually create lists using dashes, asterisks, or typed numbers.
- Do not use multiple line breaks to create spacing.
- Avoid excessive bold or italic styling for emphasis.
- Do not use all caps for emphasis.
- Acronyms may be capitalized, but always spell out the full term first, followed by the acronym in parentheses.
Example: Grossmont-Cuyamaca Community College District (GCCCD)
Links must clearly describe their destination, especially for screen reader users.
- Use clear, descriptive link text that explains the destination.
- Avoid vague phrases such as:
- “Click here”
- “Read more”
- “Sign up here.”
- Use the actual page or document title in the link text.
- Indicate file types when linking to documents.
Example: Download the Financial Aid Application (PDF)
Images must be accessible to users who rely on screen readers.
- Provide meaningful alt text for all informational images.
- Alt text should describe the purpose or content of the image.
- Decorative images should use empty alt text so screen readers ignore them.
- Do not include phrases such as “image of” unless necessary for context.
Content must be readable for users with low vision or color blindness.
- Ensure sufficient contrast between text and background colors.
- Do not use light gray text on a white background.
- Do not rely on color alone to convey meaning.
Example: Instead of saying “Items in red are required,” use “Required items are marked with an asterisk.”
Tables should only be used for presenting data.
- Do not use tables for layout purposes.
- Include column headers.
- Avoid merged or split cells when possible.
- Keep tables simple and easy to navigate.
Uploaded documents must also meet accessibility standards.
- Ensure PDFs and Word documents are accessible before uploading.
- Do not upload scanned image-only PDFs.
- Use proper headings and alt text within documents.
- Provide alternative formats when appropriate.
When embedding video or audio content:
- Ensure videos include accurate captions.
- Provide transcripts when appropriate.
- Avoid auto-playing media.
Accessibility includes cognitive and readability considerations.
- Use plain language whenever possible.
- Avoid jargon or explain it clearly.
- Break long paragraphs into shorter sections.
- Use headings to organize content logically.
Before publishing:
- Check heading structure.
- Confirm alt text is included.
- Verify links are descriptive.
- Review color contrast.
- Ensure uploaded documents are accessible.
Using an accessibility checklist and automated scanning tools can help identify issues prior to publication.
For detailed guidance on creating accessible web content, visit the official Section508.gov Web Content Development page.