Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #1423154

    Hi

    I have a site at https://oxwestg.wpenginepowered.com/ – username and password below.

    On a couple of pages I am using an image gallery – see https://oxwestg.wpenginepowered.com/why-here/local-character/

    Unfortunately, this element creates an accessibility error when the page is run through an accessibility checker (Silktide). The error is:

    ——————————————————————————

    Write lists or groups of links semantically
    WCAG 2.0 A 1.3.1

    Lists of related items should be written semantically as a list.

    Usually this means rewriting these to use the

      or

        tags.

        This allows assistive technologies to more easily navigate from item to item, or past entire groups of links if the user wants to.

        ——————————————————————————

        Does anyone have any ideas on how to fix this and apply to a child theme?

        Thanks in advance

        Dominic

    #1423327

    Hi all – any thoughts?

    #1423978

    Hi,
    Thank you for your patience, your question seems to be about the masonry image gallery giving an error for “list items” since I’m not able to access this report or the tool, I assume that the tool is referring to a “li” on your page, but the only “li” I find is in the timeline element, perhaps this is the element your report is referring to?
    If so I’m not sure what the report means by “semantically as a list”, I tried Googling this but didn’t find an explication of the expected results.
    Please check if this is referring to the timeline element and explain what the expected results would be.
    I note that the timeline element is not a normal “list item” so I’m not sure that we can change the element to something else like a “div” very easily, if that is wahat the solution will be.

    Best regards,
    Mike

    #1424050

    Hi Mike

    I think the error is suggesting the opposite. The masonry gallery is currently divs and the error suggests it should be

  • .

    Does that help?
    TIA
    Dominic

#1424056

Hi,
Unfortunately I’m not sure why your report would assume that an element should be a li instead of a div, perhaps it is a flaw in the report?
It doesn’t seem practical to change the masonry gallery into a li element

Best regards,
Mike

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.