Re: Help/ direction to reword capabilities appropriately

Proposing ...

The capabilities discussed include supplying missing alternative text,
personalizing the visual presentation, and rebuilding interactive
components.  We also discuss whether the capability remediations
discussed can be automated based on the presence of programmatically
recognizable patterns ...


Jason Taylor writes:
> Sound good, notice I updated the capabilities wording. Just to make sure you saw.
> 
> J
> 
> 
> This e-mail and any accompanying attachments are intended only to be read or used by the named addressee(s). It is confidential and contains legally privileged information. If you have received this message in error, please notify the sender immediately and delete this message.
> 
> Sent from my iPhone
> 
> On Feb 17, 2025, at 11:11???AM, Janina Sajka <janina@rednote.net> wrote:
> 
> ???Hi Jason:
> 
> How about the following:
> 
> Post-source approaches identified include ...
> 
> The capabilities discussed include ...
> 
> Jason Taylor writes:
> Hi Janina
> 
> 
> Appreciate the re-write - very close.
> 
> 
> I would change two words and use the ???doing??? words for capabilities.
> 
> My notes - We don???t consider the approaches we just assume you could use a range . And we identify capabilities not address.
> 
> So my rewrite would be for those two paraphrase.
> 
> 
> Approaches could include JavaScripted adaptations, and realtime HTML and CSS rewrites on content delivery networks (CDNs) as well as in browser extensions???all without writing any of these adaptations into the original source.
> 
> The capabilities identified include applying missing alternative text, correcting visual presentation , providing personalization, and rebuilding interactive components. We also discuss whether these capabilities can be automated based on the presence of programmatically recognizable patterns conducive to automated adaptation
> 
> 
> ???
> 
> This e-mail and any accompanying attachments are intended only to be read or used by the named addressee(s). It is confidential and contains legally privileged information. If you have received this message in error, please notify the sender immediately and delete this message.
> 
> Sent from my iPhone
> 
> On Feb 14, 2025, at 10:23???AM, Janina Sajka <janina@rednote.net> wrote:
> 
> ???Thanks, Jason--good catch!
> 
> I've now updated the Abstract. Please review:
> 
> https://A11yEdge.github.io/capabilities/#abstract
> 
> I started using your suggested text--it was helpful. But as I tightened
> and tightened, the original language you provided morphed into shorter
> phrasing--except for the description of how we address automatability.
> 
> Jason Taylor writes:
> Thanks Lionel
> 
> Only change is (as we were using current)
> 
> The ???provide custom components??? should now be ???provide interactive components???
> 
> As we are changing and adding the WCAG text for Custom components to interactive components for both the rebuilding of and providing of.
> 
> J
> 
> This e-mail and any accompanying attachments are intended only to be read or used by the named addressee(s). It is confidential and contains legally privileged information. If you have received this message in error, please notify the sender immediately and delete this message.
> 
> Sent from my iPhone
> 
> On Feb 11, 2025, at 6:40???AM, Lionel Wolberger <lionel.wolberger@levelaccess.com> wrote:
> 
> ???
> I like these changes. Thank you for all you attention to these details.
> To simplify follow-up I isolate the ones you changed in this bulleted list (current / slash propose). I leave out section number as that is assigned in rendering.
> 
> *
> Alternative Text /  Provide Alternative Text
> *
> Tooltip Provisioning /  Provide Tooltips
> *
> Site Language Indication /  Indicate Site Language
> *
> Captions /  Provide Captions
> *
> Video Descriptions /  Provide Video Descriptions
> *
> PDF Remediation /  Remediate PDFs
> *
> Cursor & Focus /  Manage Cursor and Focus
> *
> Text Styling /  Optimize Text Styling
> *
> Color /  Optimize Color Usage
> *
> Custom Components /  Provide Custom Components
> *
> Navigation & Hyper Elements /  Enhance Navigation and Hyperlinks
> *
> Notifications /  Provide Accessible Notifications
> *
> User Authentication /  Ensure Accessible User AuthenticationText Services (Semiotics) /  Provide Text Services (Semiotics)
> *
> Numbers and Digits with TTS /  Expand Numbers and Digits with TTS
> *
> Live Site Translations /  Provide Live Site Translations
> *
> Text Styling /  Optimize Text Styling
> *
> Color /  Optimize Color Usage
> *
> Custom Components /  Provide Custom Components
> 
> ________________________________
> From: Jason Taylor <jason@usablenet.com>
> Sent: Tuesday, February 11, 2025 3:26 AM
> To: Janina Sajka <janina@rednote.net>; Lionel Wolberger <lionel.wolberger@levelaccess.com>
> Subject: Help/ direction to reword capabilities appropriately
> 
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> Hi
> 
> Below could help on the task that I identified. Around making sure our title represent actions  of capabilities??? and not ???subjects??? or other.
> 
> I know it would be better as a fork but I am not sure chat gpt will generate reliable .
> 
> 
> 1 Content (HTML)
> 
> 
> 1.1.1 Alternative Text
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Alternative Text
> 
> 
> 1.1.2 Tooltip Provisioning
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Tooltips
> 
> 
> 1.1.3 Site Language Indication
> 
> Status: Needs rephrasing
> 
> Suggested Change: Indicate Site Language
> 
> 
> 1.1.4 Captions
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Captions
> 
> 
> 1.1.5 Video Descriptions
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Video Descriptions
> 
> 
> 1.1.6 PDF Remediation
> 
> Status: Needs rephrasing
> 
> Suggested Change: Remediate PDFs
> 
> 
> 1.1.7 Provide Accessible Fonts
> 
> Status: Appropriately action-oriented
> 
> 
> 1.1.8 Provide Dyslexia-Friendly Fonts
> 
> Status: Appropriately action-oriented
> 
> 
> 1.1.9 Cursor & Focus
> 
> Status: Needs rephrasing
> 
> Suggested Change: Manage Cursor and Focus
> 
> 
> 1.1.10 Text Styling
> 
> Status: Needs rephrasing
> 
> Suggested Change: Optimize Text Styling
> 
> 
> 1.1.11 Color
> 
> Status: Needs rephrasing
> 
> Suggested Change: Optimize Color Usage
> 
> 
> 1.1.12 Custom Components
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Custom Components
> 
> 
> 1.1.13 Navigation & Hyper Elements
> 
> Status: Needs rephrasing
> 
> Suggested Change: Enhance Navigation and Hyperlinks
> 
> 
> 1.1.14 Notifications
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Accessible Notifications
> 
> 
> 1.1.15 User Authentication
> 
> Status: Needs rephrasing
> 
> Suggested Change: Ensure Accessible User Authentication
> 
> 
> 1.1.16 Text Services (Semiotics)
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Text Services (Semiotics)
> 
> 
> 1.1.17 Numbers and Digits with TTS
> 
> Status: Needs rephrasing
> 
> Suggested Change: Expand Numbers and Digits with TTS
> 
> 
> 1.1.18 Live Site Translations
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Live Site Translations
> 
> 
> 1.1.19 Read Content Aloud
> 
> Status: Appropriately action-oriented
> 
> 
> 2 Presentation (CSS)
> 
> 
> 2.1.1 Optimize Text Size
> 
> Status: Appropriately action-oriented
> 
> 
> 2.1.2 Optimize Cursor Size
> 
> Status: Appropriately action-oriented
> 
> 
> 2.1.3 Optimize Hyperlink Visibility
> 
> Status: Appropriately action-oriented
> 
> 
> 2.1.4 Text Styling
> 
> Status: Needs rephrasing
> 
> Suggested Change: Optimize Text Styling
> 
> 
> 2.1.5 Color
> 
> Status: Needs rephrasing
> 
> Suggested Change: Optimize Color Usage
> 
> 
> 2.1.6 Custom Components
> 
> Status: Needs rephrasing
> 
> Suggested Change: Provide Custom Components
> 
> 
> 3 Interactions (JavaScript)
> 
> 
> 3.1.1 Ensure Keyboard Access to Interactive Elements
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.2 Manage Focus Through Interactive Processes
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.3 Supply a Reading Guide
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.4 Optimize Color Contrast
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.5 Ensure Text Transparency
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.6 Provide Accessible Notifications
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.7 Manage Time Outs
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.8 Validate Form Content
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.9 Rebuild Component
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.10 Replace Component
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.11 Remediate Structural Semantics
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.12 Clarify Interactive Elements Status
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.13 Notify External Link Targets
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.14 Notify Ambiguous Links
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.15 Expand Acronyms with TTS
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.16 Reset All Personalizations
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.17 Moderate Content
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.18 Leverage Automation
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.19 Edit Accessibility by Site Owner
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.20 Edit Accessibility by Third Party
> 
> Status: Appropriately action-oriented
> 
> 
> 3.1.21 Bundle Features into Profiles
> 
> Status: Appropriately action-oriented
> 
> 
> 
> --
> 
> 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/
> 
> 
> --
> 
> 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/
> 

-- 

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/

Received on Monday, 17 February 2025 17:49:48 UTC