Title II Digital Accessibility Tips for Staff

We discourage the use of PDFs on the website because most are not ADA compliant. PDFs must be formatted in a certain manner to be read with a screen reader. Please place content directly onto the website, and not a PDF, to ensure ADA compliance and language-translation compliance.

• If a PDF document, such as a letter or a report, must be posted on the website, it should be formatted properly with headings so it can be read with a screen reader. Tables containing data are often not formatted properly.

We are evaluating tools and templates that align with accessibility best practices and work well on phones and computers. During this transition:

• Key details from flyers will be posted on the website.

• PDFs will include alt text and tagged headings when available.

• Alternative formats or translations are available by request at info@pointschools.net or 715-345-5462. 

Thank you for your patience as we complete this work.

Last updated: October 13, 2025

A PDF that is scanned is not ADA compliant whatsoever. It is essentially a photo, and a screen reader cannot read the text at all. Remember, “a scan is not a plan!”

A document should contain headings so someone using a screen reader can navigate to different sections of the document. On the website, paste the content from your document directly onto the website and select headings (headlines) where applicable rather than posting a PDF.

• Instructions on how to include headings in a Microsoft Word document

Key instructions for accessible headers in Google Docs

• Use the correct tool: Never use bolding, increasing font size, or other manual formatting to create the appearance of a header. This is a visual cue only and will not be identified as a heading by a screen reader.
   
• Access the Styles menu: To apply a heading, select the text, then click the Format menu > Paragraph styles. You can also find the Styles dropdown menu in the main toolbar.
   
• Follow a logical order: Structure your headings like a document outline. Headings should be properly nested, and you should not skip heading levels.
  • Heading 1: Use once per document for the main title.
  • Heading 2: Use for the major sections of your document.
  • Heading 3, 4, etc.: Use for subsections within a Heading 2, and so on.
     
• Don't use the "Title" style: The "Title" and "Subtitle" styles can be inconsistent and may not be recognized reliably by assistive technologies. Instead, always use Heading 1 for the main title.
   
• Test your document structure: Use the Document Outline to verify your heading structure. Click the "Show Document Outline" icon on the left side of the toolbar (it looks like a bulleted list with indentations). This will show a nested view of your headings.
   
• Customize styles: If you prefer a different look for your headings, modify the existing style instead of manually reformatting. After changing the font, size, or color of a heading, re-open the Styles menu, hover over the heading level you want to change, and select "Update 'Heading' to match". 

Other ADA compliance tips for Google Docs

• Add descriptive alt text for images: Provide concise, meaningful descriptions for all informative images. Right-click the image and select Alt text. Leave the "Title" field blank, and enter the description in the "Description" field.
   
• Use descriptive link text: Instead of generic phrases like "click here," write meaningful link text that describes the destination. Highlight the text you want to hyperlink, and press Ctrl+K (or Cmd+K on Mac).
   
• Ensure sufficient color contrast: Check that the contrast between text and background colors is high enough for readability. Avoid using color as the only way to convey meaning.
   
• Install an accessibility checker: The third-party add-on Grackle Docs can scan your document for accessibility issues, including missing headings, and provide guidance on how to fix them. 

Learn more about accessibility in Google Docs

A screen reader cannot read information in a table when it has nested tables, split cells, or merged cells. Generally, tables are best used for numerical data. Tables must have a header row (formatted top row), and often but not always require a header column (formatted first column on left). 

Why? A screen reader audibly reads the data from left to right. The top row (header) has to be formatted so the screen reader knows to read the information in that row first before reading the information below it.

If the header is formatted properly, the screen reader will read each row by first reading the title found in the header, at the top of the column, so you can tell what type of data is being described. 

If you are creating a table on the website, click "header row" and if needed click "header column".

• Instructions on how to create accessible tables in Microsoft Word

People with limited vision cannot read the text if there is not enough contrast between the text and the background. (For example, light gray text on a light-colored background.)

A fool-proof way to ensure compliance is to use black text on a white background (like a Word Doc.) Read the WCAG color contrast standards or use the Web AIM Contrast Checker.

When you upload an image to a website or social media, you must write “alternative text” or “alt text” that briefly describes the photo for people who are blind and/or using screen readers. Here are examples of alt text. (Finalsite will require you to input alt text when uploading an image onto the website. You can also input alt text into images on Google Slides, Microsoft Powerpoints, Word Docs, etc.)

All videos on our website are required to have closed captioning so people who are hard-of-hearing can understand the information in a video. Additionally, people who are visually impaired also rely on closed captioning to service their screen readers. Please make sure closed captioning is always included in your videos, for the entire duration of the video. Words that are displayed on the screen but not spoken aloud (i.e., someone holding a sign) are also supposed to be contained in closed captioning.

Tip: The easiest way to ensure closed captioning is to simply upload your video to a YouTube account and enable automatic closed captioning. Then, you can embed the YouTube video onto a website. In addition, YouTube allows for closed captioning in multiple languages.

Sometimes, formatting issues will prevent YouTube from automatically enabling closed captioning and the process will have to be done manually.

When linking to a web page or an email address, the link should be descriptive so a person with a screen reader can understand the link they are clicking on. It should not say “click here” or “view more.” Instead, it should say, “Visit the Stevens Point Area Convention & Visitors Bureau” or “View the latest School Board Meeting.”

Readability is reduced with all caps (all capital letters) because all words have a uniform rectangular shape, meaning readers can't identify words by their shape. Also, use of all caps is considered yelling.

• Accessibility 101 from Microsoft
   

• Accessibility Testing for Electronic Documents from Section508.gov 
   

• Accessible Name and Description Inspection (ANDI) Tool
   

• Accessible PDFs in Adobe In Design
   

• Accessible PDF Forms in In Design
   

• Accessible Powerpoint Presentations from Section508.gov
   

• Accessible Word Documents 
   

• ADA.Gov Compliance Guide for Small Entities
   

• ADA Title II Fact Sheet
   

• Bookmarklets for Accessibility Testing on JavaScript
   

• Design Accessibility in Canva
   

• Design Accessibility in Canva Video
   

• Google Workspace User Guide to Accessibility 
   

• Guidance on Website Accessibility and the ADA
   

• HTML Language Codes
   

• Inclusive Microsoft Design
   

• Microsoft Accessibility Resources
   

• Protocols for Creating Accessible Open Educational Resources from National Center on Accessible Educational Materials (PDF)
   

• NVDA Screen Reader
   

• OCR Accessibility Videos; OCR Accessibility Videos Playlist
   

• PDF Remediation Training Videos from Section508.gov
   

• TPG Color Contrast Checker
   

• W3C Web Accessibility Initiative Homepage
   

• W3C WAI Testing Guidance
   

• Website Accessibility Evaluation Tool (WAVE)
   

• XML Sitemap Generator