E-mail List Archives
Thread: Guidelines clarification
Number of posts in this thread: 4 (In chronological order)
From: Kakarla Meharoon
Date: Tue, Jul 24 2018 3:54AM
Subject: Guidelines clarification
No previous message | Next message →
Hi All,
We have one customer he wanted us to add " Script ability functionality for
all the users using adaptive software" in this it contains below points
1. provide consistent method for identifying the application each screen
2. A unique id for every piece of information on the screen
3. A separate container for each piece of information on screen
As per WCAG 2.0 first one represents consistent navigation and second one
is mandatory ? is it necessary to add ids for all the html elements ?
A separate container for each piece of information on screen nothing
but landmarks.
From: Isabel Holdsworth
Date: Tue, Jul 24 2018 4:07AM
Subject: Re: Guidelines clarification
← Previous message | Next message →
Hi Kakarla,
1. A distinct, descriptive page title for each new page is always a
good idea and should cover this point. This can be done using
JavaScript if necessary - that's how it's often done in single-page
applications.
2. It depends what you think of as a "piece of information". If he's
talking about distinct areas on a page such as header, footer and main
content, then these should be in separate containers. If he means that
each paragraph, form element etc should be in its own div, then this
isn't required for accessibility but might be for scripting.
3. As regards unique IDs for each element, perhaps he wants the
ability to target the elements to add accessibility using JavaScript,
in which case it would help if elements did have their own ID.
Cheers, Lynn
On 24/07/2018, Kakarla Meharoon < = EMAIL ADDRESS REMOVED = > wrote:
> Hi All,
>
> We have one customer he wanted us to add " Script ability functionality for
> all the users using adaptive software" in this it contains below points
> 1. provide consistent method for identifying the application each screen
> 2. A unique id for every piece of information on the screen
> 3. A separate container for each piece of information on screen
>
> As per WCAG 2.0 first one represents consistent navigation and second one
> is mandatory ? is it necessary to add ids for all the html elements ?
>
> A separate container for each piece of information on screen nothing
> but landmarks.
> > > > >
From: Kakarla Meharoon
Date: Tue, Jul 24 2018 4:18AM
Subject: Re: Guidelines clarification
← Previous message | Next message →
Hi,
Thanks
As per WCAG ids is necessary for all the elements in the navigation and
links or buttons.
From: Isabel Holdsworth
Date: Tue, Jul 24 2018 6:18AM
Subject: Re: Guidelines clarification
← Previous message | No next message
No, IDs are not necessary for any element to achieve WCAG conformance.
But they might be necessary for your developer to add accessibility to
specific elements depending on how your pages are constructed at
runtime.
On 24/07/2018, Kakarla Meharoon < = EMAIL ADDRESS REMOVED = > wrote:
> Hi,
>
> Thanks
>
> As per WCAG ids is necessary for all the elements in the navigation and
> links or buttons.
> > > > >