Repository navigation
Conversation
The screen reader test for announced labels and instructions was categorized under WCAG 3.3.2, which covers the presence of visible labels — programmatic announcement is 1.3.1 (Info and Relationships). Recategorize the existing test to 1.3.1 (wording unchanged, per the issue) and add a general test for visible labels under 3.3.2 using the issue's approved wording. Include a changelog entry; its PR number gets backfilled once a PR exists. Fixes uswds#2845
| test_type: general | ||
| version_tested: 3.8.0 | ||
| wcag_criterion: 1.4.1 | ||
| - summary: Visible labels or instructions are present. |
There was a problem hiding this comment.
Small tweak here, update line 26 to Labels or instructions are present and visible.
I realize this deviates from the original issue's instructions, but I wanted to bring it a little more in line with our formatting/wording.
| version_tested: 3.8.0 | ||
| wcag_criterion: 1.4.1 | ||
| - summary: Visible labels or instructions are present. | ||
| summary_additional: There are clearly visible instructions or labels to identify what type of data is expected in the field. |
There was a problem hiding this comment.
Small tweak here, let's modify line 27 here fit a little better with our formatting: When you view a text input, you find clear, simple labels or instructions to identify the type of information expected in the field, and the format information is expected in.
I realize this deviates from the original issue's instructions, but I wanted to bring it a little more in line with our formatting/wording.
| test_type: screen_reader | ||
| version_tested: 3.8.0 | ||
| wcag_criterion: 3.3.2 | ||
| wcag_criterion: 1.3.1 |
There was a problem hiding this comment.
Small nitpick here, now that the number changed, let's bump this to the top of the screen reader section so that the criterion ordering is sequential.
Summary
Recategorized a text input accessibility test under the correct WCAG criterion and added the missing visible-labels test, using the wording the accessibility audit supplied.
Related issue
Closes #2845
Problem statement
On the Text input accessibility tests page, the screen reader test "Screen reader announces field labels and instructions" was filed under WCAG 3.3.2 (Labels or Instructions). But 3.3.2 covers whether visible labels and instructions exist — what a screen reader announces is programmatic markup, which is WCAG 1.3.1 (Info and Relationships). This was an accessibility audit finding, and the audit spelled out the exact fix.
Solution
Two changes to
_data/accessibility-tests/text-input.yml, following the issue's instructions exactly:Also added a changelog entry to the Text input accessibility tests page. The new test's "version tested" follows the file's existing convention (3.8.0, matching all sibling entries); the team may prefer the currently-bundled version instead — happy to adjust.
Testing and review
bundle exec rspecpasses (10 examples, 0 failures).