Beyond the PDF: Anyone Can Create an Accessible Webpage 

Accessibility Matters at UC - Accessible Webpages with Jamie Herrera

By Jamie Herrera, Accessibility Program Manager   

Many teams default to sharing information as PDFs, Word documents, or slide decks because they feel quick and familiar. However, when your primary goal is helping people read, search, and use information online, a webpage is almost always the better choice. 

Know When to Skip the PDF 

PDFs and Office documents still have an important role for printable flyers, forms, signed contracts, and official records requiring fixed layouts. Webpages automatically adapt to different screen sizes, work smoothly with browser translation and text-resizing tools, and are much easier for search engines to index. 

Consider publishing as a webpage whenever you create: 

  • Guidance and Policies: Standard operating procedures, employee handbooks, and public accessibility statements. 
  • Support Content: Frequently asked questions (FAQs), help articles, and training guides. 
  • Updates and Overviews: News announcements, blog posts, and product or service descriptions. 

Best of all, you do not need coding skills to build an accessible webpage. If you already use Microsoft Office or Google Workspace, you can set your content up for a smooth, accessible web transition from the very start. 

Step 1: Build Structure into Your Source Document 

Accessibility begins before your content ever goes online. Both Microsoft Word and Google Docs include built-in formatting tools that translate cleanly into webpage code (HTML)—provided you use them instead of relying on visual styling alone. 

  • Use true heading styles: Apply Heading 1 for your main title and Heading 2 or Heading 3 for subheadings. Avoid making text look like a heading simply by making it bold or increasing the font size; assistive technologies like screen readers rely on actual heading tags to navigate a page. 
  • Use built-in list and table tools: Create lists with the standard bulleted or numbered list buttons, and use real tables (with designated header rows) only for data—never just to arrange text on a page. 
  • Add alternative text to images: Any image that conveys meaning needs concise “alt text” describing what information it communicates (for example, “Employee using a screen reader to navigate a company website” rather than “Picture”). Purely decorative images can be left blank. 
  • Write descriptive hyperlinks: Replace vague links like “Click here” or “Learn more” with specific destinations, such as “View the employee benefits guide.” 

Step 2: Convert and Review Your Content 

Most content management systems (CMSs) let you paste or import content directly from Word or Google Docs. (Note: Converting existing PDFs can take more manual cleanup, as PDFs often strip away underlying structural tags. If you have access to a PDF to HTML conversion tool, it helps!) 

Once your content is moved into your web platform, verify that your formatting survived the transfer: 

  1. Check your structure: Confirm that headings, lists, and data tables kept their proper formatting. 
  1. Verify media and links: Ensure alt text remained attached to images and all links point to the right places. 

Step 3: Run Quick Accessibility Checks 

Even well-structured content can run into barriers if your website’s template has poor color contrast or broken navigation. Before hitting publish, do a quick, non-technical review: 

  • Test with your keyboard: Try navigating the page using only the Tab and Enter keys to make sure nothing gets stuck. 
  • Zoom to 200%: Increase your browser zoom to 200% and check your phone to ensure text reflows cleanly without overlapping. 

By treating accessible webpages—not PDFs—as your final destination, you create content that is easier to maintain, easier to find, and usable by everyone. 

Author  

Jamie Herrera

Jamie Herrera  
Accessibility Program Manager  
UC Office of the President  

About the Accessibility Matters at UC series 

We heard you! When we reviewed our content survey results, one message came through clearly: there’s a growing need for more focus on accessibility. And you’re right—accessibility affects everyone! Follow along as we share stories that highlight why accessibility truly matters at UC. Do you have a story to contribute to the series? Submit an intake form! Submit a UC Tech News blog intake form found here.