This issue only occurs when rendering a document that has two different fields with the same value. An example is this record in a Geoblacklight instance, which has the same organization as its creator and publisher.
The output of the LinkToFacet rendering step uses the field value as the link text, so this will create two different links on the page with the same text, but pointing to different searches since they are faceting on different fields.
This is an accessibility issue for screen reader users, because the links can be presented out-of-context in a menu where they will not be able to be distinguished.
Sighted users can use the context of the nearby field name in a <dt> to distinguish the purpose of the two links, but non-sighted users may need additional context added to the accessible name for the link.
This issue only occurs when rendering a document that has two different fields with the same value. An example is this record in a Geoblacklight instance, which has the same organization as its creator and publisher.
The output of the
LinkToFacet
rendering step uses the field value as the link text, so this will create two different links on the page with the same text, but pointing to different searches since they are faceting on different fields.This is an accessibility issue for screen reader users, because the links can be presented out-of-context in a menu where they will not be able to be distinguished.
Sighted users can use the context of the nearby field name in a
<dt>
to distinguish the purpose of the two links, but non-sighted users may need additional context added to the accessible name for the link.