{"id":10500,"date":"2026-05-14T15:49:30","date_gmt":"2026-05-14T20:49:30","guid":{"rendered":"https:\/\/netasite.org\/?p=10500"},"modified":"2026-05-14T15:51:30","modified_gmt":"2026-05-14T20:51:30","slug":"i-thought-our-website-was-accessible-i-was-wrong-by-terry-jilian","status":"publish","type":"post","link":"https:\/\/netasite.org\/?p=10500","title":{"rendered":"I Thought Our Website Was Accessible. I Was Wrong. By Terry Jilian"},"content":{"rendered":"

What I\u2019ve learned about accessibility in schools\u2014and how small changes can make a big difference<\/strong><\/h2>\n

I\u2019ve been responsible for our district website since 2015\u2014and for years, I thought I was doing accessibility right.<\/p>\n

I wasn\u2019t.<\/p>\n

Like many educators, I cared deeply about making information available to everyone. I followed the guidance I was given, checked the boxes I knew about, and did my best with the tools I had. But the biggest challenge wasn\u2019t effort\u2014it was uncertainty.<\/p>\n

I didn\u2019t always know how to check accessibility, what tools to use, or even what \u201caccessible\u201d really meant in practice.<\/p>\n

\n

When \u201cDoing Your Best\u201d Isn\u2019t Enough<\/strong><\/h2>\n

Early on, I was told that document accessibility\u2014especially PDFs\u2014was critical. I learned the steps I was supposed to follow and tried to apply them. But even after doing everything I thought was right, I would still get flagged in accessibility reports.<\/p>\n

It was frustrating.<\/p>\n

I didn\u2019t know what I was missing, and I didn\u2019t always have access to the tools needed to fix it. So I kept trying, hoping I was getting closer.<\/p>\n

Then last summer, at the Future Ready Nebraska Conference, I started hearing more about updated accessibility expectations and legal requirements. If I\u2019m being honest, it was overwhelming.<\/p>\n

It also forced me to confront something important: accessibility isn\u2019t just about websites. It includes the documents teachers send home, the flyers we post, and the content we share on social media.<\/p>\n

And I needed to understand it better.<\/p>\n

\n

Accessibility, in a Nutshell<\/h2>\n

Accessibility standards are built around four core principles, often referred to as POUR:<\/p>\n

Perceivable<\/h3>\n

Information must be presented in ways users can sense.<\/p>\n

This includes adding alt text to images, captioning videos, and ensuring strong color contrast.<\/p>\n

Operable<\/h3>\n

Users must be able to navigate and interact with content.<\/p>\n

That means full keyboard navigation, clear heading structure, and meaningful link text.<\/p>\n

Understandable<\/h3>\n

Content should be clear and predictable.<\/p>\n

Plain language, consistent layouts, and avoiding color-only meaning all help users process information more easily.<\/p>\n

Robust<\/h3>\n

Content must work with current and future assistive technologies.<\/p>\n

This includes properly structured documents, accessible PDFs, and using true lists and tables instead of visual formatting tricks.<\/p>\n

That all sounds straightforward\u2014but applying it consistently is where the real challenge begins.<\/p>\n

\n

What I\u2019ve Learned Along the Way<\/h2>\n

Alt Text Matters More Than You Think<\/h3>\n

Images need alternative text so screen readers can describe them. Every major tool includes a way to add this\u2014it just takes intention.<\/p>\n

Alt text should be concise but meaningful. Think about what you want someone to understand from the image, and describe that.<\/p>\n

If an image is purely decorative, mark it that way so it can be skipped.<\/p>\n

\n

Structure Isn\u2019t About Style<\/h3>\n

Headings aren\u2019t just for making text look bigger or bolder\u2014they create structure.<\/p>\n

Every document should have a clear hierarchy, starting with a main heading and followed by properly nested subheadings. This allows screen readers to navigate content logically.<\/p>\n

I\u2019ll admit\u2014I used to choose headings based on how they looked, not what they meant. That small misunderstanding made a big difference.<\/p>\n

\n

Captions Benefit Everyone<\/h3>\n

Captions aren\u2019t just for accessibility\u2014they\u2019re useful for everyone.<\/p>\n

I often find myself watching videos without sound or relying on captions to better understand what\u2019s being said. Tools like Canva make this easier with auto-generated captions, but it\u2019s still important to review them for accuracy.<\/p>\n

\n

Simplicity Improves Access<\/h3>\n

Clear, simple writing helps everyone\u2014not just those using assistive technology.<\/p>\n

Short sentences, plain language, and clean design make content easier to read and understand. Busy backgrounds and cluttered layouts can quickly become barriers.<\/p>\n

\n

Color Contrast Isn\u2019t Optional<\/h3>\n

Text must stand out clearly from its background.<\/p>\n

Using high contrast makes content readable in different lighting conditions and for users with visual impairments. Tools like contrast checkers can help verify this.<\/p>\n

Also, never rely on color alone to communicate meaning. If something is important, it should be clear even in black and white.<\/p>\n

\n

Images Can Exclude People<\/h3>\n

We often use images\u2014especially flyers\u2014to grab attention and quickly share information. But when all the important content is inside an image, it can\u2019t be read by screen readers or translated easily. That means some users are left out.<\/p>\n

A simple fix: include the same information in the accompanying text.<\/p>\n

\n

Emojis and Hashtags Need Intentional Use<\/h3>\n

Emojis can enhance a message\u2014but overusing them can disrupt screen readers. Hashtags should use camel case (capitalizing each word) so they\u2019re read correctly. For example: #SchoolLunchMenu instead of #schoollunchmenu.<\/p>\n

\n

Links Should Be Clear<\/h3>\n

\u201cClick here\u201d doesn\u2019t tell users anything.<\/p>\n

Links should clearly describe where they lead, and they should be visually distinct\u2014typically underlined and in a different color.<\/p>\n

\n

PDFs Are More Complicated Than They Seem<\/h3>\n

Not all PDFs are truly accessible.<\/p>\n

For example, documents scanned from a copier are often just images\u2014even though they\u2019re saved as PDFs. Screen readers can\u2019t interpret those.<\/p>\n

Even exporting from tools like Word or Canva doesn\u2019t guarantee accessibility. Proper structure and tagging are still required.<\/p>\n

\n

Tables Require the Right Tools<\/h3>\n

I once spent hours trying to fix a table in a flyer\u2014adjusting formatting, rebuilding it, starting over\u2014only to realize the issue wasn\u2019t what I was doing. It was how the table was created. Tables need to be built using proper tools so screen readers can interpret headers and relationships correctly. Visual formatting alone won\u2019t work.<\/p>\n

\n

Tools That Can Help<\/h3>\n

You don\u2019t have to figure this out on your own.<\/p>\n

\u25cf Built-in screen readers on Mac, Windows, and Android can help you experience your content differently<\/p>\n

\u25cf Online tools can check color contrast<\/p>\n

\u25cf Programs like Grackle Docs and Adobe Acrobat Pro can help evaluate and improve document accessibility<\/p>\n

\u25cf Many platforms now include built-in accessibility checkers\u2014use them<\/p>\n

\u25cf AI tools can also support accessibility efforts by helping generate alt text, simplify writing, or flag potential issues\u2014but they should always be used as a starting point, not a final solution.<\/p>\n

One of the most eye-opening things you can do is try navigating your website using only a keyboard or listening to it with a screen reader.<\/p>\n

You\u2019ll learn quickly what works\u2014and what doesn\u2019t.<\/p>\n

\n

Moving Forward<\/h3>\n

If you\u2019ve ever created a document or posted content and just hoped it was accessible, you\u2019re not alone.<\/p>\n

Accessibility can feel overwhelming at first. There are a lot of details, and it\u2019s easy to feel like you\u2019re missing something.<\/p>\n

But this work matters.<\/p>\n

It\u2019s about making sure everyone\u2014students, families, and community members\u2014can access the information they need.<\/p>\n

Accessibility isn\u2019t about perfection. It\u2019s about progress.<\/p>\n

And each time we take a step forward, fewer people are left out.<\/p>\n

 <\/p>\n

 <\/p>\n

I used AI tools to help refine and organize this post, but the experiences and lessons shared here are my own.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

What I\u2019ve learned about accessibility in schools\u2014and how small changes can make a big difference I\u2019ve been responsible for our district website since 2015\u2014and for years, I thought I was… <\/p>\n

<\/div>\n

Read More<\/a><\/p>\n","protected":false},"author":123459,"featured_media":10502,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-10500","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/netasite.org\/index.php?rest_route=\/wp\/v2\/posts\/10500","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/netasite.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/netasite.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/netasite.org\/index.php?rest_route=\/wp\/v2\/users\/123459"}],"replies":[{"embeddable":true,"href":"https:\/\/netasite.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=10500"}],"version-history":[{"count":2,"href":"https:\/\/netasite.org\/index.php?rest_route=\/wp\/v2\/posts\/10500\/revisions"}],"predecessor-version":[{"id":10503,"href":"https:\/\/netasite.org\/index.php?rest_route=\/wp\/v2\/posts\/10500\/revisions\/10503"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/netasite.org\/index.php?rest_route=\/wp\/v2\/media\/10502"}],"wp:attachment":[{"href":"https:\/\/netasite.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=10500"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/netasite.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=10500"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/netasite.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=10500"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}