Conversation
| The ATAG CG will not work on any of the following topics: | ||
| </p> | ||
| <ul> | ||
| <li>Accessibility standards for content, this is the domain of WCAG. ATAG will reference |
There was a problem hiding this comment.
to disambiguate what a standard for content could be:
| <li>Accessibility standards for content, this is the domain of WCAG. ATAG will reference | |
| <li>Standards for the accessibility of content, this is the domain of WCAG. ATAG will reference |
| <li><a href="https://accessible.canada.ca/">Accessibility Standards Canada (ASC)</a>: The | ||
| ATAG CG will liaise with ASC on the development of accessibility standards for authoring | ||
| tools.</li> | ||
| </ul> |
There was a problem hiding this comment.
I think it would be helpful to liaise with other SDOs (I'm thinking exploring if we could work with ETSI/CEN/CENELEC to have a better authoring section in EN 301 549 to maximise impact; I'm in that group and happy to help).
| <li><a href="https://accessible.canada.ca/">Accessibility Standards Canada (ASC)</a>: The | ||
| ATAG CG will liaise with ASC on the development of accessibility standards for authoring | ||
| tools.</li> | ||
| </ul> |
There was a problem hiding this comment.
Should we liaise with policy makers on this too? To make sure they understand what we're doing and how they can reference it should they want to?
| are up to date. | ||
| </p> | ||
| <p> | ||
| The ATAG CG will also begin to incubate ideas for the next versino of ATAG, with a focus on |
There was a problem hiding this comment.
| The ATAG CG will also begin to incubate ideas for the next versino of ATAG, with a focus on | |
| The ATAG CG will also begin to incubate ideas for the next version of ATAG, with a focus on |
| Community Group. This should be a brief description describing the reason | ||
| the group has been formed.}</span> | ||
| The Authoring Tool Accessibility Guidelines (ATAG CG) will explore | ||
| updating ATAG and addressing the role of AI in accessible authoring |
There was a problem hiding this comment.
We're saying “AI” a lot in this paragraph.
Maybe we can leave it out in this first paragraph, as we're explaining the focus on emerging technologies in the next:
| updating ATAG and addressing the role of AI in accessible authoring | |
| The Authoring Tool Accessibility Guidelines (ATAG CG) will explore | |
| updating ATAG. |
| updating ATAG and addressing the role of AI in accessible authoring | ||
| for web content. The ATAG CG will incubate updates to ATAG relating | ||
| to the creation of accessible web content and authoring tool | ||
| accessibility, with a focus on emerging technologies like AI. This |
There was a problem hiding this comment.
This is not me being pedantic, but “AI” isn't very well defined, and a term that looks specific but isn't. I think that's a problem for us today, as it makes the charter less easy to grasp as it is, but also a problem in the future, when the word may start to mean other things.
My preference would be to talk about “LLMs” or “generative AI” here, as that's more specific.
If I'm alone in that, I'd also be happy for us to define what we mean by AI on the first instance.
There was a problem hiding this comment.
“generative AI” would be my preference. I do think folks will look more for "AI" than "LLM"
But would could also put that in brackets afterwards (Large Language Models (LLMs))
But that all gets even wordier.
| <li>Review ATAG 2.0 and identify areas for improvement and updating, including | ||
| references to WCAG 2.2, areas needing clarification, and any outdated references.</li> | ||
| <li>Explore developments in authoring tools and platforms since the release of ATAG 2.0, | ||
| including the rise of AI and LLMs in content creation, the increased use of web-based |
There was a problem hiding this comment.
maybe another development we could add here is the rise in headless CMSes (or CMSes that strictly separate content and presentation), and the major change in content types (TikToks just weren't as much of a thing back then… there's a lot more multimedia, more 'social' media too).
There was a problem hiding this comment.
Agree this is a good point. How about something like:
... including the rise of AI and LLMs in content creation, API-driven or headless authoring tools, ...
There was a problem hiding this comment.
I like it. Would suggest we update line 74 to include it like this:
| including the rise of AI and LLMs in content creation, the increased use of web-based | |
| including the rise of AI and LLMs in content creation, and the increased use of API-driven, headless, and web-based |
(in this suggestion I disambiguated 'rise of AI/LLMS' from 'rise of increased use' etc)
hidde
left a comment
hidde
left a comment
There was a problem hiding this comment.
Excellent first draft, great work!
I left a few nitpicks, typos and more general comments and concerns.
| <span class="remove">{TBD: describe the mission and goals of the | ||
| Community Group. This should be a brief description describing the reason | ||
| the group has been formed.}</span> | ||
| The Authoring Tool Accessibility Guidelines (ATAG CG) will explore |
There was a problem hiding this comment.
Add "Community Guidelines" after "Authoring Tool Accessibility Guidelines"?
There was a problem hiding this comment.
going to assume they misunderstood "CG" as meaning "Community Guidelines" ...
There was a problem hiding this comment.
Aahh I see… we might just say “This Community Group will explore”
There was a problem hiding this comment.
Whoops, yes I meant "Community Group".
"The Authoring Tool Accessibility Guidelines Community Group (ATAG CG)" to fully introduce the acronym.
Co-authored-by: Hidde de Vries <hidde@hiddedevries.nl>
6 participants
Based on the discussions in the group, here is my first go at creating a charter for this group. Please review and provide feedback!