E-mail List Archives
Thread: Expanding awareness WVAG
Number of posts in this thread: 4 (In chronological order)
From: allyssa jessicon
Date: Wed, Apr 07 2021 7:44AM
Subject: Expanding awareness WVAG
No previous message | Next message →
Hi,
I would like to know if someone has a resource or idea wjere I can educate
myself to understand the difference between 1.3.1 info and relationship and
4.1.2 Name, role, value? Any help would be greatly appreciated.
Regards,
Allyssa.
From: Laura Fathauer
Date: Fri, Apr 09 2021 11:44AM
Subject: Re: Expanding awareness WVAG
← Previous message | Next message →
Hi-
They both deal with programmatic equivalents. 1.3.1 looks at all content,
whereas 4.1.2 applies only to user interface components. There can be
overlap (see failure F42; also in cases where the information is about form
fields such as a question for a group of form fields). 1.3.1 looks at any
relationships between elements that is conveyed visually (tables). 1.3.1
also covers other information conveyed visually, so for example if you have
a weighted word cloud where words used more often are bigger/bolder, that
is visual information that needs to have a way the information is provided
programmatically. 4.1.2 explicitly references changes in the state of user
interface components (open/closed, etc).
Laura
On Wed, Apr 7, 2021 at 9:44 AM allyssa jessicon < = EMAIL ADDRESS REMOVED = >
wrote:
> Hi,
>
> I would like to know if someone has a resource or idea wjere I can educate
> myself to understand the difference between 1.3.1 info and relationship and
> 4.1.2 Name, role, value? Any help would be greatly appreciated.
>
>
> Regards,
> Allyssa.
> > > > >
From: Guy Hickling
Date: Fri, Apr 09 2021 12:40PM
Subject: Re: Expanding awareness WVAG
← Previous message | Next message →
SC1.3.1 applies to all content on screen. Put simply, it says that anything
that is presented visually must also be marked up in a way that allows
assistive technology to understand that visual presentation. So it covers
headings, lists, buttons, input fields, everything. That enables screen
readers and other devices to announce what is presented. (It's a rather
vague SC, since people can differ in their interpretation of what is being
presented, but that is the basic principle.)
In contrast, SC4.1.2 applies specifically to interactive components, not to
static content. But I would say that, yes, it basically says the same as
1.3.1. It just does so much more explicitly. It picks out the various
aspects of interactive components in more detail and reinforces the
requirement that all those aspects must be conveyed, in the markup, to
assistive technology.
So seeing a text label over an input field, for example, we could usually
deduce that it is the field's label. SC4.1.2 simply says we must go further
than rely on the visual presentation by adjacent position, it must be
linked in the markup to the field so screen readers can announce it as the
field name and label, and not just leave users to guess. It also says we
must provide such a name even if the visual presentation does not.
Again, if something can be revealed and hidden, we must say what the
current state is initially. And any changes to that state, and any other
changes to content, must also be passed programmatically to assistive
technology.
So I guess 4.1.2 doesn't say anything different from 1.3.1. It is merely
saying it much more clearly and explicitly for interactive components,
because they have a lot more properties than static content has!
I hope that helps. Others may explain it differently but that is my take on
it. The first place to look for more information on the two SCs, of course,
is in their "Understanding" documents, from the links in the WCAG itself.
From: allyssa jessicon
Date: Mon, Apr 12 2021 11:58PM
Subject: Re: Expanding awareness WVAG
← Previous message | No next message
Thanks, much appreciated for writing back.
On Friday, April 9, 2021, Laura Fathauer < = EMAIL ADDRESS REMOVED = > wrote:
> Hi-
>
> They both deal with programmatic equivalents. 1.3.1 looks at all content,
> whereas 4.1.2 applies only to user interface components. There can be
> overlap (see failure F42; also in cases where the information is about form
> fields such as a question for a group of form fields). 1.3.1 looks at any
> relationships between elements that is conveyed visually (tables). 1.3.1
> also covers other information conveyed visually, so for example if you have
> a weighted word cloud where words used more often are bigger/bolder, that
> is visual information that needs to have a way the information is provided
> programmatically. 4.1.2 explicitly references changes in the state of user
> interface components (open/closed, etc).
>
> Laura
>
>
> On Wed, Apr 7, 2021 at 9:44 AM allyssa jessicon < = EMAIL ADDRESS REMOVED =
> >
> wrote:
>
> > Hi,
> >
> > I would like to know if someone has a resource or idea wjere I can
> educate
> > myself to understand the difference between 1.3.1 info and relationship
> and
> > 4.1.2 Name, role, value? Any help would be greatly appreciated.
> >
> >
> > Regards,
> > Allyssa.
> > > > > > > > > >
> > > > >