Re: well known URI proposal

Hi Matthew, All:

This topic was discussed on WAI CC today, and I volunteered that we were
indeed active in this space and intending to further develop our
thinking with a joint meeting at TPAC with the relevant "well-known" WG,
whose full name I'm still temporarily forgetting!

https://www.w3.org/2023/08/21-waicc-minutes.html#item04

Shawn is happy for APA to go forward and then coordinate with EO when we
get to human readable elements.

Perhaps it also becomes another item for the planned APA plus EO meeting
during TPAC.

Janina

Matthew Atkinson writes:
> Hi Shawn, all,
> 
> Sadly I wasn't able to make the call today, apologies, but this (or rather something very related) is something that APA, and specifically Adapt TF, have been looking at—we're actually about to arrange a call at TPAC with the WebAppSec WG who originated the "Well-known URL for changing passwords" spec [1] to talk about it. We should have as many of you in that call as possible (let me know whom we should add to APA's invite request, or we can at least keep WAICC updated).
> 
> There are two related problems to this original work that we felt could be solved in a similar way:
> 
> 1. Making sites easier to navigate by providing well-known URLs for common site functions (as determined by COGA) such as: Login; Logout; Search; and so on.
> 
> 2. Making the accessibility statement easier to discover (that's what the proposal you sent out seems to focus on).
> 
> I have been thinking of, and taking some informal advice on, various ways this might be architected, and have several thoughts on it, and how to ensure it's as efficient as possible. I think a chat with WebAppSec at TPAC would be a good way to get a read on what sort of architecture would be considered apt by those in the know.
> 
> I'll check up on the minutes with interest, and will be chatting with Janina in APA's planning call tomorrow. We definitely want to help coordinate things so that we are all working in the same direction in this exciting area, and will keep you updated with any news from our TPAC planning.
> 
> Best regards,
> 
> 
> Matthew
> 
> [1] https://www.w3.org/TR/change-password-url/
> -- 
> Matthew Tylee Atkinson (he/him) 
> -- 
> Principal Accessibility Engineer 
> TPG Interactive 
> https://www.tpgi.com 
> A Vispero Company 
> https://www.vispero.com 
> -- 
> This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. 
> Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful. 
> 
> 
> 
> 
> On 21/08/2023, 15:22, "Shawn Henry" <shawn@w3.org <mailto:shawn@w3.org>> wrote:
> 
> 
> CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.
> 
> 
> 
> 
> H WAI CC,
> 
> 
> Attached is material for today's meeting.
> 
> 
> ftr:
> Shawn asked: Please let us know if you are comfortable with us sharing your attachments with a W3C Web Accessibility Initiative (WAI) coordination group via a mailing list that is publicly archived.
> > On 10-Aug-23 12:01 PM, Kumar, Abhinav wrote:
> > Please feel free to share the attachments with the W3C Web Accessibility Initiative (WAI) coordination group.
> 
> 
> Best,
> ~Shawn
> 
> 
> --
> Shawn Lawton Henry
> W3C Web Accessibility Initiative (WAI) Program Lead
> W3C Accessibility Education and Communications Lead
> GitHub: @shawna-slh Twitter: @shawna_slh
> About: www.w3.org/People/Shawn
> 
> 
> 

-- 

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/

Received on Monday, 21 August 2023 17:01:53 UTC