search

w3c / strategy

team-strat, on GitHub, working in public. Current state: DRAFT
158 stars 47 forks source link

[wg/aria] PDF Accessibility API mappings #461

Closed plehegar closed 2 months ago

plehegar commented 6 months ago

Investigation

cc @jnurthen @spectranaut

plehegar commented 6 months ago

For a Recommendation track document that would be co-published by 2 organizations, we would establish an MoU to do the joint work, then recharter the Group to put the work listed in the MoU within the scope of a working group.

There are several questions that needs answering, including:

  1. is this within our technical strategy?
  2. what are we (the WG and W3C) trying to achieve and what are our parameters?
  3. what is the other organization trying to achieve and what are their parameters?
  4. Any other consideration that we ought to take into account?

Once we have all of that, assuming no red flag, we give it all to our legal team for them to come up with a draft MoU. Once both orgs are happy with the draft, W3C then need to follow section 9. Liaisons as it would be a technical agreement. The other organization would need to follow its own process to sign it as well. We may also be able to do the rechartering in parallel if we're confident about the outcome.

iadawn commented 3 months ago

@plehegar Thanks for this. I spoke with Duff regarding the approach to partnering on this work. I emailed the outcome of the conversation which Duff agreed with.

PDF Association is keen to have this material published by W3C as they see this as resulting in better uptake. Given the extensive use of PDF delivery through browsers it makes sense to look at developing and publishing this material. This should benefit assistive technology in dealing with PDFs delivered through compliant browsers.

My understanding, and forgive my memory for not knowing where this came from, was that an MoU wasn't a necessity.

plehegar commented 2 months ago

Thank you @iadawn .

There is a proposed charter to include the PDF accessibility in the ARIA WG.

At this point, we can close this issue and track the follow-up on the charter issue.

See https://github.com/w3c/strategy/issues/466