TCPA.com

The law behind
the conversation.

Search/ The TCPA Brief

Policy

Accessibility

On this page

We aim to make TCPA.com accessible to everyone, including people who use screen readers, keyboard navigation, magnification, captions or other assistive technology.

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.2 is the current version of the guidelines.

What we do

  • Structure. Every page uses standard HTML landmarks (header, navigation, main content and footer), one main heading and headings in order, so screen reader users can move through a page by section.
  • Keyboard access. The site is designed to work with a keyboard. A "Skip to content" link is the first item on every page, focus is always visible, and the menu on small screens opens with Enter or Space and closes with Escape.
  • Color and contrast. Text and controls are designed to meet WCAG Level AA contrast ratios, and color is never the only way information is shown.
  • Zoom and small screens. Text can be enlarged, and pages reflow to a width of 320 CSS pixels without scrolling sideways. Wide tables scroll inside their own labeled area.
  • Motion. The site has no autoplaying video, carousels or timed content, and it follows your device's reduced-motion setting.
  • Forms. Every form field has a visible label, and form messages are announced to screen readers.
  • Images and icons. Images have text alternatives, and purely decorative marks are hidden from assistive technology.
  • Plain pages. Articles, guides and case pages are plain HTML that can be read without JavaScript. The site loads no web fonts.

How we test

We tested every type of page on the site (27 page templates) with axe-core 4.10, an automated accessibility checker, against the WCAG 2.0, 2.1 and 2.2 Level A and AA rules. The tests found two contrast problems, on a decorative symbol on the home page and on the unused letters in the glossary's A to Z bar, and we fixed both. A repeat test found no violations. On the same day we checked by hand that every page type reflows at 320 CSS pixels, that keyboard focus is visible and starts with the skip link, and that the mobile menu works with a keyboard.

Automated tools can't catch every problem. We have not yet had an independent accessibility audit or testing by people who use screen readers every day. Based on our own testing, we believe the site substantially meets WCAG 2.2 Level AA, and we will keep testing as we add pages.

Compatibility

TCPA.com is built with standard HTML and CSS and a small amount of JavaScript, and it is designed to work in current versions of major web browsers and with common screen readers. Our testing so far has been in Chromium-based browsers, such as Google Chrome and Microsoft Edge.

Writing for clarity

Our content is written in plain English. We spell out the name of each agency, such as the Federal Communications Commission (FCC) and the Federal Trade Commission (FTC), with its acronym on first use, and legal terms are explained in our glossary.

Documents from other sources

Many of our web pages include links to documents published by courts and government agencies, such as opinions and orders published as PDFs. We are unable to control how these documents are presented and some may not be fully accessible with assistive technologies. If you need a source in a different format, contact us and we will try to help, or check the official website for an accessible version.

Known limitations

  • Site search needs JavaScript. If search doesn't work for you, every page can be reached through the menu, the topic pages and the site directory.
  • The home page filters need JavaScript. The filter buttons above the latest articles don't work without it. The full list is always available on Latest analysis.
  • Documents from other sites. Court and agency documents we link to are not ours, and some may not be accessible. See "Documents from other sources" above.

Feedback and help

If you have trouble using any part of this website, please let us know through our contact form. Include the page address and a description of the problem, and tell us if you need information in a different format.

Sources