Content Standard

Texas State must use create content that adheres to the Web Content Accessibility Guidelines (WCAG) 2.1 AA.

Accessibility Guides

Please refer to the Accessibility Basics for more in depth information. This page provides an exhausted “checklist” of requirements, but more granular information can be found in each unique guide.

Creating Page Structure

Use the built-in Heading styles.

  • Use the Format/Styles dropdown to apply:
    • Heading 1 (H1) – Page title
    • Heading 2 (H2) – Main sections
    • Heading 3 (H3) – Subsections
  • Do NOT:
    • Change font size to “look like” a heading.
    • Bold text to create section titles.
    • Skip heading levels (H2 → H4).

Use proper lists.

  • Use the bullet or numbered list buttons.
  • Do not type dashes or numbers manually.

Use tables correctly.

  • Only use tables for data.
  • Use the table header option for column headers.
  • Do not use tables to control layout.

Adding Links

Write meaningful link text. When inserting a link:

Do NOT write:

  • Click here
  • Read more
  • More info

Instead write:

  • View Financial Aid Deadlines
  • Download the 2026 Course Catalog (PDF)

Make links clear out of context. If someone only hears the link text, it should still make sense.

When linking to a document:

  • Add (PDF), (Word), etc.
  • Example: Employee Benefits Guide (PDF)

Consult the course Accessible Link Text at Texas State for additional information.

Uploading and Inserting Images

When adding images through the Media Library:

Always complete the “Alt Text” field. Alt text should:

  • Describe the meaning of the image.
  • Be short and clear.
  • Not say “image of.”

Decorative images

If the image is purely decorative:

  • Leave alt text blank (if CMS allows), or
  • Mark as decorative.
  • Gato does not currently provide a way to mark decorative images but other CMS may have this functionality.

Do not upload flyers as images.

If information is important:

  • Put the text directly on the page.
  • Do not upload a JPG or PNG of a flyer instead of real text.

Adding Buttons

When creating buttons the text must describe the action.

Good:

  • Apply Now
  • Submit Application
  • View Program Details

Bad:

  • Click Here
  • More

Choosing Text and Background Colors

Use approved color styles only and ensure text meets the following requirements:

  • Normal text meets or exceeds 4.5:1 contrast ratio.
  • Large or bolded text meets or exceed 3:1 contrast ratio.
  • Do not manually choose custom light colors.
  • Do not override theme colors.

Do not rely on color alone to communicate meaning.

Instead of:
“Courses in red are full.”

Write:
“Courses marked ‘Full’ are no longer available.”

Embedding Video

  • Confirm captions exist.
    • YouTube/Vimeo auto-captions must be reviewed.
    • Do not publish videos without captions.
  • Do not enable autoplay.
  • Provide transcripts for audio-only content.

Uploading PDFs and Documents

Before uploading:

  • Confirm the document is accessible.
    • Proper headings used.
    • Tagged PDF (not scanned).
    • Alt text for images inside document.
    • Selectable text (not a picture of text).
  • If possible, create a web page instead of uploading a PDF.

Creating Forms (If CMS Allows Form Building)

  • Every field must have a visible label.
  • Required fields must be clearly marked.
  • Error messages must explain how to fix the issue.
  • Do not rely only on red highlighting for errors.

Checking Before Publishing

Before clicking “Publish”:

  • Headings are structured correctly
  • Links are descriptive
  • Images include alt text
  • No flyer images used instead of text
  • Videos have captions
  • PDFs are accessible
  • No “click here” links
  • Content is clear and readable
  • Page works when using only the Tab key

Things CMS Editors Should NOT Do

  • Do not paste content directly from Word without cleaning formatting.
  • Do not manually change font sizes.
  • Do not override theme styling.
  • Do not upload scanned documents.
  • Do not create blinking or moving text.

When to Ask for Help

Contact the EIRAC if:

  • You are unsure how to write alt text.
  • You need help making a PDF accessible.
  • You suspect a template issue.
  • You are embedding third-party tools.
  • You receive an accessibility complaint.