E-mail List Archives
Re: WCAG2 and vertical bars (|)
From: Birkir R. Gunnarsson
Date: Apr 28, 2015 8:57AM
- Next message: Dawn.Igoe@wellsfargo.com: "JAWS Reading Comments in HTML Emails"
- Previous message: Lynn Holdsworth: "WCAG2 and vertical bars (|)"
- Next message in Thread: Bourne, Sarah (ITD): "Re: WCAG2 and vertical bars (|)"
- Previous message in Thread: Lynn Holdsworth: "WCAG2 and vertical bars (|)"
- View all messages in this Thread
Lynn
I don´t thin 1.1.1 applies here .. the only one that mentions ascii
art, see H86:
http://www.w3.org/TR/WCAG20-TECHS/H86.html
You could go with 2.4.4 or 3.3.2 (link text/labels) and explain that
inserting characters for visual effect but without meaning makes the
text of link or label of buttons harder to understand for screen
reader users.
Propose to use an image with empty alt or a background icon to achieve
the same purpose without disrupting screen reader users.
This one is borderline, I would not always call it as a violation of
WCAG, though I would usually include it in a best practice
recommendation.
On 4/28/15, Lynn Holdsworth < <EMAIL REMOVED> > wrote:
> Hi all,
>
> Under WCAG2, is there any way to fail techniques that use characters
> for visual effect, such as inserting vertical bars to separate items
> in a menubar, or tacking angle brackets on to "Previous" and "Next"
> links to act as arrows?
>
> Thanks as always, Lynn
> > > > >
--
Work hard. Have fun. Make history.
- Next message: Dawn.Igoe@wellsfargo.com: "JAWS Reading Comments in HTML Emails"
- Previous message: Lynn Holdsworth: "WCAG2 and vertical bars (|)"
- Next message in Thread: Bourne, Sarah (ITD): "Re: WCAG2 and vertical bars (|)"
- Previous message in Thread: Lynn Holdsworth: "WCAG2 and vertical bars (|)"
- View all messages in this Thread