Re: Accessible authentication and we need a fundamental change

Hi all,

With regard to accessible authentication, there is emergent work within the
W3C on that topic today (Verifiable Claims and Web payments in general),
although, similar to our Working Group, the Verifiable Claims folks
encountered some push-back while attempting to get their work into a
Working Group (and out of a Community Group).

The problem today is that we need a better mechanism for robust and secure
authentication, but it isn't really all there yet and it will very likely
be dependent on browser vendors support. Thankfully, we have a number of
accessibility folk from our numbers directly involved in that work (Katie
Haritos-Shea, Shane McCarron, Janina Sajka) and there is some exciting
prospects ahead - but currently the work is immature (to say the least).

Re: Jason's thoughts - bang on! This very much sounds and feels like
something that the EO WG should be involved with, and I am curious if we've
formally reached out to them (yet)?

JF





On Wed, Feb 1, 2017 at 10:55 AM, White, Jason J <jjwhite@ets.org> wrote:

>
>
>
>
> *From:* Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
> *Sent:* Wednesday, February 1, 2017 11:39 AM
>
> We have many commenters and observers who are looking forward to our work,
> but among these are many people who want to see WCAG 2.1 standardize what
> is implementable based on the technologies that are available today, and we
> need to work to try to find the right balance between what would be best
> for users with all different types of disabilities and what is
> achievable/testable.
>
> *[Jason] With these constraints in mind, there should be a good home for
> design guidance that, for whatever reason, can’t be included in a normative
> specification, but which is nevertheless valuable for accessibility
> reasons. I recall discussion of a CSS best practices document, but what I
> have in mind here would be broader in scope.*
>
> *It doesn’t fit into Techniques, but it would nevertheless be a valuable
> practical aid to content authors. Any guidance which is later refined and
> becomes fit for inclusion could then be migrated into a future normative
> specification.*
>
> *The suggested document could include advice from the task forces that
> doesn’t make its way into WCAG 2.1, as well as more general
> accessibility-related practices. If work proceeds within W3C on any kind of
> Web development best practices guide, this material on accessibility could
> achieve higher visibility by being included there. WCAG 2.1 could also make
> a non-normative reference to this material (wehther published by the
> Accessibility Guidelines working group or elsewhere).*
>
>
>
> ------------------------------
>
> 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.
> ------------------------------
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion