E-mail List Archives
Re: best practices in accessibility coding questions
From: Birkir R. Gunnarsson
Date: Sep 26, 2017 3:36PM
- Next message: Sarah Ferguson: "Re: best practices in accessibility coding questions"
- Previous message: Sarah Ferguson: "quotes and css"
- Next message in Thread: Sarah Ferguson: "Re: best practices in accessibility coding questions"
- Previous message in Thread: Lovely, Brian (CONT): "Re: best practices in accessibility coding questions"
- View all messages in this Thread
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:
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Sarah Ferguson
> Sent: Tuesday, September 26, 2017 3:33 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] best practices in accessibility coding questions
>
>>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.
>
> Sarah, a menu can be based on a list, but will announce as a menu if the
> correct roles are applied.
>
> <ul role="menubar">
> <li tabindex="-1" role="menuitem">About Us</li>
> <li tabindex="-1" role="menuitem">About You</li>
> </ul>
>
> Note that in this example it is assumed that JavaScript will be used to make
> the menu behave as expected. You can refer to the WAI-ARIA Authoring
> Practices for more information:
> https://www.w3.org/TR/wai-aria-practices-1.1/#menu
>
>
>>Sarah Ferguson
>>Web Accessibility Specialist
>>Department of Digital Communications
>>Brandeis University *|* 781.736.4259
>>www.brandeis.edu/web-accessibility
>
>
>
> >
> The information contained in this e-mail is confidential and/or proprietary
> to Capital One and/or its affiliates and may only be used solely in
> performance of work or services for Capital One. The information transmitted
> herewith is intended only for use by the individual or entity to which it is
> addressed. If the reader of this message is not the intended recipient, you
> are hereby notified that any review, retransmission, dissemination,
> distribution, copying or other use of, or taking of any action in reliance
> upon this information is strictly prohibited. If you have received this
> communication in error, please contact the sender and delete the material
> from your computer.
> > > > >
--
Work hard. Have fun. Make history.
- Next message: Sarah Ferguson: "Re: best practices in accessibility coding questions"
- Previous message: Sarah Ferguson: "quotes and css"
- Next message in Thread: Sarah Ferguson: "Re: best practices in accessibility coding questions"
- Previous message in Thread: Lovely, Brian (CONT): "Re: best practices in accessibility coding questions"
- View all messages in this Thread