Getting Started with Worldspace Sync

Texas A&M IT performs weekly accessibility scans of Key Public Entry Points (KPEPs) using a tool called Worldspace Sync. KPEP webmasters can use their Worldspace Sync account to review the accessibility reports generated from these scans.

A Worldspace account is required

To use FireEyes, you must have a Worldspace account. If you do not already have an account, please create a Worldspace account before proceeding.

Choosing your Project

  1. Visit https://worldspacesync.net.tamu.edu.
  2. Log in with your NetID and password.
  3. Activate the Dashboards menu.
  4. Choose Project.
  5. Choose the Project associated with your site from the Project Dashboard dropdown list.

Reviewing the report data

  1. Specify a date range to filter issues according to when they were found.
  2. Activate the table headings to sort table data.
  3. Activate the issue description to see more details about that type of issue.
  4. Activate the number of issues to see a filtered table of that issue type (i.e., Issues Report).
  5. Activate the number of pages to see a filtered table of the pages where that issue occurs (i.e., Pages Report).

Additional help and resources

The Worldspace Sync product documentation provides more information on checking reports:

If you have any questions or experience problems, please contact the IT Accessibility Team.

Did you know?

  • In the United States, about 55 million people have a disability (src: 2010 U.S. Census).
  • About 1 in 5 Americans have some kind of disability (src: 2010 U.S. Census).
  • The percentage of people affected by disabilities is growing as our population ages.
  • Two popular, free screen readers are VoiceOver (Mac OS and iOS) and NVDA (Win).
  • Good accessibility practices can improve the search ranking of your website.
  • Form fields without labels can cause problems for some assistive technology users.
  • Low color contrast makes content difficult to see, especially for users with low vision.
  • Documents linked on a website need to be accessible too (e.g., PDF and Word files).
  • Audio content, like podcasts, need transcripts for deaf or hard of hearing users.
  • Online videos should be captioned for deaf or hard of hearing users.
  • Using HTML tags correctly is very important for accessibility.
  • Descriptive link text helps make a website more accessible. Avoid using "Click here" or "Read more."
  • A "screen reader" is an application that reads content aloud to a user.
  • There is no "alt tag" in HTML. "Alt" is an attribute used with the img tag.
  • HTML uses the alt attribute to provide a text description of an image.
  • Alt text should describe an image, if the purpose of the image is to convey information.
  • If an image is a link, the alt text for the image should explain where the link goes.
  • If an image is only being used for decoration, the alt text should be null (i.e., alt="").
  • If a table has headers, using header tags (<th>) will make the table more accessible.
  • An accessible website is one that can be navigated and understood by everyone.