Broken ARIA references Image List Content Type in CMS

[laflannery]

Describe the defect

Within the edit screens on the Image List content type, there are multiple aria-describedby attributes that do not correspond to an ID anywhere on the page.

• Page Introduction
• Calls to Action
• VA Benefits Hubs
• Related Information
• Phone number within Contact information
• Other Categories where people may look for this article

AC / Expected behavior

• [ ] Determine what the original intention of the ARIA reference was/is. What additional context was it providing? Do we still need to provide that information in some other way?
• [ ] UX to determine display of additional information if it is determined this is needed
• [ ] Update attribute based on above determination (remove attribute or update it)
• [ ] Accessibility review

Screenshots

Screenshot of the Page Introduction field error from AMP plugin. The aria-describedby attribute is pointing to something with the ID edit-field-intro-text-limited-html-0--description but if I search for that ID I can't find it anywhere on the page, it doesn't exist.

Screenshot of where the attribute is on the <div>

Accessibility Standard

WCAG version 2.0 A, Criterion 1.3.1

Team

Please check the team(s) that will do this work.

• [ ] CMS Team
• [ ] Public Websites
• [ ] Facilities
• [ ] User support
• [ ] Accelerated Publishing

[laflannery]

I put the CMS label as a placeholder cause I'm not sure who this belongs to

[laflannery]

@EWashb (or maybe @jilladams) are you able to tell me who owns Checklist, I can't tell from this mural who should be assigned this ticket

[jilladams]

Great question that I also need to ask from a different ticket today. For reference: there are ~2~ 6 checklist nodes in the whole CMS, both in draft. I suspect DaveC knows the history, but I'll give Erika first right to opine about ownership, before pulling him in. ;)

[EWashb]

I found 6 checklists in draft right now and they are all tied to Resources and Support content. I don't have the historical context of the intent of this content type, but I would agree that if they only exist currently within a PW product, that they are a PW product. I am open to conversation if folks feel otherwise. @jilladams @laflannery

[laflannery]

I saw a convo in slack that led me to putting this under PW ownership

[FranECross]

@laflannery We don't feel we'll be able to answer these questions/AC (below). Are you able to instead provide recommendations on what should be done?

• Determine what the original intention of the ARIA reference was/is. What additional context was it providing? Do we still need to provide that information in some other way?
• UX to determine display of additional information if it is determined this is needed