Make content accessible
Our digital services must be accessible to every single resident. Simple, service-oriented language that speaks to the service is the most accessible for residents.
It saves time because people don’t have to try to figure out what the department-specific jargon means and how it affects them.
  • If your Austin neighbor has a visual disability and uses adaptive-screen reading technology to read websites, it’s easier for them to navigate through pages with simple content.
  • The language should be so simple that someone in middle school should be able to understand it. It’s important to write no higher than an 8th grade reading level. Regardless of a resident’s educational background, service-oriented language strives to make the content clear for everyone.
  • If someone is translating information for a friend or family member, using simple words will make it easier for the message to be delivered clearly in another language.
View the federal law on accessibility at Section 508. At the bottom of this page, there is an accesibility checklist that you can use whenever drafting new content for the website.

Alternative text and Images

Accessibility ensures a website serves all users, including those with disabilities. Disabilities aren’t only visual; they can also be auditory, motor, cognitive etc.
Users with disabilities often use screen reading software, like JAWS and COBRA, to read the content aloud, which is why it important to follow the guidelines when we create content for the website.

What do you see in this image?

A photo of a blank, white square.
Your answer was probably “nothing.” This is a similar experience for someone using a screen reader if your image has no alternative text. Screen readers can’t read what an image is, making the image invisible and inaccessible to residents, or anyone trying to access that information.
  • Make alternative text descriptive. For example: “Children playing at Barton Springs Pool.”
  • Avoid images with text inside them. If there is text, you’ll need to include what the text says within your alternative text.

Color

Foreground and background colors must maintain a minimum 4.5:1 contrast ratio for users with visual impairments. Web best practice is to have a consistent color palette across an entire site rather than allowing multiple, varying colors on different pages of a site.
If a user is colorblind, certain colors are not visible to them, making the site inaccessible. To maintain accessibility, a standard color palette has been set and adjustments to colors on the site are not permitted.

PDFs and Non-HTML Content

It is best to avoid adding non-html content, such as PDFs, PowerPoints, etc., to the site as they are not typically accessible. Ask yourself if this content can be added to the site as a page. If it is necessary to add non-html content, make sure to update the content so that is accessible, such as adding tags to a PDF.
While PDFs are convenient for uploading a lot of content to the website, it makes it inaccessible for a large part of our population.

Animated GIFs

GIFs are fun to send to friends, but not great for accessibility. They can be a distraction or disorient residents with certain types of cognitive disorders, according to Web Content Accessibility Guidelines (WCAG).

Hyperlinks

Do:

  • Be descriptive.
  • Give a preview of what will be found by clicking.
  • Include file size on links to download a file (e.g., PDF, spreadsheet).
Example:
  • Diabetes can be managed with diet and exercise. Read more about diabetes prevention.
  • Download the care manual (96 kb) for more information.

Don't:

  • Use “click here”
  • Be vague
  • Navigate away from the website (have external sites open in a new tab)
Example:
  • Click here for Diabetes info.
  • Here is more info.

Video

  • Provide transcripts or captioning for videos.
  • Avoid videos with strobing or flashing as this can induce seizures in some users.
See more on federal government usability standards, and explore the W3C Web Content Accessibility Guidelines.

Accessibility checklist

Use this checklist to ensure your content is following basic accessibility guidelines.

Necessity

  • This page is necessary because a resident needs it to access a service or learn information that’s important to them.
  • This page is specific to only one user need and is not a catch-all or an FAQ.

Maintenance

  • The information on this page is true and up to date.
  • Content is as evergreen as possible (does not include information likely to change quickly).

Clarity and readability

  • Page title is clear, succinct, and includes keywords.
  • Page description includes keywords and informs the reader in plain language what they can learn or do with this page.
  • Uses active voice, not passive voice.
  • Content is as concise as possible while retaining essential information.
  • Content has no long paragraphs and uses headings (H1, H2) to break up content when appropriate.
  • Content has no lists longer than 3 items that aren't bulleted.
  • Content has been put through a reading level checker and is at or below an 8th grade reading level, or as low as you can get it for the intended users and context.
  • Acronyms are only used when they are necessary for understanding, and they are spelled out the first time they are used.
  • Technical terms are either defined they first time they are used or link to a reference page.
  • Page is free of jargon and idioms.
  • Hyperlink text is clear and actionable (not "Click here" or “Download now”).
  • All links on the page go to trustworthy sources (e.g., .gov, .edu).
  • Any PDF or downloadable file is either:
    • Absolutely necessary because it is a legal artifact (has signatures, seals, or stamps).
    • Absolutely cannot be made into a web page.
  • The page includes contact information residents can use to ask questions, ideally both a phone number and an email address, not a contact form.
  • If the page has any images, a clear, concise description is in the alt-text field.
  • If the page has any pre-recorded video or audio, WCAG standards have been implemented to make them accessible.
Last modified 9mo ago