This test page was created to validate the behavior of some WorldSpace rules as they are being considered for inclusion in State Farm's ADA rule set.
Checking the rule: "Ensure that the alt attribute for active images is not empty or blank". (SC 1.1.1 - Non-text Content) We want to make sure that an image with null alt and visible text within the same anchor does NOT throw an issue.
I am a Triangle
Results: FireEyes does not throw an error. This is the expected / desired result.
Checking the rule: "Identify the text that should have been marked as caption (H39) - Text of first row that spans the width of table should be marked up as caption. A table with the first row used to include a visual caption." (SC 1.3.1 Info and Relationships) We want to determine if a "Moderate" priority is sufficient. If the spanned row causes a screen reader to not be able to interpret the rest of the table structure, this priority may be elevated. In the table below, the first row spans all of the columns and contains what should be a visual caption above the table, the second row contains column headers, and the first column contains row headers.
| This is an improper caption | |||
| Name | 1 mile | 5 km | 10 km |
|---|---|---|---|
| Mary | 8:32 | 28:04 | 1:01:16 |
| Betsy | 7:43 | 26:47 | 55:38 |
| Matt | 7:55 | 27:29 | 57:04 |
| Todd | 7:01 | 24:21 | 50:35 |
Results: This table does throw and error as expected. The table reads fine in NVDA / FF. HOW DOES IT READ in VO???
Checking the rule: "Check for use of "rowspan" attribute in tables - Using rowspan within a table makes the cell's content inaccessible to users of assistive technology." (SC 1.3.2 - Meaningful Sequence) We want to validate that this rule does not throw an issue when rowspan is used in a properly coded data table containing compound header cells.
| Females | Males | |||
|---|---|---|---|---|
| Mary | Betsy | Matt | Todd | |
| 1 mile | 8:32 | 7:43 | 7:55 | 7:01 |
| 5 km | 28:04 | 26:47 | 27:27 | 24:21 |
| 10 km | 1:01:16 | 55:38 | 57:04 | 50:35 |
Results: This rule DOES throw an error. This is NOT desired since this table is coded according to a11y guidelines.
Checking the rule: "Check for use of "rowspan" attribute in tables - Using rowspan within a table makes the cell's content inaccessible to users of assistive technology." (SC 1.3.2 - Meaningful Sequence) We want to validate that this rule does throw an issue when rowspan is used in a layout table containing rowspan.
A layout (has role=presentation and no th) table with rowspan
| Header Area | ||
| Navigation Area | Content Section 1 | Sidebar Area |
| Content Section 2 | ||
| Footer Area | ||
Results: This table does NOT throw an error. This is not the expected result.
Checking the rule: "Check for title attribute to identify form controls when the label element cannot be used (H65)" (SC 1.3.1 Info and Relationships) We want to know if aria-label will be accepted as a label in addition to title the title attribute.
Results: This does not throw and error. This is the expected / desired result.
Checking the rule: "Check for title attribute to identify form controls when the label element cannot be used (H65)" (SC 1.3.1 Info and Relationships) We want to verify that implicit (wrapped) labels are accepted in addition to explicit (label / for / id) labels.
Results: This does not throw and error. This is the expected / desired result.