Skip to content

508-defect-4: Fieldset and legend pairing isn't needed on step 1 #22849

Open
@joshkimux

Description

@joshkimux

508-defect-4

Feedback framework

  • ❗️ Must for if the feedback must be applied
  • ⚠️ Should if the feedback is best practice
  • ✔️ Consider for suggestions/enhancements

Definition of done

  1. Review and acknowledge feedback.
  2. Fix and/or document decisions made.
  3. Accessibility specialist will close ticket after reviewing documented decisions / validating fix.

Point of Contact

VFS Point of Contact: Josh

Details

The fieldset and legend "Veteran Information" below the h2 "Veteran Information" isn't necessary. The

element is meant to group parts of an HTML form, like addresses, dates, or radio/checkbox selections.

Eeach of the fields on the Veteran Information page are independent and understandable on their own (barring dates, which already is contained within a fieldset), so it's ok to remove.

In fact, the current implementation won't make most of the accessibility benefits a fieldset/legend pairing can provide since the legend here is not the direct child of the fieldset.

Acceptance Criteria

  • Remove the fieldset and legend "Veteran Information"

Steps to Recreate

Step 1 of 4: Veteran Information

Proposed Solution

Remove the fieldset and legend "Veteran Information"

WCAG or Vendor Guidance (optional)

Using the fieldset and legend elements.)

Screenshots or Trace Logs

Screen Shot 2021-04-07 at 12 24 40 PM

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    a11y-defect-4Low-severity accessibility issue that should be fixed within 2 - 4 sprintsaccessibility

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions