You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The unordered list markup for each form controls is read by screen readers as (with some differences in naming lists for every screen reader):
list item 1
list item Search Groups ellipsis
// content addressed in upcoming ticket
list item end
list item 1
list item Order by: ...
// content addressed in upcoming ticket
list item end
There's only one item listed in each of the two lists in #subnav-filters, so let's remove the extra noise. Fortunately, <div>s and <span>s are not read by screen readers except those with ARIA roles/landmarks. Alternative wrapper:
There is also a second item in the first up so in some senses this is a list as we have a search element and feed link.
Unpicking this has to be done through three points index files, search include and filters include, suggests really that the index file markup would be better moved to it's own include really to enable work on one single file.
One thing I'm worried about is losing semantic markup e.g a list over simply aggregating non-semantic elements 'divs' 'spans' however going to try unpicking this and creating a new include file to handle all uses of thse elements.
Per note in #117: We currently have the following markup for div#subnav-filters:
The unordered list markup for each form controls is read by screen readers as (with some differences in naming lists for every screen reader):
There's only one item listed in each of the two lists in #subnav-filters, so let's remove the extra noise. Fortunately,
<div>s
and<span>s
are not read by screen readers except those with ARIA roles/landmarks. Alternative wrapper:The text was updated successfully, but these errors were encountered: