.@w3c WCAG should not be developed/designed for the benefit of #accessibility testing vendors. It is there to improve the user experience of disabled people.
🤨
"We expect to publish Web Content Accessibility Guidelines (WCAG) 2.2 as a “W3C Recommendation” web standard in 2023.
We are addressing new comments that we received in August 2023. Depending how that goes, the final publication could be in September or later in 2023."
"For people who are blind or low vision, identifying dynamic changes (non-user-initiated) in the content of a web app is very challenging. ARIA live regions are the only mechanism available today that communicate content changes down to the accessibility layer..."
Quick guidance for referring to (parts of) HTML elements By @yatil
“You always need to be very clear in what you mean. Otherwise, it is hard to read for your audience. Always include brackets with the element names. You can differentiate attributes and values by using these words. Always include the word “value” when talking about values.”
Simone here. A professional bassist, sound designer and producer for more than 25 years, I've been juggling between creativity and technical jobs for decades.
Pioneering #GameAudio in the early 2000s, I'm working to go back to the #videogame industry after a long hiatus. I was present at both the launch of Steam by Valve and Game Audio Network Guild, in San Jose, GDC 2002.
Why do people think progressive enhancement (PE) equals "no JavaScript"?
Genuinely asking. Every time I bring up PE ppl interpret it as saying "zero client JS" which is not PE. Progressive enhancement is additive client JS rather than exclusively JS?
"Regularly people link to or quote from some outdated version of a specification. This can be confusing and detrimental to understanding, if the information is no longer correct or relevant."
"I wrote an article in 2007 called Fieldsets, Legends and Screen Readers. It was my first post on the TPGi blog. I have been meaning to provide an update to it, for the last 15 years…"