Been using GitHub's copilot for a week now. Really impressed what it can do. Certainly isn't going to replace me any time soon, but its a nice addition, especially in writing tests, which can be fairly repetitive. Thanks GitHub!
Remote
Wilco
@wilco@mastodon.nl
mastodon 4.7.3+procolix.mnlWeb accessibility standards & tools nerd.
axe-core & axe-linter lead @DequeSystems
ACT Task Force & WCAG 3 facilitator @W3C
0 Followers
0 Following
15 Posts
Joined November 08, 2022
I am stoked to let you all know that the W3C has officially announced the ACT Implementations list. This is the list of accessibility solution that have documented their consistency with rules for WCAG and ARIA.
https://www.w3.org/WAI/standards-guidelines/act/implementations/
For info about ACT Rules, see https://www.w3.org/WAI/standards-guidelines/act/rules/about/
And if you'd like your tool on this list: https://www.w3.org/WAI/standards-guidelines/act/report/submit/
I miss one WCAG meeting and suddenly a success criterion is getting pulled. I'll be the last person to say we need to leave 4.1.1 parsing as is, but just removing it is problematic too. Looking for an alternative. https://github.com/w3c/wcag/issues/2820
Found a bug in #axe-core Monday that we're rushing to get fixed. I'm very glad I found it before it went into the extension, but not nearly as glad that I was the one who introduced it a few months back. Bit of a mixed bag.
Spent the holiday getting more into machine learning. Looking forward to next week's WAI conference on the topic: https://www.w3.org/WAI/about/projects/wai-coop/symposium2/ Signup ends tomorrow!
Time for xmas decorations again. I noticed last year that having all these lights around the house makes a real difference on my winter depression. This is the first year I actually looked forward to putting them up.
Another 90 minute conversation about WCAG 2.2's target size. I'm sure not going to miss these once WCAG 2.2 is done!
Always interesting to work in code you haven't touched in a few years. Happy to see my coding skills are still improving. Always more to learn.
Anyway, axe will soon have an option to select / exclude specific parts of a shadow DOM tree: https://github.com/dequelabs/axe-core/pulls
My favorite test case of the month. Axe-core is leaning how to blend -webkit-text-stroke:
Hello world
I want to welcome ember-template-lint to the ACT implementors list. Fantastic, and the first accessibility linter on the ACT implementors list:
https://www.w3.org/WAI/standards-guidelines/act/implementations/#accessibility-linters
Interesting development in #WCAG 2.2 land today. Sounds like SC 4.1.1 Parsing might get deprecated still. Or some other word that means "don't worry about it if it doesn't fail something else". That's a nice surprise.
Worked on tooling today that should make it much easier to create an ACT implementation report. Here's a preview of what I've got for ember-template-lint:
https://deploy-preview-157--wai-wcag-act-rules.netlify.app/standards-guidelines/act/implementations/ember-template-lint/
And here's what was used to run it:
https://github.com/act-rules/act-shared-reports/blob/main/src/runEmberTempaleLint.ts
Trying to list out what types of text in images WCAG's "essential" definition applies to. This is how far I got. Anyone have any more?
Four more ACT rules awaiting final approval by the accessibility guidelines working group. I suspect we might get to 30 approved rules this year!
This week axe Linter hit 1
00k installs on VS Code. I'm so stoked people are using this. It's been a long-time dream to build a proper "accessibility spell checker". It's already cool, but the potential for it is so much bigger still. Fingers crossed the ball keeps rolling for axe-linter.