CUNY Academic Commons

One of the items from the accessibility audit (instance ID 510186-01) mentions the links under the profile image on a user's CV:

The list of links under the image are visually an unordered list but is not marked up as an unordered list.

When content is presented as an unordered list, or a clearly related collection of items not intended to be read in a specific order, marking it up using semantic unordered list HTML elements helps assistive technology users to navigate and orient themselves within a page of content. Screen reader users can navigate to (or over) unordered lists when they are correctly marked up. Also, when reading content in an unordered list, assistive technology provides rich information about how long the list is and where the user is in the list.

Note: In cases where semantic markup can't be used, role=""list"" may be added to a non-semantic containing element and role=""listitem"" to each item element to provide the correct list semantics.

Note: Be aware that in situations where a list has been styled to not appear visually as a list, e.g., by applying CSS such as list-style: none, the Safari browser may remove list element semantics, and those semantics will not be announced by VoiceOver. This is a reaction to the over-use of the list element to structure content without wanting it to appear to be a list. Adding role=""list"" to an <ul> and role=""listitem"" to each <li> should ensure VoiceOver announces the correct semantics but consideration should be given as to whether the content should then be structured as a list at all."

The links the audit refers to are the cv-shortlink and the cv-profile-navigation blocks: https://github.com/cuny-academic-commons/cac/blob/a3e0d045ff2da3f11981d0d74026152561d578f4/wp-content/plugins/cac-cv-editor/includes/data-default-template.html#L6-L8. It looks like we could alter the get_block_html() functions for these blocks to switch the markup to list-items, but the <ul> wrapper would need to be added to each CV's post.

Jeremy, do you think it would be possible to do a similar filter approach like you did in #25349 for the <ul>? The alternative is using the role="list" / role="listitem" approach instead of switching to <ul> / <li>, but this would also require markup changes in the CV post.