College of Education & Human Development
Web Accessibility
Our team not only builds and maintains websites and tools for the College, but also ensures that digital experiences are accessible and usable for everyone. This means enforcing WCAG Guidelines and embedding accessibility into every step of design and development.
Beginning April 2026, compliance with WCAG 2.1 AA standards will become a legal standard. We are working to ensure our sites meet those standards, and provide tools and resources for faculty and staff to also comply with these requirements.
If you have questions or want to speak to someone, email us at our shared mailbox cehdmarcom@tamu.edu.
Topics on this page
Headings
All pages must have only one H1 and it needs to be the first heading and reflect the title of the page or its content. Headings must be nested in order. All pages must end with an H2, H3 or lower heading — the headings in our footers are H3 headings.
Heading Rules
- One H1 per page (page title).
- Use H2 for major sections, H3 for subsections.
- Don’t skip levels (e.g., avoid H1 → H3).
- Headings should be meaningful, not used just for styling.
Visual Example
Images
All images that convey meaning must have descriptive alt text. If the image is broken or the user cannot see the image, do they need to know what it shows? You will need to use your judgement to make that determination, but here are some examples and guidelines to help you make that decision.
Images That Need Alt Text
Informative Images
Images that convey information not already given in text. Alt should briefly describe the content or meaning.
Examples
Photo of Research Team in the Field
alt=”Dr. Deanna Kennedy checks data with students on laptop.”
Headshot on a Profile
alt=”Portrait of Dr. Michael A. de Miranda, Dean of the College of Education & Human Development”
Graph Showing Enrollment Growth
alt=”Line chart showing student enrollment increasing from 2019 to 2025.”
Functional Images
Images that act as a link, button, or trigger an action. Alt text should describe the function, not the appearance.
Examples
Magnifying Glass Icon Used For Search
alt=”Search”
Social Media Icon That Links to Instagram
alt=”Follow us on Instagram”
Conceptual or Educational Graphics
Images that explain a concept, like diagrams, infographics, or process illustrations. Alt text should summarize the key takeaway.
Examples
Flowchart of Approval Process
alt=”Flowchart showing the three-step research approval process: application, review, and notification.”
A Venn diagram comparing two teaching models
alt=”Venn diagram showing overlap between project-based and experiential learning.”
Brand or Organizational Images That Convey Meaning
If your logo or mark is identifying an organization or purpose, it needs alt text. Alt text should state the organization name or function.
Examples
College of Education & Human Development Logo
alt=”College of Education and Human Development at Texas A&M University”
Images Showing a Specific Person, Place, or Event
Alt text should identify who or what it depicts, if relevant to the context.
Examples
Specific Individual and Setting
alt=”Dr. Michael A. de Miranda, Dean of the College of Education and Human Development, speaks at the grand reopening celebration of the Marilyn Kent Byrne Student Success Center outside of Harrington Tower.”
Images That Should Not Have Alt Text
When an image does not need alt text, use an empty alt attribute — alt=””.
Use Empty Alt Attributes For:
- Purely decorative elements (e.g., background flourishes, divider lines)
- Stock images used only for visual appeal
- Repetitive or redundant logos when the same text appears nearby
- Icons with visible text labels (e.g., a phone icon next to “Call Us”)
Color Contrast
Normal-sized text requires a color contrast ratio of at least 4.5:1 to be compliant, while large text — 18pt (bold) or 24pt and larger at normal font-weight — requires a minimum ratio of 3:1.
Brand Color Contrast Checker
Text
#500000
Good Contrast
Background
#ffffff
Contrast ratio: 12.63:1
✓ Good Contrast
Video
Video content must be accessible to all users, including those who rely on captions, transcripts, or assistive technology. The following guidelines outline the core requirements for publishing video on CEHD websites and channels.
Captions and Transcripts
- All videos must include accurate captions. Auto-generated captions in YouTube are a starting point, but review and correct them before publishing.
- Provide a written transcript or short summary directly on the page when possible.
- Follow official YouTube instructions for adding captions: Add subtitles and captions in YouTube.
On-Screen Text and Visuals
- Ensure on-screen text is large, high-contrast, and visible long enough for viewers to read comfortably.
- Avoid flashing or strobing content that exceeds three flashes per second.
Playback and Controls
- Never use autoplay—users must be in control of playback.
- For looping or background videos, include pause/play controls that are keyboard accessible.
- Provide a short text summary describing the visual content if it contributes meaningfully to the page.
YouTube Upload Best Practices
- Use a descriptive title and detailed video description to improve accessibility and search visibility.
- Choose high-contrast thumbnails and avoid text-heavy graphics.
- Ensure captions are enabled and verified before embedding videos on CEHD websites.
Buttons and Links
Links and Descriptive Text
- Use descriptive link text that clearly communicates what the user will find when the link is activated.
- Avoid vague phrases like
Click here
,Learn more
, orRead more
—they provide no context for users navigating with screen readers or by keyboard. - When possible, embed the link naturally into meaningful words within the sentence. For example: “Explore our scholarship opportunities for first-generation students.”
- If a link’s purpose is self-evident (for example, a labeled button or navigation item), additional wording is not necessary.
- For multiple links with the same visible text, ensure each link’s destination is unique or add an
aria-labelto clarify context for assistive technology.
Documents and PDFs
Whenever possible, we recommend publishing content directly on a web page instead of as a PDF. Web content is easier to keep accessible, mobile-friendly, and up to date.
If there are specific reasons a PDF format is preferred (for example, printing requirements or layout considerations), please let us know. In many cases, we can replicate the same content on a web page while still meeting those needs.
When a PDF is necessary, ensure that:
- The source file (e.g., Word, PowerPoint, Canvas, InDesign) is built to meet accessibility standards before exporting.
- The exported PDF is then checked for accessibility in Adobe Acrobat using the built-in Accessibility Checker.
If a PDF is required, start by making the original document accessible (in Word, PowerPoint, or Canvas). Then use Adobe Acrobat’s Accessibility Checker to verify the exported PDF meets standards.