E-mail List Archives

Re: WCAG2 and vertical bars (|)

for

From: Andrew Kirkpatrick
Date: Apr 30, 2015 6:03AM


Jon,
I was just looking at this also. I think that we need to update F26. The example strikes me as a 1.1.1 example, and the test procedure doesn't match up with the example either.

The example says " A shopping cart uses two simple glyphs to indicate"
The test procedure says " Examine the page for non-text marks that convey information."

Even the procedure says " The objective of this technique is to show how using a graphical symbol to convey information can make content difficult to comprehend. A graphical symbol may be an image, an image of text or a pictorial or decorative character symbol (glyph) which imparts information nonverbally." which is at odds with the procedure.

So in short, I agree that this needs a look.
AWK

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jonathan Avila
Sent: Wednesday, April 29, 2015 9:02 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] WCAG2 and vertical bars (|)

> F26: Failure of Success Criterion 1.3.3 due to using a graphical
> symbol alone to convey information

It seems odd that this failure is listed under SC 1.3.3 because 1.3.3 appears to apply to instructions only. I would think this could fall under SC 1.1.1 Non-text Content as well. Not all uses of sensory information are instructions either although a button's label could be considered instructions I suppose

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>

703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Bourne, Sarah (ITD)
Sent: Wednesday, April 29, 2015 4:06 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] WCAG2 and vertical bars (|)

That would be a failure under 1.3.3 - see F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information (http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140916/F26 ) " The objective of this technique is to show how using a graphical symbol to convey information can make content difficult to comprehend. A graphical symbol may be an image, an image of text or a pictorial or decorative character symbol (glyph) which imparts information nonverbally. Examples of graphical symbols include an image of a red circle with a line through it, a "smiley" face, or a glyph which represents a check mark, arrow, or other symbol but is not the character with that meaning."

The key part here is the use of a symbol that means something different, for instance, the symbol > means "greater than" not "next".

1.3.3 is level A.

sb
Sarah E. Bourne
Director of IT Accessibility, MassIT
Commonwealth of Massachusetts
1 Ashburton Pl. rm 1601 Boston MA 02108
617-626-4502
<EMAIL REMOVED>
http://www.mass.gov/MassIT


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
Sent: Tuesday, April 28, 2015 10:57 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] WCAG2 and vertical bars (|)

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
> > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.