WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: To "Bullet" or not to "Bullet", that is the question

for

From: Liko, Todd
Date: Jun 6, 2014 6:14AM

On our website, we have lists that appear horizontally. Granted, in appearance, they do not look like lists, but semantically they are lists.

I lean to the side they should be coded as lists. Whether it is a table of contents or a menu, it is still a list of items and as a few have already mentioned, it is useful to know how many items are in the list.

Todd.

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Jon Avila
Sent: Thursday, June 05, 2014 4:09 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] To "Bullet" or not to "Bullet", that is the question

I personally think adding list structure to items that don't appear as a list can be counter productive. It adds a lot of extra speech for screen reader users. With the nav element and role we have a better way to group links. Authors jumped on this trend and many times the trade off on extra speech is not worth the benefit e.g. I see lists with one two and three items in them and I see many horizontal lists. VoiceOver for me on iOS has a bug where read to the end will stop on bullets which can be frustrating.

Jonathan

> On Jun 5, 2014, at 3:57 PM, Pratik Patel < <EMAIL REMOVED> > wrote:
>
> You can choose to remove the bullets by using css. I would still recommend keeping the semantic meaning of the list so that the user gets the benefit of knowing the number of items in a menu. In many ways, this follows convention that the user is used to on desktop apps.
>
> Regards,
>
> Pratik
>
>
> Pratik Patel
> Founder and CEO, EZFire
> T: 888-320-2921
>
> Please support our crowd funding campaign to develop comprehensive
> accessibility training. Visit http://tinyurl.com/a11ytv
>
> Sent from my iPhone
>
> On Jun 5, 2014, at 3:20 PM, Jared Smith < <EMAIL REMOVED> > wrote:
>
> On Thu, Jun 5, 2014 at 1:04 PM, Druckman,Geri wrote:
>
>> To me the latter sounds much cleaner, and to the point. What is your opinion?
>
> I think there is some benefit to the user knowing that it is a list of
> items and how many items are present (knowing there are 3 items as
> opposed to 21 might influence if/how the user navigates or listens to
> them). But there's really not a notable difference between either
> approache.
>
> Jared
> > > list messages to <EMAIL REMOVED>
> > > list messages to <EMAIL REMOVED>