Hi, as I’m wrapping up my commitments for the week, I wanted to share my thoughts on our current project title, “Accessibility at the Edge,” before it slips my mind. I understand that suggesting a major change like a new title is significant.
The term “Edge” traditionally refers to the practice of distributing code or assets closer to the user, so that as a webpage is requested, these elements are integrated into the page before the browser processes the code. However, I believe this doesn’t accurately describe the technical strategy we’re exploring.
Moreover, “Accessibility at the Edge” seems to imply a futuristic concept, whereas the technical approach under discussion has been in use for over 20 years. The method we’re discussing involves adding code or modifying personalization after the initial page load, which serves to replace, enhance, or improve the original code.
Therefore, I propose “Client-Side Accessibility Accommodation” as a more fitting title. This better reflects the technical actions we’re focusing on and acknowledges that we’re discussing a method aimed at accommodating user needs without altering the original code.
The sections discussing overlays would remain unchanged, as overlays employ this client-side accessibility accommodation instead of directly update original code. Personalization can also be seen as a form of accommodating user needs.
The concept of providing accommodation and the recognition that ii is not as as ideal as original access/universal design is also an important self awareness and industry recognition that would serve the underlying aim of this project well.
I hope you find my input both useful and interesting.
Hi, as I’m wrapping up my commitments for the week, I wanted to share my thoughts on our current project title, “Accessibility at the Edge,” before it slips my mind. I understand that suggesting a major change like a new title is significant.
The term “Edge” traditionally refers to the practice of distributing code or assets closer to the user, so that as a webpage is requested, these elements are integrated into the page before the browser processes the code. However, I believe this doesn’t accurately describe the technical strategy we’re exploring.
Moreover, “Accessibility at the Edge” seems to imply a futuristic concept, whereas the technical approach under discussion has been in use for over 20 years. The method we’re discussing involves adding code or modifying personalization after the initial page load, which serves to replace, enhance, or improve the original code.
Therefore, I propose “Client-Side Accessibility Accommodation” as a more fitting title. This better reflects the technical actions we’re focusing on and acknowledges that we’re discussing a method aimed at accommodating user needs without altering the original code.
The sections discussing overlays would remain unchanged, as overlays employ this client-side accessibility accommodation instead of directly update original code. Personalization can also be seen as a form of accommodating user needs.
The concept of providing accommodation and the recognition that ii is not as as ideal as original access/universal design is also an important self awareness and industry recognition that would serve the underlying aim of this project well.
I hope you find my input both useful and interesting.