• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
UT Shield
College of Fine Arts Web instruction
  • Welcome
  • About Us
    • WordPress & Drupal
    • Websites & Content Owners
  • Getting Started
    • Learn Best Practices for Web
    • Vocabulary Terms
    • Do you need a website?
    • Ways to Get a Website
      • Website Options Comparison
      • Initiate a Project with the Web Team
      • Outsource or DIY
    • Know Your Audience
    • Navigation & Menu Items
  • Requirements
    • Americans with Disabilities Legal Obligations
      • Alternate Text
      • Use of Color & Contrast
      • Link Text & Appearance
        • Non-Visible Link Context
      • PDF Files
      • Software Plug-in Link
      • Captions, Audio Description & Transcripts
        • webVTT Caption File
        • Caption Using Amara
        • Writing Captions & Audio Description
        • Video & Remote Communications
      • Additional ADA Issues
        • Accessible Social Media
        • Video & Remote Communications
    • UT Web Accessibility Policy
    • UT Web Privacy Policy
    • Records Retention – Backups, Archives and Revisions
    • College of Fine Arts Brand
    • UT Brand Guidelines
    • Information Security Office Policies
  • Best Practices
    • College of Fine Arts Communications Written Style Guide
    • Using a Rich Text Editor
      • Using an External HTML Editor
    • Links & URLs
      • Link Text & Appearance
        • Non-Visible Link Context
      • Absolute vs. Relative Paths
      • HTTP vs HTTPS
      • Anchor Links
      • Changing URLs
      • Shorten a URL for Marketing
    • Images
      • JPG vs PNG
      • Image Editing and Troubleshooting
    • Web Forms & Surveys
      • Create a Link to Pre-Filter a Web Form Page
    • Standards & Structure
      • Hierarchical Headers
      • Computer File Names
      • URL address names
        • UT Short Links Service
      • HTML
        • Common HTML Errors
        • Multiple Rows with Floated Images
        • Responsive Word Wrapping
    • Artificial Intelligence
    • Test & Evaluate
    • Wikipedia
    • Social Media & Networking
      • Accessible Social Media
    • RSS & Feeds
    • UT Austin Web Publishing Guidelines
  • Site Performance
    • Page Load Time
      • Fonts
    • Respond to a Variety of Devices
      • Telephone Numbers on Smart Phones
    • Analytics & Visitor Data
      • Outreach Campaign Link Tracking
        • Campaign URL Builder
        • Campaign Link Tracking Worksheet
    • Page Not Found Traffic
    • Tips to Increase Traffic
    • Optimize for AI Chat and Search
  • Site Specific Instructions
    • Instructions for COFA sites on University Blog Services WordPress
    • Instructions for COFA Drupal Kit sites
    • Instructions for COFA sites on UT Drupal Kit Managed

HTML

Last Updated December 2024

It’s a good idea to become familiar with some basic HTML code. Once you are familiar, we encourage you to inspect the code regularly. You’ll be surprised at what you can infer.

Common Tags

Headings – use for hierarchical structure of your content as titles and subtitles.
<h1> A Heading </h1>

Paragraphs
<p> Some text </p>

Links – learn how to write effective link text.
<a href=”about”> About </a>

Images – learn more about the required alt value.
<img src=”photo.jpg” alt=”descriptive text about the image” />

Common HTML Errors

You MUST Edit the HTML

There are some things that a Content Management Rich Text Editor just can’t do.

Acronyms and Abbreviations

Acronyms and abbreviations that aren’t coded properly will cause issues for people using assistive technologies. Learn to edit the HTML for acronyms and abbreviations.

Foreign Language

Assistive Technologies also don’t know what to do with foreign languages if not coded properly. Learn how to edit the HTML for foreign languages.

Telephone Numbers

Smartphones can call a telephone number with one click, if it’s coded correctly. Learn how to create telephone number links.

Rows of floated images

Create rows of content floated next to images, such as in an aggregated list of teasers, like news. Usually these kinds of layouts are set up to automatically generate but sometimes you may want to simulate the layout.

Word Break Opportunity

Handle long words within narrow columns. Especially an issue with responsive websites.

Troubleshooting

HTML consists of tags that wrap around your content and give instructions to the browser. Usually, the tags have a beginning and an end:

An opening tag is between less than and grater than signs: <tag>
An end tag has a / after the less than sign: </tag>
Your content goes between these two tags.

There are a few tags that do not have a closing tag, for example the image tag, example:
<img src=”path/to/file/image.jpg” />

Tags can have additional attributes. For example:
<tag attribute=”some_attribute”>

Sometimes, with content management systems, the rich text editor gets confused and nests tags in the wrong order, or people inadvertently erase a closing tag, or code pasted from an external source really makes things weird.

To make things even harder, some tags have special rules about the order they can be in or if they can be nested inside of other tags or not.

Block Vs. Inline Tags

There are block level tags that give instruction to the browser to start on a new line and take up the full available width of the screen. These include:
paragraph – <p>
horizontal rule – <hr />
headers – <h1> thru <h6>

There are inline level tags that only take up as much width as is necessary. These include:
emphasis – <em>
strong – <strong>
citation – <cite>

Example

The following code could be caused by putting the cursor within a block level element to start new content while in the Rich Text editor. Because the tags are not nested properly, the following code will cause the video to display over the top of the heading, in essence making it appear that the heading completely vanished:

<div class=”responsive-video”>
<hr />
<p>
<iframe title=”description of video” src=”https://player.vimeo.com/video/234518290″></iframe>
</p>
<h2>Title for this section</h2>
</div>

To fix the issue, the “responsive-video” div needs to end before the heading starts. No visible issues are caused by the horizontal rule tag being inside of the video tag content but logically it should be before the”responsive-video” div:

<hr />
<div class=”responsive-video”>
<p>
<iframe title=”description of video” src=”https://player.vimeo.com/video/234518290″></iframe>
</p>
</div>
<h2>Title for this section</h2>

Learn More

Get the confidence you need to dig deeper with Code Academy’s HTML Fundamentals. The V School Web Development site takes an in-depth look at all you could want to learn about Block and Inline elements.

Primary Sidebar

Open Office / Co-Working Sessions

Second Monday of the month:
11 a.m. – 12:30 p.m.

Fourth Thursday of the month:
2 p.m. – 3:30 p.m.

Email us for the Zoom link.

College of Fine Arts WordPress Instruction
College of Fine Arts Drupal Instruction
Subscribe to our email list to receive periodic tips and resources for generating great digital content

Contact Us

The COFA Web team can be reached by emailing us at cofawebmaster@austin.utexas.edu


To view some links on this page you may need to download Acrobat Reader.

UT Home | Emergency Information | Site Policies | Web Accessibility | Web Privacy | Adobe Reader

© The University of Texas at Austin 2025