Readable page structure is vital for digital accessibility as it breaks content into digestible, logical chunks. It allows users of screen readers to navigate via shortcuts, helps individuals with cognitive disabilities process information
Headings aren’t just for making text big and bold. They tell screen readers—and all assistive technology—how your page is structured.
People who use screen readers navigate your page easily
All readers quickly skim and scan for key information
Google and search engines understand your content better
Screen reader users often jump from heading to heading to find what they need
Headings create structure, just like a table of contents
Without real headings, a page becomes a wall of text for anyone using assistive tech
Don’t use bold text alone to fake a heading
Don’t skip heading levels (like jumping from H3 to H5)
Don’t use headings just to make something look bigger—they’re not for decoration
✔️ Start with H3 (Finalsite reserves H1 & H2)
✔️ Use headings to break up content into meaningful sections
✔️ Always follow a logical order
❌ Never rely on bold or size alone
Explore the many hands-on science programs offered at our school. (Normal Text)
Students study living organisms, cellular structures, and environmental systems. (Normal Text)
Focused on plant biology, this elective explores species classification and lab experiments. (Normal Text)
We return to the bigger heading because this is a new subheading. If we were to describe different math programs in this section, we would use subheadings to clearly organize them, like the examples above.
When using Final Site, start headings for p[age content with H3 —Not H1 or H2
On our SMCPS websites (Finalsite), the top heading levels are already in use:
H1 = the website name (like “Greenview Knolls Elementary”)
H2 = the page title (like “Special Programs”)
That means:
You should begin your content with H3.
How to Structure Your Headings
Main section heading <h3>
Subsection under that <h4>
Optional sub-sub-section<h5>
Always use headings in order—don’t skip from H3 to H5.
Font formatting is critical for digital accessibility because it dictates whether users with visual, cognitive, or motor impairments can perceive, navigate, and comprehend your content. Proper formatting ensures that assistive technologies (like screen readers) interpret text accurately and that readers with conditions like dyslexia can process information without visual strain.
✔️ Stick to simple, sans-serif fonts
✔️ Use bold or large size for emphasis
❌ Don’t rely on color or underlining to show importance
❌ Skip cursive and wild fonts—even if they look cool
If someone prints your page in black and white, will they still understand it?
If not, adjust your contrast.
Has anyone told you it’s hard to read? Change it.
Use Strong Color Contrast
Users with low vision and color blindness may have difficulty reading documents that lack sufficient contrast.
Rule of Thumb:
Black text on white background.
White text on black background.
That’s it. That’s the safest, easiest combo.
Why This Matters:
Some users:
Have low vision or glare sensitivity
Are colorblind
Use monochrome displays or dark mode readers
Without good contrast, text becomes unreadable—and your message gets lost.
Normal text: at least 4.5:1
Large text (18 pt or 14 pt bold): at least 3:1
You don’t need to memorize this.
Just use this simple tool if you’re unsure: WebAIM Contrast Checker
Light Gray with White
Yellow with Light Blue
Any Blue with Any Blue
Red with Green
Color alone should never be used to:
Show importance
Give instructions
Highlight errors
Some people are colorblind or use a black-and-white display. If you use color to emphasize something, also use bold text, size, or a clear icon.
Example:
✅Good: Please fill out all required fields.
❌ Bad: All red questions are required.
In modern digital accessibility, it is an established best practice to never use underlines for emphasis on non-clickable text. Underlines are an established visual indicator that text is a hyperlink. Using them for emphasis creates confusion, violates accessibility conventions, and frustrates users who try to click them but fail.
Cursive may look pretty, but it’s hard to read—especially for:
People with dyslexia
Screen readers
Mobile users with small screens
Users who can’t read cursive
Arial, Verdana, Open Sans, Roboto, Tahoma
Cool-looking fonts are often a nightmare for accessibility.
They might confuse screen readers, slow down reading, or look like gibberish when resized.
Plain language is communication that your audience can understand the first time they read or hear it. It is a vital component of digital accessibility because it reduces cognitive load, directly bridging information gaps for users with cognitive or intellectual disabilities, language barriers, and lower reading proficiency.
Why it's important:
It is easier to understand: Many people think and learn in different ways. Simple words and short sentences help everyone understand important ideas quickly.
Accessibility rules, including the Americans with Disabilities Act (ADA), require web content to be understandable.
It helps people finish tasks: When instructions are simple, people are less likely to make mistakes on forms or when using websites.
It helps computer tools: Tools like screen readers (which read text out loud) work much better when the writing is clear and simple.
Writing simply also makes computer translation tools much more accurate. When you use easy words, the software can translate your content into other languages without making mistakes.
Why simple writing helps translation:
It prevents mix-ups: Simple words usually have only one meaning, so the computer picks the right one.
It keeps sentences clear: Short sentences are easier for the computer to understand.
It stops funny mistakes: Avoiding slang and idioms keeps the meaning accurate when translated.
It saves money: Good, simple writing means human translators have less work to do.
Why should headings be used in order instead of using bold or large text to “fake” a heading?
What is one way you can make a page easier to read for families using phones, screen readers, or translation tools?
Before publishing, what is one thing you can check to make sure your text is readable?