Re: Proposal: We need to identify whether a proposed SC applies broadly

hi Kim

The current proposal has an exception for audience...

   - The content will be penalized for not conforming to a given writing
   style (such as a CV, dissertation, or Ph.D. proposal).

​Having said that I think the proposed language would need a lot of work to
pass the 9 requirements for SCs.
https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria
​. It seems in very lay terms now and needs to describe the passing state,
and the exceptions need to describe the state of the content when it is
excepted.
​




Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Wed, Mar 22, 2017 at 10:59 AM, <kimberlee.dirks@thomsonreuters.com>
wrote:

> Hi Gregg,
>
>
>
> Thanks for replying.
>
>
>
> Can you give me an example of how you would restrict to particular
> content, please?
>
>
>
> Thank you.
>
>
>
> Kim
>
>
>
> *From:* Gregg C Vanderheiden [mailto:greggvan@umd.edu]
> *Sent:* Tuesday, March 21, 2017 1:19 PM
> *To:* Jason J White
> *Cc:* alands289; Dirks, Kim (Legal); w3c-waI-gl@w3. org
> *Subject:* Re: Proposal: We need to identify whether a proposed SC
> applies broadly
>
>
>
> +1  to Jason’s comment
>
>
>
> You can solve this problem by restricting the SC to only those types of
> content that it should apply to.
>
>
>
> g
>
>
>
>
>
> Gregg C Vanderheiden
>
> greggvan@umd.edu
>
>
>
>
>
>
>
> On Mar 21, 2017, at 2:04 PM, White, Jason J <jjwhite@ets.org> wrote:
>
>
>
> The WCAG 2.0 position is that if a success criterion is not broadly
> applicable to different kinds of content (including Web sites and Web
> applications in a general sense), then it belongs at Level AAA. I would be
> very surprised if this working group were to depart from that position in
> crafting WCAG 2.1.
>
>
>
> *From:* alands289@gmail.com [mailto:alands289@gmail.com
> <alands289@gmail.com>]
> *Sent:* Tuesday, March 21, 2017 1:10 PM
> *To:* kimberlee.dirks@thomsonreuters.com; w3c-wai-gl@w3.org
> *Subject:* RE: Proposal: We need to identify whether a proposed SC
> applies broadly
>
>
>
> Kimberlee,
>
>
>
> I was reading through your email and I’m thinking is not possible that
> there would be “professionals” that would have disabilities?
>
>
>
> Do we not need to consider accessibility for employees as an employer to
> meet the US Government’s Section 503 if applicable?
>
>
>
>
>
> Alan Smith
>
>
>
> *From: *kimberlee.dirks@thomsonreuters.com
> *Sent: *Tuesday, March 21, 2017 10:58 AM
> *To: *w3c-wai-gl@w3.org
> *Subject: *Proposal: We need to identify whether a proposed SC applies
> broadly
>
>
>
> Hello everyone,
>
>
>
> It’s my understanding that our goal is to make every website accessible to
> everyone and develop guidelines that are universally applicable. Given
> that, I’m really struggling with how to apply some of the proposed SCs to *
> *all** websites.
>
>
>
> *Please note*: I’m using “website” generically – I’m including mobile
> apps, software, etc. I’m also using “computer” generically to include all
> devices we use to interact with digital content.
>
>
>
> *Proposal*
>
> Proposed SCs need to identify targeted types/categories of websites, based
> on expected users, because not all websites can or should be expected to
> conform to all categories of user needs. In other words, a site geared
> toward the practice of medicine doesn’t need to take into account my
> autistic nephew, but a bank site where he can check is bank balance, does.
>
>
>
> *Background*
>
> There are multiple “professional” websites. In fact, my company has over
> 150 digital product offerings. These sites are designed for highly educated
> professionals to be used in the course of their jobs. Our target audience
> includes legal professionals, data scientists, tax and accounting
> professionals and other expert users. These users are in careers that
> require a very high level of knowledge and cognitive functioning. Their
> *licenses* require a very high level of knowledge and cognitive
> functioning. This leads me to the conclusion that some of the proposed SCs
> fail because they do not apply to all user profiles.
>
>
>
> However, I also see merit in those same proposed SCs. It seems like we
> have two options.
>
> 1. Throw out all the “squishy” SCs
>
> 2. Create a “category” for those SCs that may not apply to all websites.
> This is not accurate, but for the sake of this proposal, it could be
> something like “public” and “professional” as an example.
>
>
>
> *Justification*
>
> Some websites do need to be accessible and usable by virtually everyone
> who can use a computer. For example, everyone should be able to check their
> bank balance or fill out online job applications (assuming they are
> qualified for those jobs). But for websites that target specific people or
> groups of people such as graduate students, doctors, or lawyers, it may be
> impossible for them to present their content and the functionality of their
> website such that every person who uses a computer can use and understand
> their websites. I’m concerned that we will be putting companies such as
> mine in a position to have to *choose between their business needs and
> accessibility standards*. To me, this harms our reputation as a
> standards-generating body.
>
>
>
> We already separate out accessibility guidelines, such as those targeting
> page authoring, testers, and so on.
>
>
>
> What do you think? I think we need to have a conversation about this and
> figure out a way to keep the some of the new SCs, even if they don’t apply
> to every website.
>
>
>
> Thanks.
>
>
>
> Kim
>
>
>
>
>
> *Kimberlee Dirks, JD*
>
> Accessibility Specialist, Legal UX
>
> Thomson Reuters
>
> kimberlee.dirks@tr.com
>
>
>
>
>
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
>
>
> Thank you for your compliance.
>
>
>