Re: WCAG vialations or accessibility enhancements

Alan,

I'm not sure I agree with the 3.2.2 categorization. 3.2.2 only applies to
changes of context as a result of changing the settings of a control.
Clicking a link is explicitly called out as* not *being a change of
settings in the Understanding
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.html>
 3.2.2
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.html>
 page:

"Note: This Success Criterion covers changes in context due to changing the
setting of a control. *Clicking on links or tabs in a tab control is
activating the control, not changing the setting of that control*."
(emphasis added)

Regards,
John Cha


On Wed, Feb 14, 2018 at 9:56 AM, ALAN SMITH <alands289@gmail.com> wrote:

> Ramakrishnan,
>
>
>
> I just was starting my day when I saw your email and no one had replied
> for 8 hours.
>
>
>
> Perhaps we are all just getting started?
>
>
>
> I was typing a reply when I saw Jon’s reply come in. He provided a link to
> the landmarks coding which helps you fix your landmarks but he did not
> answer your questions.
>
>
>
> Also, it sounds like you already know the labeling is wrong.
>
>
>
> What you have listed are accessibility violations.
>
>
>
> People like to hear “enhancement” but they are “violations” or
> non-conformance issues.
>
>
>
> Headings out of proper hierarchical numbering  order is a violation of
> 1.3.1 Info and Relationships
>
> Landmark labeling being duplicated for different information is a
> violation of 1.3.1 Info and Relationships
>
> Links that open in new windows thus changing the context for the user is a
> violation of 3.2.2 On Input
>
>
>
> I like to use the WCAG 2.0 Quick Reference link as a starting place for
> all things WCAG 2.0 related.
>
> https://www.w3.org/WAI/WCAG20/quickref/
>
>
>
> If you need further assistance and do not hear from others, please reach
> out to me personally.
>
>
>
> Alan Smith
>
>
>
> *From: *Ramakrishnan Subramanian <ram.eict2013@gmail.com>
> *Sent: *Wednesday, February 14, 2018 1:23 AM
> *To: *w3c-wai-ig@w3.org
> *Subject: *WCAG vialations or accessibility enhancements
>
>
>
> Dear Members,
>
> I hope it is appropriate to post this query here.
>
> I kindly request you to help me understand few of the accessibility
>
> related issues mentioned below.
>
> Whether these are treated as accessibility enhancement which would be
>
> helpful for the end user. Or accessibility violation.
>
> Heading order:
>
> Whether the following heading level is considered an accessibility
>
> violation? if yes, which criteria does this violate?
>
> The first heading level in the page is <h2> sample text </h2>
>
> The next heading level is <h5> sample text </h5>
>
>
>
> Landmark regions:
>
> When there are different content given inside two different aria
>
> region, with same aria label. Under which criteria this fails?
>
> <div role=”region” aria-label=”apple”>
>
> Apple related content goes here
>
> </div>
>
> <div role=”region” aria-label=”apple”>
>
> Bannana related content goes here
>
> </div>
>
> 3. Links which open in a new window:
>
> When there is no indication for the screen reader users for the link
>
> which opens in a new window, is that considered an accessibility
>
> violation? If yes, which criteria does this issue violate?
>
>
>
>
>
> --
>
>
>
> Thanks and Regards
>
> Ramakrishnan
>
>
>
>
>



-- 
*John Cha  |  Software Tester  | ULTRA**TESTING *
233 Broadway, Fl 28  |  New York, NY 10279  |  USA
m: john@ultratesting.us <brandi@ultratesting.us>