- When using tables on a page, make sure that the first row of each table is set up with a “header” property. You can do this within the Table Properties dialog.
- Don’t place hyperlinks around non-descriptive elements, such as “Click Here, or “Read More Here.” Instead, have the link attached to descriptive text directly preceding that instruction or rewrite the link to describe where the user is being taken.
- When using Google Calendar for your events, make sure that every event has a unique name, even if it’s a repeating event, such as a School Board Meeting. Be sure to add some kind of differentiator (such as the date) to ensure the title is unique.
- When adding content within an <iframe>, you need to add TITLE information to the code being added so that screen readers can identify the item.
- Update/Remove Flash-based content with other ADA-compliant variation. If keeping Flash content, then an OBJECT tag needs to be added to the code
- Never use the same title for multiple pages.
- When using the Button widget, make sure to add descriptive information in the TITLE field; screen readers use this to tell the user what the button does.
- Always make sure to have a title filled in the metadata area for each page created.
- All images must have “ALT TEXT” information filled in the properties area so that a screen reader knows what that image is. This applies to every usage of an image, whether it’s part of your text area or within a photo gallery.
- "ALT TEXT” needs to use more descriptive words/phrases to describe the images.
- Do not nest tables within other tables.
- Do not use Heading tags (<h1>, <h2>, etc.) with spaces to create blank space between paragraphs. Either add padding to the widget, or use the Paragraph (<p>) tag. The same rule applies when adding images within the Text widget editor. Put them within a paragraph tag, not a heading.