In many of the requests for proposals (RFPs) that we get for municipal website design, there is a common question about whether or not we can build ADA Compliant websites. The short answer is yes. The above question (is the platform compliant) is the wrong question to ask. You see, once we hand over the keys to your staff to manage your website, they will need specific training to make sure that the content that they enter is ADA compliant. The vast majority of municipal websites, even ones that we have built over the years and those that our competitors have built (no matter what they tell you) are not ADA compliant for various small reasons. On this page, we will show you some of the basics to remain compliant.
Pre-Launch, here are some of the things we will incorporate into your site:
Usually this is their salespeople saying this, because they don't understand the requirements.
See the rest of this page for more information.
This is a better question to ask, because as new content is entered into your website you will need to make sure it is formatted properly, no matter which CMS provider you choose.
From the article link above, we will address of the suggested requirements.
We will do this with the images that we transfer over. Each time you add a new image to your website, however, you will need to right-click on it, go to “advanced” and enter an alternative title. It is a bit burdensome, and unfortunately most people don’t bother. But that is what is needed to meet this point so that screen readers can function.
The practice of using collages and flowchart images is pretty much over. But again, alt text can be added to any image and we will. We don't recommend large collage photos in modern, mobile website design.
We will make a best guess as the the purpose of the images in your design and include that in the alt text. But your staff will need to put alternative descriptions on EVERY image that they upload. This is tedious, and unfortuately most people adding content don't do it.
We try not to use images as navigation elements because they are not mobile friendly. We instead now use CSS to create menus and action buttons. There are many websites out there that are legacy websites created by our competitors that still have image buttons. And many don't have information on the destination like this suggestion states.
This is a bit of an outdated requirement as images for backgrounds and decorative areas could be loaded from CSS, and not have an image within the page code itself. However, for images placed into a page for decorative purposes, we will provide an empty alt tag for the image. Your staff will need to do the same if they add decorative images to a page.
We don’t produce videos, so this is not applicable to us. However, you can imagine how difficult it would be to put subtitles on all of your council meeting videos. Keep this in mind if you place them into your website. It might be better to link to an outside video resource to remain compliant here. We do offer a video player and an audio player as part of our website platform. Those players do not create subtitles for videos automatically (nothing does that we are aware of).
We don’t produce videos, so this is not applicable to us.
We don’t produce videos, so this is not applicable to us. Can you imagine how difficult this would be to do for every council meeting video?
We will do this, but most of our customers prefer to have their videos embedded into their website.
It is easy to drop a YouTube video into a web page, but this compliance guideline suggests this is a bad idea.
Newer website play videos in the browser, so there is no player. This is an outdated requirement.
We don’t produce video transcripts, so this is not applicable to us. If you wish to supply a written transcript of all of your videos, we can link then for you.
Image maps went out of favor in the 1990s and we do not use them. Image maps were large images that had multiple hotspots on them that you could click for navigation.
The look terrible, are not mobile friendly, and no one really uses them. This is an outdated requirement.
Same thing. This is related to image maps. We do not use them.
It is common to add tables to your website when you want to organize content on a page.
Like this one:
|This is a table Header Cell||This is another header cell|
|this is a data cell||this is a data cell|
|this is a data cell||this is a data cell|
The key is to make sure that tables that have data in them (Data Tables was the key phrase of this requirement) have descriptive header cells at the top of each row if you make these tables.
Because content editors can use tables from time to time, they will need to do this after the site launches.
We do this, but most layouts are handled with DIV tags and not tables.
Typically we see this within legacy content that is being migrated to a new website.
This is straightforward – make sure that the cells are under the correct headings.
This is mainly for people with epilepsy, who are sensitive to flashing images. I don't know of any municipal website vendors that use these. We do not do this.
We do not use browser plugins for Java. This is a legacy requirement that isn't valid with today's websites.
We don’t use Java applets, and we strongly discourage uploading office documents (word, powerpoint, etc.) into your website. We can’t guarantee that Adobe’s software is compliant, but we can link to it. Using PDF files to eliminate the use of office documents is an acceptable standard here.
We can do this. It is possible that it can change the look of your forms.
We do this already. Each form field has a title attribute.
This is simply part of form design. However, the "field" label can change the way your forms look.
This is done automatically. Basically they mean that you can use the tab key on your keyboard to move between form fields.
This is easy to add to any site as part of the design.