Skip to content

Conversation

@howard-e
Copy link
Contributor

@howard-e howard-e commented Sep 18, 2025

Hi @shawna-slh and @remibetin. We would like to deploy a new version of the APG. This was approved during this week's APG meeting by @mcking65 and @daniel-montalvo.

The update includes the following, sourced from w3c/aria-practices 2025-09-17 September 2025 APG Publication Milestone and pushed to w3c/aria-practices main branch:

Developing a Keyboard Interface Practice: Editorial revision to note about pointer considerations (pull #3366)

By Daniel Montalvo on September 30, 2025

Makes two minor editorial improvements to the note about pointer considerations when managing focus:

  • Change 'must' to 'need to' to avoid use of normative sounding language.
  • Remove phrase 'of course' to avoid superfluous language.

View commit 2cafe96


Carousel Pattern: Fix inconsistency in use of digits and number words (pull #3362)

By Mehraz Morshed on September 17, 2025

Changed "slide one" (word form) to "slide 1" (digit form for consistency with other mentions of slide numbers.

View commit 59a55b3


Add "Quantity Spin Button" pattern example (pull #3328)

By Adam Page on September 17, 2025

Resolves #3261 by:

  1. Adding a new quantity spin button example that includes editable inputs for each spinner.
  2. Deprecating the date picker spin button example, which did not include editable inputs. The date picker spin button example page is still available, but its link has been removed from the pattern page and it has been marked deprecated.

These changes also resolve issues #2241, #2238, #1837, #1655, and #1188.

Co-authored-by: Howard Edwards
Co-authored-by: Matt King

View commit 0234ae9


Grid Pattern: Correct error in description of left/right arrow behavior when navigating inside a cell (pull #3356)

By NakajimaTakuya on September 16, 2025

Documentation of wrapping behaviors when navigating among elements inside of a grid cell had the wrap-around behavior reversed. This commit corrects the error.

View commit 219f526


Developing a Keyboard Interface Practice: Add note about pointer activation and roving tabindex/aria-activedescendant (pull #3311)

By Patrick H. Lauke on September 16, 2025

Fixes #1710:
Adds a new note advising authors to change the roving tabindex or set the correct aria-activedescendant reference as a result of pointer interactions (clicks, taps, ...) as otherwise there will be a mismatch for users that navigate with both keyboard and pointer.

Also adds <code> ... </code> around relevant words like tabindex and aria-activedescendant.

Co-authored-by: Ariella Gilmore

View commit b5f2c69


Pattern Pages: Show link to "Read This First" just after the H1 on each pattern page (pull #3320)

By Howard Edwards on September 2, 2025

Resolves issue #3293 by including a link to the "Read This First" practice page at the top of every pattern page, immediately following the H1.

Includes an infrastructure update to move control of the read this first content display to the aria-practices content repository from the wai-aria-practices build repo.

View commit 457f47a


Editor Menubar Example: Fix tabindex management to ensure only the most recently opened menu is in the page tab sequence (pull #3309)

By Alec Mitnik on August 12, 2025

Fixes bugs where using a combination of keyboard and mouse interactions caused multiple menu items to be in the page Tab sequence.

The following changes ensure that only the most recently opened menu is the only menu item in the page tab sequence regardless of how that menu item was opened or had originally received focus:

  • Opening a menu via clicking now correctly updates the tabindex values of the menubar items (instead of the submenu items).
  • Opening a menu via hover now correctly updates the tabindex values of the menubar items (instead of updating nothing due to erroneously passing in a menu rather than an ID).
  • Opening a menu via Enter, Space, or Arrow Up/Down now updates the tabindex values of the menubar items, since it's possible for the parent menuitem to have received keyboard focus other than through a way that would have already updated the tabindex values (e.g. by pressing on it and dragging off it before releasing).

View commit ccfa79e


All Pages: Change 'Javascript' to 'JavaScript' (pull #3306)

By Umair Khan on August 12, 2025

Standardize case of 'JavaScript' across content and templates.

Co-authored-by: Howard Edwards

View commit 8b05538

howard-e and others added 30 commits July 28, 2025 12:02
Added script to pr-create.yml to reinit submodules to avoid stale references if any exist
Fix merge conflicts in submodule when `pr-create` runs
# Conflicts:
#	.gitmodules
#	ARIA/apg/patterns/feed/examples/feed.md
#	_external/aria-practices
# Conflicts:
#	ARIA/apg/patterns/patterns.md
#	ARIA/apg/practices/practices.md
#	_external/aria-practices
#	content-assets/wai-aria-practices/shared/js/read-this-first.js
Sources "Read This First, No ARIA is better than Bad ARIA" banner from APG
@netlify
Copy link

netlify bot commented Sep 18, 2025

Deploy Preview for aria-practices ready!

Name Link
🔨 Latest commit 5e305f4
🔍 Latest deploy log https://app.netlify.com/projects/aria-practices/deploys/68db29b667f6bc00085421da
😎 Deploy Preview https://deploy-preview-436--aria-practices.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.

shawna-slh
shawna-slh previously approved these changes Sep 18, 2025
Copy link
Contributor

@shawna-slh shawna-slh left a comment

Choose a reason for hiding this comment

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

From quick skim, looks OK to me. Rémi will take it from here...

<div class="note">
<h4>Note</h4>
<p>This guidance focuses specifically on keyboard interaction. However, authors must of course also consider pointer interactions, such as mouse clicks
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this can be improved. We are putting must in a note, which in itself is confusing. Also, the of course here is redundant, so can be avoided.

Suggested change
<p>This guidance focuses specifically on keyboard interaction. However, authors must of course also consider pointer interactions, such as mouse clicks
<p>This guidance focuses specifically on keyboard interaction. However, authors also need to consider pointer interactions, such as mouse clicks

@daniel-montalvo
Copy link
Contributor

Sorry @howard-e I just pressed the button too quickly. For a follow-up PR on my requested changes, see w3c/aria-practices#3366

@howard-e
Copy link
Contributor Author

howard-e commented Sep 23, 2025

Sorry @howard-e I just pressed the button too quickly. For a follow-up PR on my requested changes, see w3c/aria-practices#3366

@daniel-montalvo thanks! I updated w3c/aria-practices#3366 title but this change seems good to me

cc @mcking65 @a11ydoer, I requested both of your reviews on that to unblock this publication release

@daniel-montalvo
Copy link
Contributor

@remibetin this is now ready for your review & publication.

@howard-e howard-e changed the title For publication / deploy on Thursday September 18, 2025 For publication / deploy on Tuesday September 30, 2025 Sep 30, 2025
@howard-e
Copy link
Contributor Author

howard-e commented Oct 6, 2025

Hello @remibetin! Checking in again if there's anything else needed to move this to publication?

@daniel-montalvo
Copy link
Contributor

@howard-e

@remibetin did talked about this to me this morning. Just logging it in here.

Not a blocker for publication, but something for us to pick up for future fix. The "Read this first" banner is included using client-side JavaScript. It would be more elegant if we could use HTML or a jekyll _include

@remibetin remibetin merged commit a4561a4 into publication Oct 7, 2025
9 checks passed
@remibetin
Copy link
Member

@daniel-montalvo @howard-e Published and ready for your QA.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants