Creating accessible web content ensures that all visitors—including screen reader users, keyboard-only navigators, and individuals with visual or cognitive impairments—can easily comprehend, navigate, and interact with web pages. Because content management systems and publishing workflows often introduce formatting inconsistencies, adhering to semantic HTML standards is essential for a seamless user experience. You can review the official HCU Page Building Guidelines for complete institutional publishing standards.
How to create accessible web content
Preliminary considerations for accessible web content
Before publishing web pages or editing content in the CMS, keep these foundational principles in mind:
- Avoid Importing Junk Code: Never copy content directly from online applications like Microsoft Word documents in SharePoint/OneDrive, Google Docs, artificial intelligence (AI), or HCU newsletters (Encompass/Slate), as these carry hidden junk code and broken tracking links. Always download files locally before copying to the website.
- Prioritize Semantic HTML: Always use proper semantic tags (headings, lists, blockquotes) for their intended structural purpose rather than relying on visual styling or font sizing to simulate structure.
- Leverage Automated Sanitization: The HCU content sanitizer automatically corrects common formatting errors upon saving—such as normalizing headings, fixing broken URLs, and enforcing font variables—but editors must still build clean content from the start.
- Keep Code Clean and Lightweight: Avoid embedding unnecessary inline styles or complex nested HTML structures that can disrupt screen reader parsing and slow page rendering. Prompt AI to remove all custom classes and HTML attributes when requesting generated content in code format.
In addition to following the Basic Content Accessibility Guidelines, keep reading below for specific web accessibility guidelines.
Accessibility guidelines for websites
Guidelines for accessible web content reflect general content guidelines, but the instructions for applying these recommendations are unique to publishing platforms, semantic markup, and automated content sanitization.
In this page:
- Headings & Structure
- Highlights & Emphasis
- Links & Buttons
- Images & Video
- Tables & Lists
- Color & Contrast
- Web Forms
1. Headings & Structure
Headings provide the foundational outline that screen reader users rely on to skim and navigate web pages efficiently. Refer to the HCU Page Building Guidelines for official heading case and case-sensitivity rules.
- Maintain a single H1 per page: Reserve the <h1> tag exclusively for the main page title (generated automatically by the CMS).
- Follow a strict numerical hierarchy: Progress sequentially from <h2> down to <h6> without skipping levels for visual styling. (Use Heading Styles when you need to style text like headings.)
- Avoid empty or whitespace-only headings: Never create blank heading tags used purely for spacing.
Learn more about Title and Headings Basics and Headings & Document Outline.
<h1> tags to <h2>, strips empty heading tags, and safely unwrap or reposition images trapped inside heading tags.2. Highlights & Emphasis
Proper styling and typographic emphasis ensure that critical text elements are correctly interpreted by assistive technologies.
- Use semantic emphasis tags: Apply <strong> for important text and <em> for stressed italics rather than relying on raw font styling.
- Never use underscores for emphasis: Underscores should never be used on web pages because they visually imply the presence of a clickable hyperlink. Use bold or italics instead.
- Avoid bolding or italicizing entire paragraphs: Limit emphasis to key words, phrases, or occasional sentences to maintain readability.
Learn more about Readability Basics and Typography & Readability.
3. Links & Buttons
Clear, descriptive links and interactive elements enable users to navigate with confidence across internal and external resources.
- Write descriptive link text: Make hyperlink text explicit about its destination (e.g., “Read the HCU Page Building Guidelines” instead of “Click Here”).
- Distinguish external links and PDFs: Ensure links pointing outside
hc.eduor to PDF documents clearly indicate they open in a new window. - Link contact information properly: Format email addresses as
mailto:links and phone numbers using hyphens (e.g.,tel:281-649-3000) rather than periods for screen reader compatibility.
Learn more about Link Basics and Writing Helpful Links.
http:// to https://, stripping www., and correcting hcu[sic].edu to hc.edu), adds target="_blank" to external and PDF links, and auto-linkifies email addresses and phone numbers.4. Images & Video
Visual content must be accompanied by appropriate alternative text and structured descriptions so all users receive the full message.
- Provide descriptive alt text: Describe informative images concisely so screen readers can convey their meaning.
- Mark decorative images correctly: Use empty alt attributes (
alt="") for purely visual dividers or background graphics. - Avoid text on banner images: Do not use banner images that contain embedded text. Rely on the default site template title overlay, ensuring text remains accessible and legible.
- Never post flyers or QR codes: Avoid uploading flattened flyers or QR codes as primary content without accompanying HTML text.
Learn more about Images & Alt Text , Video Captions, and Providing Descriptions for Video.
5. Tables & Lists
Data tables and structured lists organize complex information in a predictable format for screen readers and visual scanners.
- Use semantic list markup: Format related items using native unordered (<ul>) or ordered (<ol>) lists.
- Define table headers explicitly: Use the editor’s table tool to add <th> tags with appropriate scope attributes for tabular data, and avoid using tables for layout design.
Learn more about Table Basics, Accessible Tables, and Lists & Semantic Structure.
6. Color & Contrast
Consistent color application and high contrast standards ensure readability across all devices and lighting conditions.
- Meet contrast minimums: Maintain at least a 4.5:1 contrast ratio for normal text and 3:1 for large text and UI components.
- Adhere to HCU brand standards: Utilize approved color palettes and typography tokens for consistent institutional branding.
- Use the WebAim Color Contrast Checker to test your colors.
Learn more about Color Basics and Color Contrast & Meaning.
7. Web Forms
Interactive web forms require precise labelling, keyboard support, and clear error handling to ensure barrier-free submissions.
- Use Simple Text Inputs: Avoid date picker dropdowns and extensive select/dropdown menus that require a lot of scrolling. Instead, use simple text input fields.
- Explicit Labels & Grouping: Every input field, checkbox, radio button, and dropdown must have a programmatically associated
<label>(oraria-labelwhen visually hidden). Wrap related options—like radio buttons or checkboxes—inside a<fieldset>with a descriptive<legend>so screen readers announce the overarching question. - Persistent Helper Text & Placeholders: Never use placeholder text as a substitute for a permanent label, as it disappears when typing and often lacks contrast. Place instructions and expected formatting (such as
MM/DD/YYYY) in persistently visible helper text. - Keyboard Navigation & Focus Order: Ensure the HTML DOM order matches the visual top-to-bottom, left-to-right flow of the form. Maintain clear, high-contrast focus indicators on all active elements and avoid using positive
tabindexvalues. - Clear Error Identification: Do not rely on color alone to flag errors. Provide descriptive, text-based error messages and link them directly to the invalid field using
aria-describedbyso screen readers announce the issue upon focus. - Descriptive Actions & Target Sizes: Use specific button labels (e.g., “Submit Application” instead of “Submit”) and include accessible text for icon-only buttons. Ensure all interactive controls have a minimum clickable target area of 44×44 pixels.
- No Unexpected Timeouts: Avoid automatic session timeouts unless strictly necessary for security; if required, provide users with a clear option to extend their time.
Learn more about creating accessible forms.
Automated Media & Content Sanitization
The HCU WordPress environment includes an automated sanitizer plugin that runs upon saving posts, pages, ACF fields, and media uploads. While content editors should follow accessibility rules proactively, this system automatically corrects common formatting errors and enforces institutional compliance.
Media Standards & Alt Text Enforcement
- Required Alt Text Notices: The media library scans attachments and flags images lacking alt text to ensure WCAG and SEO compliance.
- Upload Directory Restrictions: Non-media documents (such as PDFs and word files) are restricted from the standard media library and automatically redirected to the department’s File Manager publication folders.
- Default Link Settings: Automatically configures the default image “Link To” setting to “None” to prevent broken link wrapping.
Heading & Structure Corrections
- H1 Normalization: Automatically converts stray primary header elements down to secondary header levels to reserve the main heading exclusively for the page title.
- Empty Heading Deletion: Strips out empty or whitespace-only heading tags.
- Image Heading Clean-up: Unwraps and repositions images trapped inside heading elements into separate, accessible content rows.
Link & Contact Enhancements
- External & PDF Target Attributes: Automatically applies target-blank parameters to all external non-hc[sic].edu links and PDF documents.
- Smart Protocol Cleaning: Fixes URL typos by converting HTTP to HTTPS, removing extraneous www subdomains, and correcting hcu[sic].edu typos to hc[sic].edu.
- Automatic Linkification: Standardizes phone numbers with hyphenated formatting and converts raw email addresses and phone strings into active mailto and tel links.
Typography & Color Variable Enforcement
- Pixel-to-REM Conversion: Automatically converts rigid pixel font-size declarations into responsive rem units based on a 16px base.
- Brand Color Mapping: Replaces hardcoded hex color codes with official HCU CSS custom properties (such as blue and black variables) to maintain color compliance.
- Junk Code Stripping: Cleans up hidden markup artifacts, redundant classes, and inline styles left over from pasting out of Microsoft Word, Google Docs, or AI chat windows.
Table Standards & Formatting Fixes
- Responsive Table Cleaning: Strips non-percentage widths and all fixed height attributes from tables, table data cells, and headers to ensure full responsiveness.
- Editor Outline Removal: Automatically strips temporary visual editor outline styles used during drafting so they never save to the live page.
- Empty Cell Protection: Automatically fills empty table cells with “N/A” text nodes to prevent screen readers from breaking layout flow or skipping content.
- Decorative Image Roles: Automatically injects
role="presentation"into images with empty alt text attributes so screen readers correctly skip them.
Learn more about creating accessible content
Guidelines for Documents, Multimedia, Email, Canvas, Charts & Graphs, and Forms.