Accessibility Updates for Apollo 2

The Apollo 2 Theme received an update to the underlying HTML code to further improve accessibility for website visitors using assistive technologies to access websites on our WordPress network. These updates will apply to all sites automatically. These updates are based on a report from an accessibility tool used by the Florida Department of Education which identified some issues Web Services could address for all sites. Some issues our website admins and editors can address at their own speed, and a link to an accessibility tutorial is present at the bottom of this article.

Below is a list of the updates and information on what these rules apply to:

  • complementary landmark: must be top level
    There needs to be an indication in the HTML code that identifies a part of the page content as related to the main content. This helps disabled website visitors better recognize parts of the page through the assistive technology they are using to browse the website.
  • Link text must describe the link target
    This is an accessibility measure to help website visitors understand the usefulness and purpose of the link.
  • Headings nested in landmarks
    This is an accessibility measure to help website visitors understand the structure of the information on the webpage.
  • Role must have parent
    To help website visitors using assistive technologies, interactive elements on the page need to be defined in a structural way (i.e. parent/child relationship) to provide enhanced navigation features for moving between items in lists, tables, and grids.
  • Role is not allowed
    To help website visitors using assistive technologies, some HTML elements which create controls for a website’s interface may have a role (ex. ID number) programmatically determined for them and if that role does not suit the element properly, it can cause an issue for some website visitors.
  • Widget labels must be descriptive
    It addressed the need for proper labelling of elements on the page to ensure they are concise and descriptive of the widget’s purpose.
  • Form controls must have labels
    Form inputs and buttons need to be able to be read by screen reading technologies, and labels provide this functionality for them.
  • `role` must be valid
    Elements on the page should have a description that clarifies that section of the page for assistive technologies.
  • Widgets must have label
    This labelling helps screen readers communicate information about the element on the page to the user out loud.

As a website Admin or Editor, you can take some steps to make sure you part in accessible content is covered by following the guidelines laid out in this Accessibility Tutorial.

Please contact us with any questions about best practices in content strategy and accessibility at any time!