HTML and Content Pages

Reading with Tabs | Quick Check

HTML—Hypertext Markup Language—is the foundation of web content. You don’t need to be a coder to benefit from it, but it helps to understand the idea of semantic structure. When the structure is semantic, assistive technologies (like screen readers) can understand the page: what’s a heading, what’s a list, what’s navigation, what’s a button, what’s a table header, etc. That is largely what makes pages accessible, consistent, and easy to navigate.

If you use Canvas for any reason, please review the following tabs for foundational concepts:

HTML Basics

HTML—Hypertext Markup Language—is the code behind web pages. It structures content semantically and controls how pages look and behave, including headings, lists, emphasis, links, and media.

In Canvas, you’re already using HTML whenever you work in the Rich Content Editor (RCE)—to build announcements, discussions, assignments, or pages. Every time you format content in those tools, you’re creating structured web content through a visual editor.

A simple visual showing HTML tags around headings and paragraphs.

Content Pages

Canvas containers function much like websites—so Canvas authors are web authors.

Most of the framework is already built for you, but your pages bring the content to life. A content page allows you to add and organize material right within your course, formatted using the Rich Content Editor.

In a face-to-face setting, people learn through a mix of tools—whiteboards, handouts, slides, demonstrations, and conversation. In an online environment, content pages can become the central hub that keeps everything readable, navigable, and in one place.

Well-designed pages reduce barriers and cognitive load by limiting extra downloads, reducing scrolling fatigue, and making it easier for people to find what they need quickly.

Why Design Matters

Digital media has the potential—if designed thoughtfully—to work seamlessly with assistive technology and benefit everyone. Accessible design doesn’t just help a few users; it creates smoother, faster access for all.

When content is structured well—with headings, lists, and descriptive links, which we'll learn about in the pages to come—assistive technologies can interpret it accurately. The result is an inclusive experience that benefits readers with and without disabilities alike.

Web Page, Canvas Page, or Document?

In our district, we work in an ecosystem: some content lives inside Canvas (only available to enrolled users), some needs to live on the open web (public-facing), and some content still needs to be a document (downloadable/editable/official). The best format depends on who needs access, how they will use the information, and whether the content needs to be updated often.

Start with this question

Who needs access? If the audience is limited to enrolled Canvas users, a Canvas page is often best. If the audience includes anyone outside Canvas, you may need a public web page or an accessible document.

Then ask...

Will it need updating? The answer is usually yes—consider what format will fit with your workflow and needs.

Review the following three tabs to assess which format makes the most sense for you and your audience:

Use a Canvas Page

Best for: content meant for people who are already in your Canvas space (students, trainees, committee members, internal reviewers).

Why choose Canvas?

It fits the workflow: people are already there, so there are fewer clicks, fewer downloads, and fewer places to get lost.
Easy to update: edit once and everyone sees the current version right away.
Better navigation: headings, lists, and links work well with keyboard navigation and screen readers when built cleanly in the RCE.
Mobile-friendly: Canvas pages respond dynamically (resizing to different devices), much better than PDFs (portable document format) on phones and tablets.
More consistent: you can keep patterns (overview → steps → examples → etc.) so people learn how to move through your content.

Use Canvas pages for things like:

Module overviews, weekly instructions, and step-by-step directions
Short readings and guidance that people will return to
“How to” pages, checklists, and process documentation
Embedded media with context (videos + captions/transcripts + key points)

Watch out for:

Canvas is not open: if someone outside the course needs access, a Canvas page won’t help them unless you enroll them or provide another format.
Third-party embeds: embedded tools can introduce accessibility barriers even when the page itself is well built.

Use a Public Web Page

Best for: information that must be available beyond Canvas (public audiences, prospective participants, community members, cross-campus partners, or anyone without course access).

Why choose the web?

Access without enrollment: anyone with the link can reach the content (no Canvas role, no login hurdles).
Shareable and searchable: easier to reference in emails, websites, and documentation; can be found again later.
Single source across groups: useful when the same content supports multiple courses, departments, or trainings.
Better for “evergreen” guidance: policies, resource lists, and step-by-step help that stays relevant over long periods of time.

Use public web pages for things like:

Public-facing guidance (how to access supports, general accessibility expectations, how-to resources)
District-wide resource hubs and help pages
Information you need to send broadly (staff, faculty, students, community)

Watch out for:

Ownership and upkeep: decide who is responsible for maintaining the page so it doesn’t go stale.
Accessibility still applies: web pages must meet accessibility expectations too—structure, contrast, alt text, captions, and keyboard support.

Link stability: if you frequently reorganize sites, use stable URLs or a central hub to avoid broken links.

A best practice

Link to ONE primary place you can update rather than building/re-updating the same content in multiple places.

Use a Document (Word/Portable Document Format)

Best for: materials that truly need to be downloaded, edited, printed, signed, or preserved as an official file.

Why choose a document?

People need to edit it: templates, worksheets, and forms: especially Word documents or fillable Portable Document Formats (PDFs).
It must be preserved: official policies, contracts, agreements, and archival documents.
Print is part of the workflow: when layout matters and the document is designed for print use.
Offline access: useful when people may need to read or complete something without reliable internet.

Use documents for things like:

Fillable forms and signature documents
Editable templates (Word) and structured worksheets
Official policies and long formal reports that must remain as files

Watch out for:

Documents with accessibility barriers: scanned PDFs, missing formatting, etc.
Extra steps: downloading, opening, and switching between files adds friction for everyone (especially on mobile).
Version confusion: once files are downloaded, old versions can linger.

Best practice when a document is needed

Pair the document within an email, Canvas, or web page that includes a plain-language summary, what to do with the file, key dates, and next steps.

Quick rule of thumb: If it must be read and navigated, choose a page (Canvas or web). If it must be downloaded to complete, edit, sign, or preserve, choose a document. If the audience is outside Canvas, a public web page (or accessible document) is usually the right move.

Quick Check

Which option best reflects when to use a Canvas page instead of uploading a document?

Upload a PDF for weekly instructions so people can download and print them.: Weekly instructions are usually easier to follow as a Canvas page because they’re more readable, navigable, and easy to update.
Build the module overview and step-by-step directions as a Canvas page, and only attach a document if people need a downloadable template or form.: Correct: Canvas pages are best for content people need to read and navigate. Documents are best when a file is required for editing, completing, or printing.
Always use documents because they look more professional than web pages.: Documents can be appropriate in some cases, but pages are often more usable and accessible for everyday content.

Connection

You may have started to notice that pages in this course are designed similarly. Consistency in how information is presented helps students, colleagues, and reviewers engage with your material confidently and with fewer barriers.