Using Accessibility Tools on the Career Site

Objective

After completing this lesson, you will be able to use accessibility tools to test specific aspects of the career site.

Supporting Software Applications

Screen readers are software programs that convert digital text into synthesized speech. They allow blind or visually impaired users to read the text that is displayed on the computer screen. Screen readers announce the page title (the <title> element in the HTML markup), headings, links, and the alt text (description) for images. To get an overall impression of a page's content, users can jump from heading to heading, from link to link, and from paragraph to paragraph.

Accessibility tools, such as WAVE (https://wave.webaim.org), will flag accessibility issues on websites, but cannot tell you if web content is accessible. Only a human can determine true accessibility. Tools will flag certain accessibility errors and warnings, but, for example, cannot detect embedded text on images.

The WAVE Summary View presents your page with embedded accessibility icons and indicators.

  • Red icons indicate accessibility errors that need to be fixed.
  • Yellow icons indicate alerts to possible issues.
  • The other icons and indicators highlight other elements about the site.
A screenshot of the WAVE summary view

From the Details tab, you can click on an icon to view the item on the page.

A screenshot showing an icon selected under Details, which opens a page with more information about the issue, that is, low contrast of color.

Reference View displays an explanation of the element you're viewing.

A screenshot of the Reference view with details about the issue, that is, low contrast color

The related code displays at the bottom of the page.

A screenshot of the related code

No Styles view is very useful to access errors and alerts for complex career sites or sites with fixed headers. Turning off Styles displays your page with tables linearized. This view presents the underlying reading and navigation order, the order in which keyboard-only and screen reader users will access the page.

A screenshot of the No Styles view

Contrast View shows only contrast issues on your page, based on WCAG 2.0 guidelines. You can use the tools in the panel to change the color contrast until it receives a 'pass' report, and take note of the updated colors that meet these guidelines, to change the site.

A screenshot of Contrast view with pass and fail reports

The Structure tab displays the headings on the page.

A screenshot of the Structure page

Accessibility

Many parts of the world adhere to accessibility laws. For example, in Canada, private, public, and non-profit organizations with 50+ employees must ensure that their websites are accessible. Web Content Accessibility Guidelines (WCAG) is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a single shared standard for web content accessibility that meets the needs of individuals, organizations, and governments internationally. The WCAG documents explain how to make web content more accessible to people with disabilities: https://www.w3.org/WAI/standards-guidelines/wcag/ Each guideline has three levels of accessibility: A, AA and AAA.

WCAG version 2.2 is the latest published version of the WCAG guidelines: https://www.w3.org/TR/WCAG22/. The publication of WCAG 2.2 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. The use of WCAG 2.2 is recommended to maximize future applicability of accessibility efforts.

Accessibility guidelines in the United States require federal agencies to develop, procure, maintain, and use information and communications technology (ICT) that is accessible to people with disabilities - regardless of whether or not they work for the federal government. See Section 508 of the Rehabilitation Act: https://www.section508.gov/manage/laws-and-policies/https://www.section508.gov/manage/laws-and-policies/.

Tips for testing websites for accessibility

There are a number of ways to know if your website is accessible:

  1. Automatic assessment and assistive technology: For example, you can review your site using assistive technology, such as a screen reader, to make sure the design and technical aspects of the site are accessible.
  2. User testing and feedback: If possible, ask people with disabilities to test your site. Get feedback from customers and other site users to find out if there are any improvements needed.
  3. Review key milestones and changes: Keep a record of the accessibility issues that have been repaired, or ask your web developer to maintain such a record. This will show you the completed work and the new level of accessibility. It will also be helpful if your organization is asked to show that your website follows WCAG 2.1 guidelines.
  4. Online accessibility checker: You can use an online tool to check if your website is accessible. Using an online accessibility checker does not guarantee that you will find all accessibility issues with your website. It is important to have a person review the site as well.

Summary

  • Accessibility is guided by laws and standards: Many regions require accessible websites (e.g., Canada’s requirements for organizations with 50+ employees; U.S. federal ICT requirements under Section 508). The global standard is WCAG, with compliance levels A, AA, AAA; WCAG 2.2 is the latest and is recommended for future-proofing.
  • Use multiple methods to evaluate accessibility: Combine assistive technology checks (e.g., testing with a screen reader), user testing and feedback from people with disabilities, and tracking/fixing issues over time to document improvements and demonstrate guideline alignment.
  • Automated tools help, but humans confirm true accessibility: Online checkers and tools like WAVE can flag errors/alerts (e.g., red = errors, yellow = alerts) and provide views like Summary, Details/Reference, No Styles (reading order), Contrast, and Structure (headings)—but they can’t catch everything (such as meaningfulness of content or some text embedded in images).