For a Sunday: The Gospel of HTML

(or, “At the Crossroads of HTML and Daily Relevance for A11Y”)

(or, “Why should I care about HTML? I just use PDF documents!”)

Musician points towards the heavens as turquoise light shines down.
Photo by Adrian Linares on Unsplash

Good morning!

Have I told you lately what I think about HTML?

In terms of accessibility, if plain text is the most honest digital format, then HTML is the most powerful:

  • HTML enables both the content and the container to exist.
  • HTML binds and aligns technologies while presenting them as a unified whole.
  • HTML presents the message and at the same time it can know what it is talking about.
  • HTML enables the Internet to exist and allows for the thing we call Web Accessibility where people with disabilities can enjoy this rich capability to interact with the world.

For each of us here, HTML has allowed our individual capability to create, express, and experience the world to go far beyond anything previous generations have known or imagined.

At its best, HTML helps us be more fully aware and capable of maximizing our own potential.

And cat videos. HTML allows you to see more cat videos than anyone needs or could have dreamed possible.

Despite all of that, people tend to hate HTML code.

Two thumbs down and a frown from a brown-haired girl.
Photo by Thomas Park on Unsplash

With the obvious exceptions, most of the world will actively avoid the knowledge of HTML code and any activity that requires them to engage with text inside of brackets.

I get it- I’m not here to try and sell you on it.

But why does this matter?

Because anywhere you type digital text in your CMS you are creating HTML text.

This is something I thought you should know about, because I recognize you are really committed to the cause.

I can tell if there is an opportunity to enhance the access and usability of the communications you send students, you will be sure to make it most usable.

Because now you know- and you care.

That’s just beautiful…

Organizational Name-Calling

The thing about HTML that makes it special is the schema that allows for everything to be defined. This is the “ML” from HTML – MARKUP LANGUAGE.

The whole point of HTML is to define every part of the message by marking it up with a tag. There are a lot of tags available in HTML – but thankfully we don’t need to worry about all that.

We can get away with a handful of things to worry about because our CMS text editors are typically limited in what they make easily possible.

So without going crazy, or getting your hands nerdy, you can probably manage the a11y of HTML in your CMS.

Creating HTML in your CMS – all you need for now…

You should be able to influence these items within your CMS-based content editor:

  • Text and Background Color Contrast
  • Headings
  • Lists
  • Image descriptions
  • Table Header Rows
  • Link Anchors (the clickable text)

Text and Background Color

You need to make sure the text is legible and distinct from the background. Ensure your contrast ratio between foreground text and background colors satisfies the WCAG criteria –  7:1 for normal text and 4.5:1 for large text.

Tools for Colorful Creations

Here are some tools to help with color contrast:

  • Who Can Use – A tool that allows you to specify any color combinations for text and background, and then it tells you about the different use cases where the text would be problematic. You can learn about color contrast and different kinds of colorblindness as well.
  • Color Oracle – A colorblindness simulator that applies a full screen overlay over your work, allowing you to experience your content as someone with a colorblindness disability would.
  • ColorSafe – Enter your background color and font style, and ColorSafe will provide WCAG compliant colors for your text.
  • Khroma – This tool is amazing. If you are ever searching for that color combination to make your content pop, Khroma can be super helpful. Khroma asks you to pick 50 of your favorite color swatches, and then powerful AI derives countless combinations of WCAG compliant and artistically satisfying color combinations.

Your CMS text editor should have the ability to specify colors for the text and background. If you are unsure of how to specify colors with your CMS text editor, you need to contact your technical support person for assistance.

Headings

Every CMS text editor should have the ability to assign a heading style to text. Many will include styles labeled as “Heading 1” and “Heading 2”, others will simply call them “Heading” and “Sub-Heading”, or “Main” and “Sub”.

If your CMS text editor does not include this capability, you need to ask your system administrator how you are supposed to be able to create accessible content with the tools they are providing you. This is a serious question you need an answer to, and asking it might raise awareness and affect positive change.

While you wait for an answer from Tech Support…

Meanwhile, try creating your content in MS Word or another modern editing program with support for heading styles.

