The question always hangs in the air, unspoken for a moment: "Is there a way to know when...?" Both client and developer understand the query, yet articulating it proves surprisingly difficult.
Initially, it seems purely technical – akin to asking about functionality on a specific device. But the hesitation reveals a deeper layer. Phrases like "assisted browsing context" don't roll off the tongue as easily as "on a phone" or "on a slow connection." The former is the language of accessibility experts; the latter, the client's everyday reality.
The question, finally voiced, is usually something like: "Is there a way to know when a user is using a screen reader?"
The answer, for a long time, was a welcome change from the typical complex web development response: "No, we can't." Technically, it's impossible; computers don't communicate that way. The "no" provided a sense of relief, confirming their unspoken assumption.
Even if technically feasible, I'd explain, it's undesirable. Detecting assistive technology use would add to our maintenance burden, not reduce it. It's analogous to the "phone-user" scenario; we can't reliably determine browsing context, and assumptions lead to problems. Each new feature would require additional work to ensure accessibility, raising the question: is the feature essential enough to justify the extra effort?
The idea of a fully featured website alongside a separate, accessible version might seem appealing. However, this approach quickly falls apart: an inaccessible main site will inevitably mean an incomplete accessible version. Creating a distinct "accessible experience" relegates it to an afterthought, mirroring the limitations of many dedicated mobile sites.
There's rarely disagreement. We've all experienced the frustration of being forced onto a subpar mobile site. We've learned from past mistakes.
Yet, the question transcends the purely technical. It's not just about browsers and screen sizes. The hesitation, the pause, the stumbling over words, transforms a mundane development question into something far more significant. The unspoken heart of the matter is: "Can we know if a user has a disability?"
The simple "no" was initially empowering, a convenient way out. But the introduction of "accessibility events" in iOS 12.2 and macOS 10.14.4 changed everything. This feature, quietly introduced, allows browsers to identify VoiceOver users. With this setting enabled (by default), a user's assumed disability is broadcast to the internet unless explicitly disabled.
(Update May 2019: Apple removed this feature.)
The outrage is justified, not only for users, but also for developers. Apple has made it possible to know if a user has a disability, opening the door to discriminatory practices. This information can be captured and used for targeted marketing or worse. All under the guise of inclusivity.
At some point, the developers of "accessibility events" were undoubtedly asked about its feasibility. Their "yes" was likely well-intentioned, a seemingly simple technical solution.
In the future, I will face similar hesitant questions. The pauses will be familiar. The easy "no" based on technical impossibility is gone. We can know if a user is using assistive technology. The information could be misused in countless ways.
But I won't participate in perpetuating Apple's mistake. My answer will be a heavy, uncomfortable "no." Not because we can't, but because we shouldn't. The "technically" excuse is gone. The answer is a firm, unequivocal No.
The above is the detailed content of Accessibility Events. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
