frame-tested

Description

The frame-tested rule requires you to ensure that your accessibility scanning tool processes the content of all <frame> and <iframe> elements. These elements load separate web pages. If you do not include this embedded content in your scan, your accessibility report will be incomplete, and you will miss potential barriers for users of assistive technology.

The rule aligns with WCAG Success Criterion 4.1.2 (Name, Role, Value).

Examples

In the following example, the <iframe> element is missing a descriptive title attribute. While the frame is present, the lack of an accessible name may cause the scanning tool or assistive technology to ignore or misinterpret the element, violating the principle of ensuring it is “tested.”

In the following corrected example, you provide a descriptive title attribute. This gives the <iframe> a meaningful accessible name, ensuring the element is identifiable and included in accessibility testing:

How to fix

To fix violations of the frame-tested rule, follow these steps:

• Provide an Accessible Name: Add a descriptive title attribute to every <frame> and <iframe> element. The value of the title attribute should clearly describe the frame’s content or purpose.

• Verify Tool Settings: Check the configuration of BrowserStack Accessibility testing. Ensure that you have set the tool to traverse and scan the document object model (DOM) within all found <frame> and <iframe> elements.

• Ensure Embedded Content is Compliant: Verify that the web page loaded within the frame’s src attribute is itself fully accessible and compliant with all relevant accessibility standards.

Reference

• WCAG Success Criterion 4.1.2: Name, Role, Value