Once you finish creating your content, try to copy and paste it into your CMS text editor.

With the content pasted into the CMS text editor, save and view the page.

You can inspect the code for a heading style ( <H1>, <H2>, <H3>, etc. ) or use another tool such as the Wave Accessibility Checker to test whether or not the heading style was included in the copy and paste.

Heading styles are usually retained when you copy and paste from a serious word processor into your CMS text editor.

Lists

Your CMS text editor most likely has the ability to style content as numbered or bulleted lists. Look for something on the toolbar that looks like a stack of three lines with bullets or numbers on the left-hand side.

bulleted and numbered list tools from MS Word.
Bulleted and Numbered list tools from MS Word.

Image Descriptions

In many modern CMS text editors, you will be prompted to include an alternative text description of an image when you insert it into your document.

Here are some tips for providing good descriptions:

  • Be brief but descriptive of the core meaning of the picture relevant to the content it is appearing in.
  • If your CMS text editor doesn’t provide a way to give your images an alternate text description, then you should provide a textual description in your main text, and identify the image with an image caption.

If you are uncertain about whether or not your image has an alternate text description:
Try selecting your image and clicking on the Insert/Edit image toolbar button to bring up a dialog with image properties. If you’re lucky there will be a place to provide a text description.

Table Header Rows

Support for table header rows is pretty common, but it is not always easy to find the place to activate this formatting. Sometimes the toolbar will have a Table Properties button, or sometimes you will need to look in the individual cell formatting options, but somewhere in your CMS text editor should be the ability to define table header rows.

Link Anchors

Finally, when you use links in your content, make sure that the anchor (the clickable blue underlined text), is descriptive of the content that is being linked to.

Don’t use the phrase “click here”, or “more” or any other generic term used repetitively as a shortcut for inferring what will be coming if you click the link.

For Those Who Dare…

Man stands in a forest on a path that forks in two directions to go around a grove of trees.
Photo by Caleb Jones on Unsplash

Finally, and absolutely no pressure here – but if you find yourself wondering about the HTML code editing capabilities of your CMS editor, you can look for the toggle and see what sorts of options and power are unlocked…

Or you can be sure to avoid clicking anywhere near that toggle and get on with your life.

Nobody has to know either way, and no judgment.

I’m just glad you showed up and read this far. Thank you!

The Plain Truth of Accessibility

Magnifying glass lies on pages of opened bible.
Photo by Blake Cheek on Unsplash

Digital text is the foundation of accessible online communications. It is the primary structure of meaning that comprises the message being communicated.

Headings are then added to text, enhancing accessibility through increased usability.

Sure, but what does that MEAN?

To explore what this means, let’s take a trip back in time to when you were a seven year old child. Let’s pretend you’re writing a letter to Santa Claus in an effort to convince him you’ve been good this year.

The fact that you’ve been good and learning about accessibility is the essence of the message. This must get through, above all else.

However, the presentation of the letter matters too. Plain words can’t possibly convey the emotional significance of your message. You enhance your communication with sophisticated layout!

You might use colored markers or pencils – or both!

You could add glue and glitter, construction paper cut-outs, ribbons, stickers, gold stars and lipstick kisses. The creative arsenal of your seven year old self is truly impressive.

Whatever makes you happy – no judgment.

The point is that all manner of adornment could be added to your letter in an effort to make it more appealing, engaging, and ultimately successful at winning over Mr. Claus’ affection.

The one condition being, that at the root of it all is the meaning of your carefully worded message. The underlying meaning is something you want to be as simple, unmistakable, and straight forward as possible.

This way, when Santa runs all his mail through the new Anti-viral Sterilizer 9000 Spam Filter (with optional De-Glittering module), the main message remains intact.

Digital information can be styled to appear in many different ways, and the core of the message can be enhanced with semantic formatting and dynamic presentations, as long as at the root of it all the message is built on plain text.

The Honesty of Plain Text

Sign with the words "you are beautiful"
Photo by Gio Bartlett on Unsplash

If you open your information directly in a plain text application like Notepad on Windows, or TextEdit on MacOS, you see the entirety of the message in simple plain text. This is one of the most complete and unfiltered views of the text you can achieve.

