WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: best practices in accessibility coding questions

for

From: Sean Murphy
Date: Sep 26, 2017 5:02PM

No i am not saying list views should not be used Rather use the examples from the ARIA best practice site

My experience is the part

> On 27 Sep 2017, at 5:33 am, Sarah Ferguson < <EMAIL REMOVED> > wrote:
>
> So Sean, I feel like you are advocating not to make menus lists. this page
> from Jennifer say TO make them lists...I'm not sure why though.
>
> https://www.w3.org/WAI/tutorials/menus/structure/
>
> Sarah Ferguson
> Web Accessibility Specialist
> Department of Digital Communications
> Brandeis University *|* 781.736.4259
> www.brandeis.edu/web-accessibility
>
>
>> On Tue, Sep 26, 2017 at 10:28 AM, Sarah Ferguson < <EMAIL REMOVED> > wrote:
>>
>> Thanks, Jennifer and Sean. No worries, if I get no response to Q2, I will
>> repost it ;)
>>
>> Sarah
>>
>>
>> On Mon, Sep 25, 2017 at 10:40 PM, Jennifer Sutton < <EMAIL REMOVED> >
>> wrote:
>>
>>> Continuing to focus on the menuing question (and I do hope others will
>>> help with the other one, too):
>>>
>>>
>>> I would recommend the WAI Education and Outreach Tutorial on Menus,
>>> starting here:
>>>
>>> http://www.w3.org/WAI/tutorials/menus/
>>>
>>>
>>> I don't recommend that folks spend time handling screen reader quirks --
>>> one does something one way and one another. It's much better to code to
>>> specifications. Perfection is the enemy of good, and it's expensive, too!
>>>
>>>
>>> Trying to make all screen reader and browser combos act the same is the
>>> same as trying to replicate exactness across browsers, or replicate print
>>> presentation on the web. Unless functionality is outright not available,
>>> slight variants isn't a big deal, in my view.
>>>
>>>
>>> Screen readers function differently -- sometimes that's a feature, and
>>> sometimes it's a bug, but I see a lot of people in this industry driving
>>> themselves crazy with this sort of thing. And I personally don't think it's
>>> the most sensible use of people's time/best bang for buck.
>>>
>>>
>>> Now, how about the second question, if nobody has anything else on this
>>> menu one?
>>>
>>>
>>> I always worry about posts with several questions in them. They're hard
>>> to find in archives, and they can get lost in long rambling responses, like
>>> mine!
>>>
>>>
>>> Best,
>>>
>>> Jennifer
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>>>> Behalf Of Sarah Ferguson
>>>> Sent: Tuesday, 26 September 2017 8:04 AM
>>>> To: WebAIM Discussion List < <EMAIL REMOVED> >
>>>> Subject: [WebAIM] best practices in accessibility coding questions
>>>>
>>>> I have a couple of questions from our developer that I could not answer.
>>>> Any thoughts?
>>>>
>>>>
>>>> - Quotes:
>>>>
>>>> We have a large, stylized quotation mark to signal a pull quote on some
>>>> pages. At the moment we have it marked up as a quotation in the code. Our
>>>> developer asks, "
>>>> would it be equally acceptable to include the curly quote (&#8220;) in
>>>> the HTML and style that with CSS?"
>>>>
>>>>
>>>> - In our menus (left nav, top menu, and hamburger menu) on one of our
>>>> sites, VO is reading "1 item" for each menu, because it considers
>>>> each 1
>>>> list of X number of items. On other sites, it reads the number of
>>>> items in
>>>> the "list" instead. I would think the latter is more helpful, as the
>>>> user
>>>> will want to know how many items s/he will be encountering. I've
>>>> also heard
>>>> that the menu must be marked as a list. How would we go about both
>>>> marking
>>>> it as a list and having VO say the number of items in the list? Our
>>>> developer is able to do one or the other. Also, is this the approach
>>>> you
>>>> could recommend or do you have alternatives?
>>>>
>>>>
>>>> Thanks!
>>>> Sarah
>>>> >>>> >>>> archives at http://webaim.org/discussion/archives
>>>> >>>>
>>>> >>>> >>>> >>>> >>>>
>>>
>>> >>> >>> >>> >>>
>>
>>
> > > >