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

For publication / deploy on Wednesday April 12 or Thursday April 13 (see comments for date determination) #210

Merged
merged 35 commits into from
Apr 13, 2023

Conversation

alflennik
Copy link
Contributor

@alflennik alflennik commented Apr 10, 2023

Hi @shawna-slh, we would like to deploy a new version of APG.

Changes include:

@netlify
Copy link

netlify bot commented Apr 10, 2023

Deploy Preview for aria-practices ready!

Name Link
🔨 Latest commit 0d8fb80
🔍 Latest deploy log https://app.netlify.com/sites/aria-practices/deploys/6438180c1fb6b20008ad2ec6
😎 Deploy Preview https://deploy-preview-210--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 site settings.

@mcking65 mcking65 changed the title For publication / deploy on Tuesday 11 April 2023 For publication / deploy on Wednesday April 12 or Thursday April 13 (see comments for date determination) Apr 11, 2023
@alflennik alflennik marked this pull request as draft April 11, 2023 18:31
@alflennik alflennik changed the title WIP: For publication / deploy on Wednesday April 12 or Thursday April 13 (see comments for date determination) Draft: For publication / deploy on Wednesday April 12 or Thursday April 13 (see comments for date determination) Apr 11, 2023
@shawna-slh
Copy link
Contributor

shawna-slh commented Apr 11, 2023

@alflennik
Copy link
Contributor Author

@shawna-slh I do see it in the assistive technology support section, it's the last heading on the page, here's a screenshot of what I'm seeing:

Assistive Technology support section with support tables loaded

@alflennik alflennik changed the title Draft: For publication / deploy on Wednesday April 12 or Thursday April 13 (see comments for date determination) For publication / deploy on Wednesday April 12 or Thursday April 13 (see comments for date determination) Apr 11, 2023
@alflennik alflennik marked this pull request as ready for review April 11, 2023 21:38
@alflennik
Copy link
Contributor Author

alflennik commented Apr 11, 2023

@shawna-slh assuming my comment cleared things up, we are ready to release!

cc @mcking65 @a11ydoer

@shawna-slh
Copy link
Contributor

Ah, I was looking for it in the Page Contents box -- and with my configuration, I don't see it:
image

even when I scroll down:
image

So that's a separate issue. I'll leave it to you all to create an Issue for that.

@daniel-montalvo
Copy link
Contributor

Hi @alflennik @mcking65
Ideally we can fix w3c/aria-practices#2650 soonish.

I would expect these pages to get more traction given the imminent blog announcement. Even if it is not related to AT support tables, it seems to me that having an example that lacks visual focus indication is problematic and can raise some eyebrows. If I am not mistaking, the button examples are one of the four that will have the new tables, so that is yet another reason for people to look specifically at this pages. I would suggest we prioritize this.

@alflennik
Copy link
Contributor Author

alflennik commented Apr 12, 2023

@shawna-slh thank you for sharing the screenshot, I can see that in your setup the page contents navigation box is so tall it's clipping off the bottom of the screen. The part that especially gives me pause is that the links in the box are wrapping so much, for example the "Role, Property, State and Tabindex Attributes" link is wrapped over four lines. I tried a few ways to reproduce this issue, including changing the default text size, but I couldn't get that amount of wrapping to occur.

Looking at your screenshots I can see that there might be some custom css styles applied to the site. Would you mind checking if the issue still occurs without the styles present? Also would it be possible to let me know what your default text size is?

@alflennik
Copy link
Contributor Author

Hi @daniel-montalvo, thank you for emphasizing the importance of the button focus issue, I agree that it's an eyebrow raiser. I opened a PR here: w3c/aria-practices#2673 and, pending review, the fix should be in the next release.

@mcking65
Copy link
Contributor

@alflennik, with w3c/aria-practices#2673 merged, should we try to include it in this PR before the publication?

@alflennik
Copy link
Contributor Author

@mcking65 I updated the PR with the typo fix and the button focus indicator fix, I'm glad we had a chance to fix those.

@shawna-slh
Copy link
Contributor

@mcking65 @alflennik @a11ydoer

It looks like we'll get the blog issues worked out. Shall I publish this now, while Alex is available to QA it?

@mcking65
Copy link
Contributor

@shawna-slh Yes, we are on track for Monday announcement, so let's please push this to production.

@mcking65
Copy link
Contributor

Thank you @alflennik for getting those latest 2 fixes included in this PR.

@shawna-slh shawna-slh merged commit 5bdbf12 into publication Apr 13, 2023
@shawna-slh
Copy link
Contributor

Deployed. I did a just few quick checks, and looks good. Others please do more thorough QA. Thanks.

@alflennik
Copy link
Contributor Author

Thank you @shawna-slh! I confirmed that the support tables are working.

@mcking65
Copy link
Contributor

Thank you @shawna-slh!!!

I went through all the changed pages since last deploy and spot checked some other places, and from the POV of a screen reader user, it looks great! I hope the same is true visually!
Would be good for someone to double-check the fix to focus indicator on button example page.

@alflennik
Copy link
Contributor Author

@mcking65 I confirmed that the button indicator is working.

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