Re: Requesting A11y review for Decentralized Identifiers (DIDs) v1.0

Hi, Ivan:

Yes, please feel free to copy my email comment as is useful, but also
thanks for asking!

Best,

Janina


Ivan Herman writes:
> Thank you very much, Janina.
> 
> On a purely administrative level, is it o.k. if I copy the content of your mail into the issue? It is the place where we follow these reviews and that we will use in our final reports, and it would simplify things for us later.
> 
> Thank you again
> 
> Cheers,
> 
> Ivan
> 
> > On 8 Jul 2020, at 16:53, Janina Sajka <janina@rednote.net> wrote:
> > 
> > Dear Ivan, All:
> > 
> > I have completed reading through the DID specification as of today's
> > date:
> > 
> > https://www.w3.org/TR/did-core/
> > 
> > 
> > I note and appreciate your responses to our (nascent) accessibility
> > self-check instrument:
> > 
> > https://github.com/w3c/did-core/issues/105
> > 
> > I would agree there are no accessibility concerns in this specification.
> > Moreover, it does appear there are excellent opportunities to apply this
> > specification to various accessibility use cases--admittedly a different
> > matter.
> > 
> > My apologies for taking so long to complete this review. I do expect we
> > will clear our various tracking checks during today's APA call at Noon
> > (Boston).
> > 
> > Best,
> > 
> > Janina
> > 
> > Ivan Herman writes:
> >> For the sake of simplicity, I used the content of the i18n issue template for asking an i18n horizontal review. Please contact us if you think there are other aspects you need to know about. 
> >> 
> >> 
> >> - name of spec to be reviewed:  Decentralized Identifiers (DIDs) v1.0
> >> - URL of spec: https://www.w3.org/TR/did-core/
> >> 
> >>    Note, however, that the Working Group uses respec+ECHIDNA in such a way that each merge into the master branch creates a new version of the document on TR space. This also means that the document on TR changes often. We would therefore prefer if each comment referred to the dated URL-s rather than the undated one.
> >> 
> >> - Current Rec/Note phase? Working Draft phase heading toward CR. Note that we prepared the self test [1] around the FPWD phase, but the subsequent f2f meeting led to discussions that have resulted in a complete re-organization of the document, and preferred to wait for things to stabilize before contacting the horizontal review groups./
> >> 
> >>    [1] https://github.com/w3c/did-core/issues/105
> >> 
> >> - What and when is your next expected transition? Transition to CR, to be expected (late?) summer.
> >> 
> >> - What has changed since any previous review? N/a
> >> 
> >> - Any information arising from a self-review? The DID Core specification (which is a data model, essentially) does not deal with human readable texts at all. As a consequence, we have the impression that no serious accessibility issue would arise.
> >> 
> >> - Where and how to file issues arising? Best is to use github issues at https://github.com/w3c/did-core/ 
> >> 
> >> - Pointer to any explainer for the spec? Not yet available.
> >> 
> >> Thanks
> >> 
> >> Ivan
> >> 
> >> ----
> >> Ivan Herman, W3C 
> >> Home: http://www.w3.org/People/Ivan/
> >> mobile: +33 6 52 46 00 43
> >> ORCID ID: https://orcid.org/0000-0003-0782-2704
> >> 
> > 
> > -- 
> > 
> > Janina Sajka
> > https://linkedin.com/in/jsajka
> > 
> > Linux Foundation Fellow
> > Executive Chair, Accessibility Workgroup:	http://a11y.org
> > 
> > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
> > 
> 
> 
> ----
> Ivan Herman, W3C 
> Home: http://www.w3.org/People/Ivan/
> mobile: +33 6 52 46 00 43
> ORCID ID: https://orcid.org/0000-0003-0782-2704
> 

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

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

Received on Wednesday, 8 July 2020 15:26:35 UTC