So yeah, I'm just going to introduce for those that don't know the groups that are involved in the accessibility space, do a quick overview of some of the work that we've been doing in the past 12 months.

For those that don't know, there are four key groups within the accessibility space.

There's the accessibility guidelines working group.

They're principally responsible for the main standard, the web content accessibility guidelines and working on resources that support that, explain that and develop the new standard WCAG 3.

We have the ARIA working group who are responsible for extensions on HTML to improve accessibility and the APIs associated with that.

The Accessible Platform Architecture working group.

Their primary responsibility is around about the accessibility horizontal review, although they also take a forward-looking view on a lot of weird and wonderful technologies that might be coming through and what we need to do around about those.

And finally, we have the Web Accessibility Initiative, the WAI Interest Group.

This is an extended community group, really, where we've got a group of community where we have a mailing list and a lot of support across the community for understanding our resources and for reviewing our resources.

So some of the highlighted publications from this year, we've published an update to the WCAG 3 draft, twice, and that is slowly developing in maturity.

We've got the ACT Rules, the Accessibility Conformance Testing Rules format.

That's a new 1.1 version is to CR.

Hopefully, we're getting that out later in the year.

We've had refinements and updates to WCAG2ICT.

So this is a set of guidelines that explain how WCAG might apply in non-Web technologies and spaces.

We've been doing a lot of architectural work in the background, looking at how we create the standards and maintain the standards.

One of the outputs we've managed to get out of that is maintained versions of WCAG 2 in JSON format and we've been hearing some input from people where they're already starting to use that data in weird and wacky ways, which we always appreciate.

Another small publication, an update to the final publication for the collaboration tools, accessibility, user requirements, which helps understand what are the user needs around about these sorts of tools and we've got a number of user requirement documents.

In terms of general process, there is a backlog task force, which is part of AG.

They manage the vast number of issues raised against WCAG 2.

They have managed to clear 500 WCAG 2 issues since they opened, which I think is about a year and a half, two years ago, which is fairly good going.

To be fair, they probably raised about 100 of those themselves.

They're building their own stats for themselves.

We've also, as I said, we've had massive improvements in the WCAG 2 and WCAG 3 build process.

This is really important because it really helps support that update to WCAG 2 and how we manage and maintain and update that.

It's also allowed us to get some more consistency across our various different resources and platforms that we've got that provide supporting material, one of those being the WCAG QuickRef, which we've made some subtle improvements to and how we manage it.

We've also had improvements to test accessibility mappings under the web platform test infrastructure, which I think is a really important one to try and integrate accessibility more directly into the platform tests and get consistency across development there.

The APA working group has been involved in extensive accessibility horizontal reviews and continue to do so.

Some future work, just to talk briefly about that.

We have got WCAG 3 draft scheduled for publication late 2025, early 2026, depending on how long it takes us to build the PR.

We're also looking, AG working group is set for recharter.

We've got an extension to mid 2026.

We're hoping to get that out sometime soon.

That will be planning towards a late 2028 WCAG 3 candidate recommendation for wide review.

We're continuing to clear the WCAG 2 issues.

The backlog group is working very hard on those, which is great.

Developing a number of other specifications, just a couple to mention, accessibility of machine learning and generative AI and specification for spoken presentation in HTML.

We're always keen for people to contribute in various different ways.

We do have a page which we maintain, which is helpfully titled ‘what we're working on’, and we try to ensure that that's as up to date as possible.

Within WCAG 3 editor's draft, we've got a lot of requirements and guidelines, which we know are more than likely absolutely necessary, but we don't necessarily have solid research on those.

There are a number of notes within there where there's a question or an editor's note saying, needs additional research.

If anybody feels like going through those and filling in some of those gaps, we'd really be happy for that.

Finally, we are also keen for people to be involved as sponsors to the work.

And there is W3C principles champion, which is an opportunity for you to demonstrate visible support for the accessibility work.

Thank you.