Post
Thrilled Modern Web Guidance is now out, keeping quiet has been SO HARD! 🤐
I’ve had the opportunity to collaborate with Google on this project as a domain expert consultant over the past few months, and have seen firsthand the level of thoughtfulness and genuine care for developers and the web platform that has gone into it. ❤️
It’s still very early days, but I’m proud to have played a small part, and excited for what's next. Looking forward to seeing what folks build!
@leaverou Hey Lea!
I was looking for the accessibility section and the only thing I could find was about syncing :user-invalid with aria-invalid, and this is described as the way to make error announcements accessible?
I also couldn't find any accessibility guidance for keyboard management so now I'm assuming it refers to the built-in management that comes with <dialog> and popover?
Is this all? or am I missing something important somewhere?
@SaraSoueidan Hi Sara!
AFAIK most a11y guidance lives with the relevant use case guides — I believe the (in development) accessibility section you saw is intended for big picture a11y guidance + use cases *specifically* about a11y.
The idea being that a11y is an essential part of implementing a use case, not something the agent should search for separately.
That said, there are definitely gaps — it's a very early preview! If you can, please file issues, even if terse 🙏🏼
@leaverou Thank you Lea! That's helpful.
Another question: Are the gaps documented so we can know about them?
@leaverou WTF does Google care about web guidance.
@philipwalton to discuss it in more detail in 30 mins!
Install bonfire.cafe
Get the full app experience
