WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: best practices in accessibility coding questions

for

From: Sarah Ferguson
Date: Sep 26, 2017 3:57PM

I sent the previous feedback to our developer and she was not using menu
item, so she has some playing around to do.

thanks, I will send this along, as well.

So, Birkir, you are saying the curly quote won't be recognized as a
quotation mark? Does the curly quote read as *special character*?

thanks

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 5:36 PM, Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:

> The answer to your first question is technically no. WCAG 1.3.1 says
> that if something is communicated visually it must also be available
> programmatically or in text. By using a symbol that is not a quotation
> mark but style it like a quotation mark visually you are breaking that
> success criteria.
> It´s not the end of the world serious, and you could do a clumsy
> screen reader text, like <span aria-label="Quote">tye sumbol</span>
> For the second, it sounds like you are not hiding the <li> elements
> between a menu and menuitem.
> <ul role="menu">
> <li><a href="#" role="menuitem">menu item 1</a></li>
> ...
> </ul
>
> This would be announced by voiceover as "1 of 1" for every menuitem in the
> menu.
> If you add role="presentation" to the <li> element Voiceover should
> announce the menu as expected.
> I haven't seen the code, so I maybe wrong, but this is the most common
> cause for screen readers announcing (1 of 1) in menu constructs.
>
>
>
> On 9/26/17, Lovely, Brian (CONT) via WebAIM-Forum
> < <EMAIL REMOVED> > wrote:
> >
> >
> >