Skip to content

Conversation

@dtsengchromium
Copy link

No description provided.

@netlify
Copy link

netlify bot commented Nov 25, 2025

Deploy Preview for wai-aria ready!

Name Link
🔨 Latest commit 3f493d9
🔍 Latest deploy log https://app.netlify.com/projects/wai-aria/deploys/693ad2cd8e5c8b0008558e3a
😎 Deploy Preview https://deploy-preview-2680--wai-aria.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@cyns cyns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. Excited to see Android getting added!

@dtsengchromium
Copy link
Author

dtsengchromium commented Dec 5, 2025

Thanks, Cynthia! (great to see your name).

I suspect the CI failure[1] is happening because the workflow is configured to fetch the branch name directly from origin (the main repo), but my branch exists on a fork.

Some AI-suggested fixes[2] to this issue. I haven't spent time looking at this but can given appropriate perms. Probably simpler if someone with write access can do it :).

  1. +refs/tags/android_frontmatter*:refs/tags/android_frontmatter*
    Error: The process '/usr/bin/git' failed with exit code 1

    https://github.com/w3c/aria/actions/runs/19685387275/job/56389556047?pr=2680

  2. Suggestion: Could you verify the workflow configuration? Usually, removing the ref input allows actions/checkout to handle forks automatically by checking out the PR's merge commit instead of the branch name.

    Example fix:

    YAML
    
    # Change this:
    - uses: actions/checkout@v4
      with:
        ref: ${{ github.head_ref }}
    
    # To this (use default behavior):
    - uses: actions/checkout@v4

Copy link
Contributor

@spectranaut spectranaut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks David!

On line 75, there is as "Authors" array which is used to create the "Platform Mapping Maintainers" list. I think, @dtsengchromium, we should add you for android, if so can you update the list:

          {
            name: "David Tseng",
            company: "Google LLC",
            note: "AccessibilityNodeInfo", // Or android.view.accessibilty or whatever the name of this API is
            w3cid: ???, // TODO: get from Daniel
          },

Also thanks for looking into the bot failure, but that is only relevant for changes to the ARIA spec specifically, so we can ignore it for this PR.

<li><cite>User Interface Automation</cite> [[UI-AUTOMATION]]</li>
<li><cite>ATK - Accessibility Toolkit</cite> [[ATK]] and <cite>Assistive Technology Service Provider Interface</cite> [[AT-SPI]], referred to hereafter as "ATK/AT-SPI"</li>
<li><cite>macOS Accessibility Protocol</cite> [[AXAPI]]</li>
<li><cite>Android</cite> [[AccessibilityNodeInfo]]</li>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This link doesn't work, it should bring us to an entry in the references section: https://w3c.github.io/core-aam/#references

However, I looked around a bit and I don't see how to do this. Also I noticed that there is a strange split between normative and informative references... which I suppose I'll make an issue about: w3c/core-aam#255

Also I wonder about the name, "AccessibilityNodeInfo", I think from looking at the documents that maybe it should be the umbrella android.view.accessibility
... because might we want to reference AccessibilityEvents as well?

@cyns
Copy link
Contributor

cyns commented Dec 11, 2025

Thanks, Cynthia! (great to see your name).

Hi David, was great to see your name too!

name: "David Tseng",
company: "Google LLC",
mailto: "[email protected]",
note: "AccessibilityNodeInfo", // Or android.view.accessibilty or whatever the name of this API is
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dtsengchromium could you please update this accordingly?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Daniel, the idea was to update the "Platform Mapping Maintainers" list, not the editors list -- the list that is called "authors" shows up in the "Platform Mapping Maintainers" list in the rendered specification. I'm not asking David to be an editor, just a platform mapping maintainer :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants