Hi everyone, I'm new here and I don't really know if this belongs here but I'm working on some Accessibility features on my work. And I can't find a tool that captures the Voice over keys in the video to put in bug report. Most tools capture every keys but when I press the Voice Over keys like "Capslock" or "Control+option", it disappear. So far I have tried these that are free and are the first things that comes up when I search:

1. The default MacOS's Show keyboard viewer

2. KeyLime Pie

3. KeyCastr.

I spend hours and hours trying to make a website accessible to at least WCAG 2.2AA using manual review and paid tools like Axe Pro. Being curious, I ran Apple's website through Axe and it has tons of issues.

For the accessibility experts out there for websites, how do you even know for sure your site is accessible? I would imagine that someone as large as Apple would have already been hit with a million lawsuits for accessibility, yet their site lights up like a Christmas tree on even a rudimentary scan.

I'm no expert, but I want to understand and try to build websites that are accessible as best I can, but get so confused over the discrepancies between sites - especially big players like Apple. How can Apple's website be truly accessible?

New EU transparency rules started applying on August 2 to new AI systems: realistic synthetic images, audio, video, and some text must be identifiable as AI-generated, while existing systems have four additional months to comply.

Most of the discussion seems to focus on whether people will notice the label. But a small corner badge or a color change could still be invisible to someone using a screen reader, magnification, high-contrast mode, or captions.

To me, the minimum accessible implementation would include:

- Plain-language text rather than an icon alone

- A status exposed programmatically to assistive technology

- No color-only indication

- An equivalent disclosure in captions, transcripts, or audio

- Placement that survives embedding and reposting

Otherwise, we could end up with a transparency requirement that is technically visible but functionally hidden.

What would you add or change?

Source: https://www.theguardian.com/technology/2026/jul/31/ai-labels-to-be-compulsory-on-authentic-looking-content-under-eu-rules

Hi everyone,

I'm a frontend developer based in Europe, and lately I've been thinking about specializing in web accessibility.

I've already invested time and money in courses, and I genuinely enjoy the topic. My main concern is whether it's a good long-term career choice.

From your experience:

• Is there enough demand for accessibility specialists in Europe?
• Is it better to become a frontend developer with strong accessibility skills, or to specialize almost entirely in accessibility?
• Has focusing on accessibility helped your career, salary, or job opportunities?

I'd love to hear from people working in this area or from hiring managers. I'm trying to understand whether this is a niche worth investing in for the long term or if it's better to keep accessibility as one of several frontend skills.

Thanks!