Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Including relevant parts of "Using ARIA" in APG #2675

Open
daniel-montalvo opened this issue Apr 18, 2023 · 2 comments
Open

Including relevant parts of "Using ARIA" in APG #2675

daniel-montalvo opened this issue Apr 18, 2023 · 2 comments
Assignees
Labels
enhancement Any addition or improvement that doesn't fix a code bug or prose inaccuracy

Comments

@daniel-montalvo
Copy link
Contributor

As stated in w3c/using-aria#49, the "Using ARIA" document is attributed to the Web Platform Working Group. They requests us to change it to the ARIA WG. As per ARIA Editor's meetings, most of it is (or will be) already in APG pages. In order for the group to take a decision, we first need to make sure that APG contains the relevant and useful parts of that document and that there is consensus around that.

@a11ydoer
Copy link
Contributor

@jongund and @andreancardona are happy to help with content audit and move relevant contents to APG site. As the first step, mapping out the content will be done.

@a11ydoer a11ydoer self-assigned this Apr 25, 2023
@css-meeting-bot
Copy link
Member

The ARIA Authoring Practices (APG) Task Force just discussed "Using ARIA" to APG.

The full IRC log of that discussion <jugglinmike> Topic: "Using ARIA" to APG
<jugglinmike> github: https://github.com//issues/2675
<jugglinmike> Matt_King: We have the information architecture we need to support this, so the timing is pretty perfect in my mind
<jugglinmike> Matt_King: The first thing to do is to go through the headings in the "Using ARIA" document, and identify which of those sections are either (1) already covered, (2) appropriate to be discarded, or (3) appropriate for some section of APG
<jugglinmike> Jem: This seems like a good task for newcomers
<jugglinmike> Andrea: Can we think of this as an audit?
<jugglinmike> Matt_King: Not exactly. The end goal is that "Using ARIA" is going to go away. But there's information in "Using ARIA" that APG can inherit. The task is to identify which information can be salvaged and where it belongs (e.g. in a pattern or in a practice)
<jugglinmike> jongund: I can help with this because I'm familiar with both documents
<jugglinmike> Matt_King: I'm not sure of the best way to structure this, but I've been imagining taking the table of contents and then categorizing each item in an issue comment
<jugglinmike> Andrea: I'm interested in helping, too
<jugglinmike> Jem: I'll assign Matt_King, jongund, and Andrea
<jugglinmike> Jem: I'll assign myself as well so I can review
<jugglinmike> Andrea: I'll coordinate the work to start us off

@mcking65 mcking65 added enhancement Any addition or improvement that doesn't fix a code bug or prose inaccuracy documentation labels Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Any addition or improvement that doesn't fix a code bug or prose inaccuracy
Projects
None yet
Development

No branches or pull requests

6 participants