Re: Re[2]: Call for Consensus (CfC): Publish AI-Accessibility FPWD

+1

On Fri, Mar 14, 2025, 10:31 AM Joshue O'Connor - InterAccess <
josh@interaccess.ie> wrote:

> Thank you Cleyra, Niklas and Gottfried for spotting typos, grammar gotchas
> and other suggestions!
>
> Appreciated.
>
>
>
>    Joshue O'Connor
> *Director / InterAccess.ie*
> (+353) 01 961 0059
>
>
>
>
>
>
>
>
>
>
>
>
> ------ Original Message ------
> From "Cleyra Uzcategui" <cleyra.uzcategui@gmail.com>
> To "Janina Sajka (janina@rednote.net)" <janina@rednote.net>
> Cc public-apa-admin@w3.org
> Date 12/03/2025 5:02:12 PM
> Subject Re: Call for Consensus (CfC): Publish AI-Accessibility FPWD
>
> Good draft.
>
> Here my comments:
>
> *Comments on typos and grammar issues: *
>
> Abstract section:
>
> "Machine learing technology also has unique and significant limitations."
>
>    - Correction: learing should be learning.
>
>
> "illustrative of accessibiltiy-related applications..."
>
>    - Correction: accessibiltiy should be accessibility.
>
>
> Accessibility context:
>
> "if machine learning algorithm may address broader accessibility issues..."
>
>    - correction: algorithm should be algorithms.
>
>
> “existing web standard such as..."
>
>    - correction: standard should be standards.
>
>
> Section 3.2
>
> “yellow has been found the achieve the highest result...”
>
>    - Correction:  “yellow has been found to achieve the highest result...”
>
>
> “Until recently, the accuracy and validity of ASR techniques in the same
> language were considered as ineffective practices...”
>
>    - Correction: Remove "as" — “...were considered ineffective
>    practices...”
>
>
> Section 3.4
>
> “...converting complex language content to the level of lower secondary
> reading abilities often require human intervention.”
>
>    - Correction: "Require" should be "requires"
>
>
> Section 3.5
>
> “Although there are few examples in a web context where the language of
> content is defined by machine learning processes...”
>
>    - Correction: "Few" should be "a few”
>
>
> Section 4:
>
> “...and is capable of monitoring web content in real time.”
>
>    - Correction: "Is" should be "are" (referring to tools)
>
> Another aspect I noticed is the inconsistent use of "colour" and "color" —
> please ensure all terms align with the same spelling convention (British
> vs. American English).
>
>
> *Comments on structure: *
>
> The logical flow of the document is good. The structure moves from the
> relevance of current standards (Section 3.1) into specific use cases —
> alternative text, ASR, plain language, etc. — before transitioning into
> evaluation tools and accessibility overlays. This sequence makes sense,
> starting with guidelines and ending with practical tools.
>
>
> *Suggestions on expanding scope: *
>
> *Cognitive Accessibility and AI:*
>
> Discuss how AI can support individuals with cognitive disabilities by
> simplifying navigation, reading comprehension, and time management.
>
> Example: AI tools that adjust web interfaces by minimizing distractions,
> providing summaries, or offering personalized reading levels.
>
>
> *Cultural and Multilingual Accessibility:*
>
> AI's ability to provide culturally aware translations — beyond literal
> text conversion — would be crucial for multilingual accessibility.
>
> The draft touched on Automated Language Detection, but it might be worth
> expanding into AI's role in ensuring content remains contextually
> appropriate when translated.
>
> Kind regards
>
> Cleyra Uzcategui
>
> *Software Engineer*
>
> *📞 *+44 (0)7756172116
>
>
> On Wed, 12 Mar 2025 at 14:31, Janina Sajka (janina@rednote.net) <
> janina@rednote.net> wrote:
>
>> Colleagues:
>>
>> This is a Call for Consensus (CfC) to the Accessible Platform
>> Architectures (APA) Working Group proposing  publication of a First Public
>> Working Draft (FPWD) of the Research Questions Task Force Note track
>> document: "Accessibility of machine learning and generative AI." We
>> generally refer to this document by its short name: "AI-Accessibility."
>>
>> *       The snapshot to review for this CfC is here:
>>
>> https://raw.githack.com/w3c/ai-accessibility/FPWD-ai-accessbility/index..html
>> <https://raw.githack.com/w3c/ai-accessibility/FPWD-ai-accessbility/index.html>
>>
>> *       RQTF's resolution requesting publication of the above snapshot
>> version as an APA Note is recorded here:
>>         https://www.w3.org/2025/03/12-rqtf-minutes.html#e753
>>
>> *       The W3C Note track process is described here:
>>         https://www.w3.org/2023/Process-20231103/#note-track
>>
>> Please note the above snapshot will look slightly different when
>> published. The Status of this Document section will be updated, and the
>> document will display with different colorization to reflect the document's
>> FPWD status.
>>
>> As always with APA CfCs, editorial corrections, such as spelling or
>> grammar,  will be made as needed without further notice.  Please do draw
>> our attention to any editorial issues you find in this draft.
>>
>>
>> ***Action to Take***
>>
>> This CfC is now open for objection, comment, as well as statements of
>> support via email. Silence will be interpreted as support, though messages
>> of support are certainly welcome.
>>
>> If you object to this proposed action, or have comments concerning this
>> proposal, please respond by replying on list to this message no later than
>> 23:59 (Midnight) Boston Time, Wednesday 19 March.
>>
>> NOTE: This Call for Consensus is being conducted in accordance with the
>> APA Decision Policy published at:
>>
>> http://www.w3.org/WAI/APA/decision-policy
>>
>> Janina and Matthew
>> APA Co-Chairs
>>
>>
>> --
>>
>> Janina Sajka (she/her/hers)
>> Accessibility Consultant https://linkedin.com/in/jsajka
>>
>> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
>> Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa
>>
>> Linux Foundation Fellow
>> https://www.linuxfoundation.org/board-of-directors-2/
>>
>>
>>