One reason plain text is good for accessibility is because it has the least chance of getting screwed up in translation to other media.

If you take the plain text to a more substantial editing program, you set the stage for complex meaning. As you add styles and formatting to the text, your message begins to gather extra meaning. The words might still be the same, but they pack additional meaning.

Both behind the scenes and on the screen, your information is being loaded with potential to hold formatting information, semantic structure, alternate text descriptions, and interactive capabilities.

Accessibility vs Usability

There is a distinction between accessibility and usability when we consider digital information.

Sometimes a lack of usability is like dealing with a person who only tells you part of the story, withholding significant context and relational information that might affect how you perceive the message.

Some applications fail to support your content formatting, and they present a watered-down version of the data that appears fine visually, but is inaccessible to assistive technology.

Text without style and formatting might be something that you can load into your browser, but it is not always very much fun to try and make sense of.

Different Containers and Capabilities for Accessibility

Pure, yet limited, access is provided through Notepad – just the naked truth of your text. However, this is not a very usable option if you are using assistive technology.

Notepad does not allow for the formatting that makes your message usable. It is very accessible, but it is also very limited.

For usability, there is an important distinction between file format types, and the applications that create or present them. These applications are effectively different containers for your content. For example, there is Microsoft Word the program (CONTAINER), and there is a Microsoft Word File (CONTENT).

Microsoft Word the program has an accessibility capability as a container, allowing the user to effectively use the program with a variety of assistive technologies.

Microsoft Word the file format (.docx) has its own accessibility capability for defining your message – both within Microsoft Word the program, and other programs that are capable of opening a .docx file.

We understand that this .docx file will not have the same functionality if it is opened in a different program than Microsoft Word – but the message is capable of carrying the advanced meaning of its style and formatting. Many programs have the capability to read the content, even if they do not offer the same level of editing support as Microsoft Word.

Accessibility works the same way – not all combinations of file formats and programs provide the user with the tools to interact with the digital data – or in the same way.

The Most Accessible File Format

The question of what is the most accessible file format is answered through a measure of the capability to support access strategies for different types of digital information.

Perhaps not surprisingly, the answer starts simple and gets complicated very fast: HTML.

As a file format, there is very little that you can’t insert into an HTML file. In addition to an incredibly wide-open range of supported content, HTML also provides critical functionality for accessibility and usability.

HTML is also freely available, you can create HTML with the simplest of tools, and it is freely readable by many different browsers and other applications.

HTML is really hard to beat.

Two books next to a potted cactus, book titles: "HTML & CSS" and "Javascript & JQuery"
Photo by Greg Rakozy on Unsplash

And as you might know, it is also really easy to go down a deep rabbit hole with HTML.

I recognize that you are most likely an educator with a full load and you don’t have the time or desire to become an HTML expert. No worries, you don’t have to. You just need to use a modern CMS tool with the proper support – hopefully your institution has taken care of that.

Simple Best Practices for Accessible HTML

When you are creating HTML content, consider the tool you are using, and see if it can support the basic access strategies for digital media:

Access Strategies for Digital Media

Media TypeAccess Strategy
TextStructure (Headings, list styles, paragraph styles), Clarity, Legibility, Contrast
ImagesText descriptions and captions
AudioText Transcript
VideoCaptioning and Narrative Description
InteractiveText Labels, Keyboard Control, Section 508
ComplexAll of the above…
Above: Digital Media Access Strategies

The world is your oyster when it comes to HTML, and the more effort you apply, the bigger your pearl.

Sometimes a powerful tool can help make the impossible manageable, but too often we find that accessibility does not always make it into the awareness of the designers behind some of our favorite tools.

No sour grapes, HTML is wide open with potential.

When you find an inaccessible multi media construct, sometimes you can copy, paste, and redesign the content with the HTML tools of your CMS. This approach allows you to have a more accessible version of the content that lives in the CMS, and doesn’t require licensing fees or force students to buy a content pack.

Your only real limitations will come in the form of your CMS and its ability to support what you’re working with.

Thanks for reading!