angular-cli: Mac Voiceover will not start after ng serve has been run

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

_                      _                 ____ _     ___

/ \ _ __ __ _ _ | | __ _ _ __ / | | | | / △ \ | ’ \ / _ | | | | |/ _ | '| | | | | | | / ___ | | | | (| | || | | (| | | | || | | | // __| ||_, |_,||_,|| _||| |___/ @angular/cli: 1.0.0 node: 7.9.0 os: darwin x64 @angular/animations: 4.0.2 @angular/common: 4.0.2 @angular/compiler: 4.0.2 @angular/core: 4.0.2 @angular/flex-layout: 2.0.0-beta.7 @angular/forms: 4.0.2 @angular/http: 4.0.2 @angular/material: 2.0.0-beta.3 @angular/platform-browser: 4.0.2 @angular/platform-browser-dynamic: 4.0.2 @angular/platform-server: 4.0.2 @angular/router: 4.0.2 @angular/cli: 1.0.0 @angular/compiler-cli: 4.0.2

Repro steps.

Pre-req’s: Own a Macbook

  1. Run ng serve with any angular 2 app.
  2. Try to start Voiceover, Mac’s screenreader (built-in hotkey is Cmd+f5) either while it’s running or after it’s finished running.

Expected: Voiceover starts, reads screen. Result: Voiceover’s black box appears and disappears a few times, and then dies.

The log given by the failure.

N/A, although here’s the output from running ng serve, if that helps.

** NG Live Development Server is running on http://localhost:4200 ** Hash: daab498fd5db009b8bfb Time: 29612ms chunk {0} 0.chunk.js, 0.chunk.js.map 41.6 kB {1} {2} {5} [rendered] chunk {1} 1.chunk.js, 1.chunk.js.map 27.9 kB {0} {2} {5} [rendered] chunk {2} 2.chunk.js, 2.chunk.js.map 8.44 kB {0} {1} {5} [rendered] chunk {3} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 458 kB {8} [initial] [rendered] chunk {4} styles.bundle.js, styles.bundle.js.map (styles) 376 kB {8} [initial] [rendered] chunk {5} main.bundle.js, main.bundle.js.map (main) 67.7 kB {7} [initial] [rendered] chunk {6} scripts.bundle.js, scripts.bundle.js.map (scripts) 243 kB {8} [initial] [rendered] chunk {7} vendor.bundle.js, vendor.bundle.js.map (vendor) 6.48 MB [initial] [rendered] chunk {8} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered] webpack: Compiled successfully.

Desired functionality.

Voiceover can be started while ng serve is running or after it’s been run.

Mention any other details that might be useful.

Voiceover will continue to function if it is started before ng serve is run; it just won’t start while ng serve is running or after it’s been run. Also, it is possible to use browser-based screenreaders (like ChromeVox), and I haven’t tested with JAWS, but working with Voiceover would be helpful.

I’m aware this is probably a low-priority bug since it has an easy work-around, but for those of us working primarily on accessibility-related issues and for blind developers, this’d be a nice thing to fix.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 2
  • Comments: 22 (9 by maintainers)

Commits related to this issue

Most upvoted comments

Just found a crash report as I was trying to debug this. Key line:

*** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<__NSDictionaryI 0x7ff0b9004200> valueForUndefinedKey:]: this class is not key value coding-compliant for the key angular/cli.'

Thank you all so much! This is going to make accessibility-related work so much easier.

@ecerta I do not know if there is another bug in angular-cli, but we have applied a workaround that can be verified in the developer beta of 10.13.