- From: Chaals Nevile <charles.nevile@consensys.net>
- Date: Fri, 23 Feb 2024 03:05:45 +0000
- To: Janina Sajka <janina@rednote.net>, Lionel Wolberger <lionel@userway.org>, Jason Taylor <jason@usablenet.com>
- Cc: Accessibility at the Edge <public-a11yedge@w3.org>
The expanded title seems closer, and we could put "the Edge" in quotes to be clear that we mean pretty much everything after it the content was served. I don't have good ideas for the title but I like the sentiment. cheers On Thursday, February 22, 2024 15:59:40 (+01:00), Janina Sajka wrote: > +public-a11yedge@w3.org because we need to use our archived email list > for these conversations! > > One thought on retitling -- perhaps as a expanded title, i.e > > Accessibility at the Edge: > An Inventory of Non Source-Based Alternatives > > > I'm inclined to agree in the main with Jason on retitling, though I'm > mulling whether "not at the source" is too obviously, and unproductively > confrontational. I do like this litany of where else a11y might be > realized, though. That's a keeper, imo. > > Lionel Wolberger writes: > > + Janina > > > > Thought provoking! > > Janina, our agenda should, as soon as is practical, include addressing > > these "non-source" thoughts. > > > > > > On Mon, Feb 19, 2024 at 10:07???PM Jason Taylor <jason@usablenet.com> wrote: > > > > > Suggested Title Change: Making It firstly to you as Titles Are Significant > > > to Change and no point if it???s only my opinion. > > > > > > The term ???Web Accessibility Not at the Source??? would more effectively > > > communicates the alternative efforts and technical approaches to making > > > websites accessible to users with disabilities without modifying the > > > original website???s source code. These approaches can involve using external > > > tools, plugins, overlays, or browser-side changes that enhance > > > accessibility for various needs, such as visual, auditory, motor, or > > > cognitive impairments. > > > > > > It could include changes made globally at the edge, stored user > > > preferences activated with your Google account, custom client-side > > > remediation, and even simple CSS options (like color contrast option on > > > websites) along with more evolved CSS control panels. > > > > > > The empowerment lies in the fact that these changes can be made , and > > > therefore accessibility improved , without the delay of waiting for the > > > original website to be updated, along with them being performed by > > > resources other than the original website team. I.e central subject matter > > > experts helping improve a whole companies web presence . > > > > > > ??? > > > End > > > > > > > > > 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 19, 2024, at 1:07 PM, Lionel Wolberger <lionel@userway.org> wrote: > > > > > > ??? > > > > > > Dear Jason, > > > > > > Had trouble opening the A11Y Edge Zoom > > > It is open now. > > > If you are still available, would love to meet. > > > > > > https://us06web.zoom.us/j/84665535534?pwd=cDRubzgzdlZFQ2tqaEN1ZDZ4K2VOUT09 > > > > > > > > -- > > 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/ > > -- Charles 'Chaals' Nevile Lead Standards Architect, ConsenSys Inc
Received on Friday, 23 February 2024 03:05:58 UTC