Many common issues with web accessibility are addressed and remedied at the platform level and theme level. However, there are common issues that can still arise when editing pages. Publishers should be mindful of these best-practices.
-
Header styles used on paragraphs of text
When styling paragraphs with header styles (like H1, H2, etc.), it's best to avoid using the header styles from the Format menu, which are meant for page or section headers. Instead, opt for the header style options available in the Style menu within the Text widget. This approach helps maintain ADA compliance throughout your pages.
-
Copy in Images
If you add readable copy into an image using a graphics program, then you should make sure to use that copy for the ALT description of the image. In the SchoolStatus page editor, you add ALT text in the Alternative Description field in the image editor.
-
Alt Text for Images
All images need to have an alt="" attribute associated with their IMG tag. The SchoolStatus page editor adds this by default, but in some cases, additional information is needed. Any image that serves a function other than decoration needs to have the alt attribute filled in. The most common examples of this are images that contain information and images used as links. In these cases, the alt tag should be completed with a description of the image content. In the SchoolStatus page editor, you can add ALT text in the Alternative Description field in the image editor.
-
Using Tables for Page Layout
In the early days of creating and editing web pages, tables were commonly used to position elements on the page. Now, tables should only be used for displaying data that has a logical relationship. Learn how to properly use and build tables in the SchoolStatus page editor. Publishers can manage page layouts provided by the Layout widget to position elements as needed.
-
Keyboard Trap
-
Avoid "keyboard traps" or areas where a user gets stuck on the page with a keyboard. An example of when this could happen is with an embedded media player. When tabbed, the user gets stuck on the controls and cannot move beyond that point in the page, causing the user to not be able to access the remaining information.
-
Avoid plugins that require the user to install it. It might not work with certain assistive technology
-
Use radio buttons, checkboxes, and combo boxes whenever user input is needed as it reduces the amount of typing..
-
Prompt user with mistakes (prompt needs to be readable by assistive technology)
-
-
Technology Limitation Considerations
Avoid complicated words & sentences (anything that would be difficult for a robot to read)
Additional Articles
-
Keyboard Navigation in Mac Browsers - An article that reviews how to set up tab key navigation on a Mac using the system preferences and the settings in various applications.